Diagnosing a Venmo Sign-Up Conversion Collapse to 2% After a UX Redesign

Quick Overview

Venmo's sign-up rate fell to 2% after a new user experience was rolled out, and the product manager must decide what to do. The prompt tests triage and rollback judgment, checking whether the metric itself changed, segment and funnel diagnosis, and how to confirm a fix while weighing friction against account quality.

Diagnosing a Venmo Sign-Up Conversion Collapse to 2% After a UX Redesign

Company: PayPal

Role: Product Manager

Category: Analytics & Experimentation

Difficulty: medium

Interview Round: Other

You are a product manager on Venmo, PayPal's peer-to-peer payments app. After a new user experience was rolled out, the sign-up rate fell to 2%. What would you do? ```hint Check what else changed Before searching for a product cause, think about everything that shipped with the new experience, including how the sign-up funnel is measured, and how you would find the exact point where people now stop. ``` ### Clarifying Questions - What was the sign-up rate before the change, and how is it defined: completed accounts divided by app installs, by people who open the sign-up screen, or by visitors to a web page? - Did the new experience reach everyone at once, or was it released by platform, by app version, or to a percentage of users through a feature flag? - Which parts of the sign-up flow changed: screen order, required fields, phone or identity verification, or linking a bank account or card? - Did anything else change around the same time, such as marketing campaigns, app-store listings or verification vendors? ### What a Strong Answer Covers - Immediate triage: how severe the drop is, who needs to know, and whether to roll back before the cause is fully known - Data validation: the metric definition, event logging and denominator changes the new experience may have introduced - A structured diagnosis by time, platform, app version, acquisition channel and funnel step, separating internal from external causes - Fixes matched to each likely cause, followed by a controlled test of the new flow against the old one - Success measures beyond completed sign-ups, such as activation, first payment and fraud rates on new accounts ### Follow-up Questions - The new flow added a required identity check that sharply cut fraud but also cut sign-ups. How do you decide whether to keep it? - The drop appears only on Android devices running the newest app version. What do you check next, and what do you do in the meantime? - How would you keep a release like this from reaching every new user before its effect on sign-ups is measured?

Overview: Venmo's sign-up rate fell to 2% after a new user experience was rolled out, and the product manager must decide what to do. The prompt tests triage and rollback judgment, checking whether the metric itself changed, segment and funnel diagnosis, and how to confirm a fix while weighing friction against account quality.

PayPal logo
PayPal
Oct 12, 2026
mediumProduct ManagerOtherAnalytics & Experimentation
0
0

You are a product manager on Venmo, PayPal's peer-to-peer payments app. After a new user experience was rolled out, the sign-up rate fell to 2%. What would you do?

Clarifying Questions Guidance

  • What was the sign-up rate before the change, and how is it defined: completed accounts divided by app installs, by people who open the sign-up screen, or by visitors to a web page?
  • Did the new experience reach everyone at once, or was it released by platform, by app version, or to a percentage of users through a feature flag?
  • Which parts of the sign-up flow changed: screen order, required fields, phone or identity verification, or linking a bank account or card?
  • Did anything else change around the same time, such as marketing campaigns, app-store listings or verification vendors?

What a Strong Answer Covers Guidance

  • Immediate triage: how severe the drop is, who needs to know, and whether to roll back before the cause is fully known
  • Data validation: the metric definition, event logging and denominator changes the new experience may have introduced
  • A structured diagnosis by time, platform, app version, acquisition channel and funnel step, separating internal from external causes
  • Fixes matched to each likely cause, followed by a controlled test of the new flow against the old one
  • Success measures beyond completed sign-ups, such as activation, first payment and fraud rates on new accounts

Follow-up Questions Guidance

  • The new flow added a required identity check that sharply cut fraud but also cut sign-ups. How do you decide whether to keep it?
  • The drop appears only on Android devices running the newest app version. What do you check next, and what do you do in the meantime?
  • How would you keep a release like this from reaching every new user before its effect on sign-ups is measured?