How Revolut builds world-class product managers: ownership, depth, and wow products

Executive overview

Revolut consistently produces product managers who go on to become CPOs, startup founders, and senior leaders at other companies. The formula is not about hiring experienced professionals — it's about finding raw intellect and hunger, then forging them in an environment of extreme ownership, deep complexity, and an uncompromising bar for product quality.

Product owners at Revolut are local CEOs: end-to-end responsible for their product, their team, and their business metrics. Founders review every screen shipped. The result is a forcing function that builds skills no amount of experience can substitute.

The core insight: hiring less experienced but exceptionally driven people, then giving them total ownership and a relentlessly high quality bar, produces better product leaders than hiring seasoned professionals who rest on their credentials.

The "local CEO" model

• Product owners own the product end-to-end: roadmap, metrics, execution, and customer outcomes
• Cross-functional teams (engineers, designers, data analysts, ops) have the product owner as line manager
• Three specialisations: UX product owners, technical product owners, and data science product owners
• 85–90% of skills are shared across all three types; specialisation accounts for only 10–15%
• Founders review 100% of screens shipped via weekly product reviews with every team
• Flat hierarchy lets founders give direct steering to any product owner without layers of management

What great product owners have in common

• Strong problem-solving with both linear and non-linear thinking
• Deep customer empathy translated directly into product decisions — not filtered through a research function
• Technical depth: willingness to sit with engineers and read code
• Business acumen: understanding which roadmap choices drive the metrics that matter
• Ability to steamroll blockers, align stakeholders, and get things shipped
• "If something is 99% done, it's closer to 0% than 100%" — ownership extends to adoption, not just delivery

The obsession with wow products

• Quality and UX are never traded away, even in early-stage products — only functionality is scoped down
• Building a scrappy MVP makes it impossible to distinguish a bad idea from a bad product; building wow removes that uncertainty
• Small, lean teams ship across 50 countries by building on scalable platforms rather than custom solutions
• Revolut's credit division ships new products for 50 countries monthly with ~300 people; incumbents use 2,000–3,000 for one country
• Founders' weekly product reviews act as a last line of quality control — not micromanagement, but a forcing function for standards

Hiring for raw intellect over experience

• Revolut prioritises raw intellect and hunger to build over years of experience
• Experienced professionals from established companies often take too long to ramp up and resist changing the status quo
• Strong hiring signals: startup founders or co-founders, people who have built things with small teams, people who are power users of the category
• Internal transfers (from ops, engineering) are a highly successful path — guaranteed culture fit plus domain knowledge
• Sourcing targets products Revolut's own team admires, then sources from the companies that built them

Going deep as a leadership practice

• Senior leaders choose 7–10 of ~100 concurrent projects and go to engineering-level depth on those
• The signal that certain projects are under scrutiny creates discipline across all other teams
• Ambitious people at Revolut are motivated to remain autonomous — they self-regulate to avoid being the next project under deep review
• Going deep does not mean micromanagement; the goal is to verify the modus operandi and catch teams that are off track early

How new products are set up for success

• Any employee can propose a new product via a structured "new bets" framework covering market size, business case, competitive advantage, and customer problem
• A small team is assembled, builds quickly, and iterates — but quality bar applies from day one
• Products are kept narrow in functionality until metrics and retention are proven, then scaled instantly across the 50M+ customer base
• Joint accounts example: launched lean, grew to over 1 million active users
• New products benefit from immediate distribution and trust from existing customers

Lessons from failure

• Early startup: built an end-to-end cinema ticketing system including custom hardware — spent all investment before validating the business model
• Key lessons: stay lean, validate before scaling, understand run rate; hardware compounds the risk of moving too fast
• The right instinct (build something you would love to use) was correct; the execution error was scaling cost before proving demand