Revolut Software Engineer Interview: Rounds, Take-Home & Questions

Last updated: August 2026

Quick Answer

The Revolut software engineer interview runs five stages: a recruiter screen, a take-home coding task (typically 4-8 hours), a take-home review discussion, a live coding round, and a culture fit conversation with the hiring manager. Mid-level and above candidates also face a system design round. The take-home filters out most candidates and is weighted as heavily as a full interview round. From first contact to offer, the typical timeline is three to six weeks.

Stage	Format	Duration
Recruiter screen	Video	30 minutes
Take-home task	Asynchronous coding project	4-8 hours work, 5-7 day deadline
Take-home review	Video walkthrough with senior engineer	45-60 minutes
Live coding	Video with shared editor	45-60 minutes
System design (mid+ only)	Video discussion	45-60 minutes
Culture / hiring manager	Video	45-60 minutes

What Revolut Is Testing in This Round

Every stage tests two things: technical competence and ownership culture fit. The “Dream Team” philosophy means interviewers evaluate whether you can own a feature end-to-end in a live fintech environment, not just write correct code.

• Take-home: Production thinking. Tests, documentation, and edge cases you were not asked to handle.
• Take-home review: Defending architecture under pressure and acknowledging trade-offs honestly.
• Live coding: Practical problem-solving (transaction processors, currency converters). Clean error handling matters more than algorithmic cleverness.
• System design: Fintech-scale reliability — currency exchange, card processing, fraud detection, ACID ledgers.
• Culture fit: Ownership, speed, data-driven reasoning, direct communication.

What to Expect

Tech stack. Backend: Java and Kotlin. Frontend: React and TypeScript. Infrastructure: Kubernetes microservices. You can use any mainstream language for the take-home and live coding, though JVM familiarity is an advantage for backend roles.

The take-home task. Typical tasks: a currency exchange API, a transaction categorization service, a notification service, or a data pipeline. The spec is open-ended — what you add on your own initiative is part of the evaluation. Expect 4-6 hours of work. Revolut wants production-quality code with tests, not a working prototype without them.

The take-home review. A senior engineer walks through your submission: “Why this architecture?” “How does it scale to 10x load?” “Where are the failure modes?” “What did you cut?” Collaborative but probing.

Live coding. One practical problem: a transaction processor, a currency conversion service, or an event-ordering service. Interviewers expect clean code and a running explanation of your reasoning.

System design (mid-level+). Fintech-scale prompts: real-time currency conversion across multiple liquidity providers, card payment processing with sub-second latency, fraud detection pipelines, or a multi-currency ledger with ACID guarantees. See our system design interview guide for preparation frameworks.

Prepare for the live coding and system design rounds with OphyAI Coding Interview: set up a prompt, get a streamed approach, then re-implement it unassisted to build real fluency before the real round.

Example Questions and How to Answer Them

“Design a currency exchange service that shows the best rate across multiple providers.” Approach: Clarify requirements (currency pairs, latency target, volume). Design a pricing engine that polls multiple liquidity providers, caches rates with TTL, and applies Revolut’s margin. Address rate staleness, race conditions on writes, and regulatory requirements around rate transparency. Discuss circuit breakers for provider failures.

“Walk me through your take-home submission. What would you do differently?” Approach: Lead with the design rationale, not the code. Say what trade-offs you made deliberately (e.g., chose simplicity over performance for the caching layer), what you cut for time, and what you would add next. Interviewers reward honest assessment of your own work over defensive posturing.

“Implement a function that finds all duplicate transactions in a stream, with deduplication within a 5-minute window.” Approach: Sliding window with a hash map keyed on a transaction fingerprint (amount + merchant + card + timestamp truncated to 5-minute buckets). State time and space complexity. Handle follow-ups: what if the stream is distributed? What if deduplication needs to be durable?

How to Prepare in One Week

1. Days 1-2: Take-home readiness. Practice building a small service end-to-end in four hours: write tests first (or alongside), document your architecture decisions in a README, and handle at least three edge cases. Review your current test coverage habits.
2. Days 3-4: Live coding and fintech patterns. Solve 10-15 medium problems on practical data processing: sliding windows, hash maps, event ordering, transaction pipelines. Practice with OphyAI Coding Interview, then re-implement unassisted.
3. Days 5-6: System design. Prepare two fintech system design problems: a real-time pricing service and a payment processing pipeline. Drill the structure with OphyAI Interview Practice.
4. Day 7: STAR stories. Prepare 5-6 STAR stories that emphasize speed, ownership, measurable outcomes, and decisions made with incomplete information.

Common Mistakes

Submitting a take-home without tests. The single most common rejection reason. No tests = no offer, regardless of the code quality.

Generic system design answers. “I’d use a database” loses points. Revolut expects fintech-specific answers: ledger systems, idempotency keys, regulatory constraints, rate management.

Defending poor take-home decisions. If you cut a corner, say so and name the trade-off. Interviewers want intellectual honesty, not a perfect submission.

Vague culture answers. “I love fast-paced environments” is not an answer here. Bring a STAR story where pace or pressure was a real constraint you navigated.

Start practicing Revolut-style questions →

Related Guides

• Revolut interview guide (full process)
• Revolut team fit interview
• Technical interview prep for software engineers

Frequently Asked Questions

How hard is the Revolut software engineer take-home task?

The task itself is typically medium difficulty: building a small service or solving a practical data processing problem. The difficulty is not the algorithm; it is the standard of execution. Revolut expects production-quality code with tests, documentation, and explicit handling of edge cases. Candidates who submit a working prototype without any of those elements are regularly rejected, even when the core logic is correct.

Can I use any programming language for the Revolut take-home?

Revolut generally accepts any mainstream language for the take-home and live coding rounds. However, the backend is Java and Kotlin, and interviewers note that familiarity with JVM-based languages is an advantage for backend roles. If you are equally comfortable in Java or Python, Java may give a slight edge in how your submission is evaluated for a backend position.

Does Revolut ask LeetCode-style algorithm questions?

Revolut’s coding rounds are practical rather than purely algorithmic. You are more likely to see a transaction processing service, an event deduplication problem, or a currency conversion API than a pure binary tree traversal. That said, strong fundamentals in data structures and hash maps are essential for solving these problems efficiently. Expect medium-difficulty algorithm thinking applied to real-world fintech scenarios.

How does the Revolut take-home review work?

The take-home review is a 45-60 minute video call with one or two senior engineers who have already read your submission. They will ask you to walk through your architecture, explain your design choices, identify where you made trade-offs, and reason about failure modes and scalability. It is collaborative but probing. Candidates who can say “I chose X over Y because of Z, and if I had more time I would add A” tend to do better than candidates who are defensive about their submission.

Sources and verification notes

Sources checked August 2026. The Revolut software engineer interview details above are drawn from the broader Revolut interview guide and candidate-reported accounts of the software engineering process.

• Revolut interview guide (OphyAI): full process overview, take-home details, culture section, and compensation.
• Revolut Engineering Blog: public posts on Revolut’s technical stack, architecture decisions, and engineering culture. Checked August 2026.
• Glassdoor, Revolut Software Engineer Interview: candidate-reported process stages, take-home format, and question types. Checked August 2026.
• Revolut Careers: official job descriptions and engineering role expectations. Checked August 2026.