High-Performance Engineering - Inspired by Revolut
A pragmatic engineering career framework for fast-moving product teams, inspired by Revolut's emphasis on simplicity, fast delivery, feedback, ownership and high-quality software.
By The Growth Track · Inspired by Revolut
Use this template
Request a demo to use this template with your team. We’ll help you adapt it during the private beta.
Request a demoAlready have a workspace? Sign in and open the template from your workspace.
Overview
- Career tracks
- 1
- Levels
- 4
- Areas
- 5
About this framework
Designed for engineering teams operating in demanding, high-growth environments. The framework balances delivery speed with technical quality, reliability and ownership. Engineers are expected to progressively handle greater ambiguity, make stronger technical decisions and increase the impact of the people and systems around them.
Sources
- Revolut's Performance management playbookDocumentation
Disclaimer
Inspired by public engineering principles and career material from Revolut
Career structure
Tracks represent the career paths people can progress through. Each track is a ladder of levels, from first step to most senior.
Individual Contributor
4 levels
- Junior Engineer
- Software Engineer
- Senior Engineer
- Lead Engineer
Areas
Areas are the broad parts of performance and growth this framework defines. An area can be broken into capabilities when it needs more detail.
Delivery & Impact
Ability to turn problems into valuable outcomes quickly and predictably.
Described level by level, as a whole.
Technical Excellence & Simplicity
Ability to build understandable, effective and appropriately simple technical solutions.
Described level by level, as a whole.
Quality, Security & Reliability
Ability to build systems that behave correctly under expected and unexpected conditions.
Described level by level, as a whole.
Ownership & Decision Making
Degree of responsibility taken for outcomes, decisions and problems beyond assigned implementation work.
Described level by level, as a whole.
Collaboration & Technical Leadership
Ability to improve outcomes through communication, feedback and the growth of other engineers.
Described level by level, as a whole.
Expectations
Expectations describe what good performance looks like at each level. Choose a level to see what is expected there.
Individual Contributor
Junior Engineer
Delivery & Impact
- Delivery & Impact
- Delivers clearly scoped tasks with guidance from more experienced engineers.
- Communicates blockers early and incorporates feedback into subsequent work.
- Understands how assigned work contributes to the team's current objective.
Technical Excellence & Simplicity
- Technical Excellence & Simplicity
- Writes understandable code that follows established team conventions.
- Learns the architecture and technologies used by the team.
- Prefers straightforward solutions and asks for help before introducing unnecessary complexity.
Quality, Security & Reliability
- Quality, Security & Reliability
- Tests changes and handles expected failure cases.
- Follows existing security, observability and operational standards.
- Learns from incidents and bugs involving their work.
Ownership & Decision Making
- Ownership & Decision Making
- Owns assigned work through completion rather than only writing code.
- Asks questions when requirements or expected behavior are unclear.
- Takes responsibility for mistakes and learns from them.
Collaboration & Technical Leadership
- Collaboration & Technical Leadership
- Participates constructively in code reviews and team discussions.
- Seeks feedback and acts on it.
- Shares progress and problems clearly with teammates.
Individual Contributor
Software Engineer
Delivery & Impact
- Delivery & Impact
- Independently delivers small-to-medium features from implementation through production.
- Breaks problems into incremental releases rather than waiting for a perfect final solution.
- Balances delivery speed with correctness and maintainability.
Technical Excellence & Simplicity
- Technical Excellence & Simplicity
- Designs maintainable components and services within established architecture.
- Evaluates alternative approaches and explains the trade-offs behind technical choices.
- Reduces unnecessary complexity when modifying existing systems.
Quality, Security & Reliability
- Quality, Security & Reliability
- Designs tests around important behavior and failure scenarios.
- Considers security, performance, monitoring and operational support before release.
- Investigates production issues independently within familiar systems.
Ownership & Decision Making
- Ownership & Decision Making
- Independently makes day-to-day implementation decisions.
- Proactively identifies problems affecting their area and proposes solutions.
- Follows work through deployment, monitoring and stabilization.
Collaboration & Technical Leadership
- Collaboration & Technical Leadership
- Gives useful technical feedback and contributes to team decisions.
- Helps less experienced colleagues with familiar problems.
- Communicates technical decisions and their rationale clearly.
Individual Contributor
Senior Engineer
Delivery & Impact
- Delivery & Impact
- Owns ambiguous, high-impact initiatives from problem definition through production.
- Identifies delivery risks early and adapts the approach before they become blockers.
- Makes pragmatic trade-offs between short-term outcomes and longer-term engineering health.
Technical Excellence & Simplicity
- Technical Excellence & Simplicity
- Designs solutions for complex problems while keeping interfaces and architecture as simple as practical.
- Identifies problematic abstractions, coupling and architectural debt.
- Establishes patterns that make future development easier for the team.
Quality, Security & Reliability
- Quality, Security & Reliability
- Anticipates complex failure modes and designs systems that fail safely.
- Leads resolution of significant production incidents and ensures meaningful follow-up.
- Raises quality and reliability standards across the team's systems.
Ownership & Decision Making
- Ownership & Decision Making
- Owns outcomes across a significant product or technical area.
- Makes decisions in ambiguity and clearly communicates risks and trade-offs.
- Challenges assumptions when evidence suggests a better approach.
Collaboration & Technical Leadership
- Collaboration & Technical Leadership
- Mentors engineers and improves the technical judgment of the team.
- Leads technical discussions without relying on authority.
- Builds alignment between engineering, product and other stakeholders.
Individual Contributor
Lead Engineer
Delivery & Impact
- Delivery & Impact
- Drives delivery of business-critical initiatives spanning multiple engineers or systems.
- Creates clarity around ambiguous problems and establishes an effective technical approach.
- - Improves how teams deliver, removing systemic bottlenecks rather than only solving individual tasks.
Technical Excellence & Simplicity
- Technical Excellence & Simplicity
- Shapes architecture across major domains while actively resisting unnecessary complexity.
- Makes high-consequence technical decisions using explicit trade-offs.
- Establishes technical direction that supports future scale without premature over-engineering.
Quality, Security & Reliability
- Quality, Security & Reliability
- Identifies systemic reliability, security and operational risks across domains.
- Establishes engineering practices that prevent classes of failures rather than individual bugs.
- Balances reliability investments against product and business priorities.
Ownership & Decision Making
- Ownership & Decision Making
- Acts as a technical owner for strategically important domains.
- Makes decisions considering product, engineering, risk and business constraints together.
- Creates ownership in others rather than becoming a decision bottleneck.
Collaboration & Technical Leadership
- Collaboration & Technical Leadership
- Develops senior engineers and future technical leaders.
- Creates alignment across teams on difficult technical decisions.
- Raises engineering standards and positively influences the wider engineering organization.
Review method
The review method defines how people are assessed against this framework.
- Review method
- Rating + written feedbackReviewers rate each area on a scale (each capability, when an area is broken into capabilities) and explain it in writing.
- Evidence
- Reviewers can attach evidence
- Scoring
- No calculated scoreRatings stay as they are; no overall score is computed.
Rating scale
- 1Significantly below expectations
- 2Partially meets expectations
- 3Meets expectations
- 4Exceeds expectations
- 5Significantly exceeds expectations