← revolut Interview Insights

revolut·Product Manager·Onsite - Product Sense / Strategy·Senior

SeniorPrefer not to say
May 2026

Summary

PM interview at Revolut for a top-up team role. Two product questions back to back, one about launching a feature and one about diagnosing a metrics drop. Pretty standard fintech PM territory but the specificity of the context made it trickier than expected.

Questions Asked (2)

Q1

You're a PM on the top-up team at Revolut. How would you approach launching cash deposits as a new feature?

Go-to-Market (GTM)Product StrategyProduct Sense & Ideation
Author's notes

I went straight into user segments and distribution channels, probably too fast.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the goal and scope of cash deposits for Revolut's top-up team, then structure your answer around user needs, business impact, and a phased launch plan. Emphasize how you would prioritize features, mitigate risks, and measure success with clear metrics.

Pro tip: Show awareness of Revolut's regulatory environment and the importance of partnerships with banks or ATM networks to enable cash deposits. Highlight how you'd leverage existing user data to target the right segments and drive adoption.

1. Clarify Objectives and Scope

Ask clarifying questions to understand the goal (e.g., increase top-up volume, reduce churn) and constraints (e.g., regulatory, technical). Define what 'cash deposits' means (ATM, retail partners, etc.).

2. Understand User Needs and Market

Identify target users (e.g., underbanked, travelers) and their pain points with current top-up methods. Analyze competitors and market trends to assess demand and differentiation.

3. Define Solution and Prioritize Features

Brainstorm potential solutions (e.g., partnerships with ATM networks, retail cash-in networks) and prioritize based on impact, effort, and strategic fit. Consider MVP vs. long-term vision.

4. Plan Go-to-Market and Launch

Develop a phased rollout plan, including pilot testing, partnerships, marketing, and user education. Define success metrics (e.g., adoption rate, cost per deposit) and iterate based on feedback.

5. Assess Risks and Mitigation

Identify regulatory, operational, and fraud risks. Outline mitigation strategies, such as compliance checks, partner vetting, and monitoring systems.

Key Points to Mention

  • Regulatory compliance (e.g., AML/KYC) and licensing requirements for cash deposits
  • Partnership opportunities with ATM networks, retail chains, or banks to enable cash deposits
  • User segmentation and targeting (e.g., underbanked users, gig workers, travelers)
  • Cost-benefit analysis and unit economics (e.g., fees, operational costs)
  • Phased rollout with pilot testing and iterative feedback loops
  • Success metrics (e.g., adoption rate, deposit frequency, impact on top-up volume and retention)

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q2

If a key KPI for your team drops, how do you investigate and respond to it?

Product Analytics & MetricsRoot Cause Analysis
Author's notes

Felt okay about this one.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the KPI and its context, then walk through a structured root cause analysis that combines data validation, segmentation, and hypothesis testing. Emphasize cross-functional collaboration and a bias for action, showing how you prioritize fixes and measure impact.

Pro tip: Before diving into analysis, confirm the drop is real and not a data issue—many KPI drops are due to tracking errors or seasonality. Also, frame your response around customer impact and business outcomes to show product thinking.

1. Validate the data

Check if the drop is genuine by verifying data accuracy, tracking, and external factors like seasonality or market events. Rule out false alarms before proceeding.

2. Segment and localize

Break down the KPI by dimensions such as user cohort, geography, platform, or feature to identify where the drop is concentrated. This narrows down potential causes.

3. Form and test hypotheses

Generate hypotheses about root causes (e.g., recent release, competitor action, UX issue) and test them using data, user research, or experiments. Prioritize based on impact and likelihood.

4. Take action and measure

Implement the most promising fix, ideally via a quick experiment, and monitor the KPI to ensure recovery. Communicate findings and next steps to stakeholders.

5. Learn and prevent

Document learnings, adjust monitoring/alerting, and consider long-term improvements to avoid similar drops. Share insights across teams.

Key Points to Mention

  • Data validation and avoiding false positives
  • Segmentation to isolate the issue (e.g., by user cohort, platform, geography)
  • Hypothesis-driven approach with prioritization (impact vs. effort)
  • Cross-functional collaboration (engineering, data, design, marketing)
  • Rapid experimentation and iterative fixes
  • Communication and stakeholder management

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.