Project codingLast reported Jun 2022
Make Account Transfers Safe Under Concurrency
Implement an account-to-account transfer and make it correct when transfers run concurrently.
Open practiceRevolut interview practice
Revolut interview questions and coding practice Start with verified evidence.
Practice from 1 Revolut-tagged public coding problem, organized only by the stage, topic, difficulty, and recency metadata FastPrep can verify. The broader public catalog also includes 1 project-coding exercise.
- Catalog
- 2 public practice assets (1 coding)
- Start here
- Use the stage named in your invitation
- Evidence
- Phone metadata, shown in context
Phone practice path
Phone Screen
Practice solving while explaining assumptions, tradeoffs, and complexity. Problems are ranked by repeated public catalog sightings.
1 Revolut-tagged Phone Screen problems available.
| Company | Problem | Difficulty | Public evidence | Action |
|---|---|---|---|---|
RERevolut | In-Memory URL ShortenerDesignHash Table | Medium | 1 public reportLast reported Jun 2022 | Practice |
01 · Preparation plan
Turn URL identifiers and concurrency-safe transfers into a deliberate practice loop.
Revolut's two public assets move from an in-memory identifier service to runnable financial concurrency, making idempotency, uniqueness, and atomic state changes the core preparation themes. Catalog labels guide practice but do not promise a current or universal hiring loop. This is a suggested practice sequence, not the employer's interview process. Your invitation and recruiter guidance remain the source of truth.
- 01
Practice In-Memory URL Shortener
Use In-Memory URL Shortener to rehearse deterministic code generation and reverse lookup. Keep the exercise's published contract separate from assumptions about Revolut's current interview process.
- Restate the exact input, output, and constraints for deterministic code generation and reverse lookup.
- Explain the data structure and complexity before completing the implementation.
- Test a boundary case, a repeated-value case, and the smallest valid input.
- 02
Practice Make Account Transfers Safe Under Concurrency
Use Make Account Transfers Safe Under Concurrency to rehearse atomic balance transfers under contention. Keep the exercise's published contract separate from assumptions about Revolut's current interview process.
- Reduce atomic balance transfers under contention to a small runnable milestone with a visible contract.
- Implement correctness first, then add the concurrency or durability boundary.
- Run a failure case and record what must remain true after recovery.
- 03
Connect deterministic code generation and reverse lookup with atomic balance transfers under contention
Finish the Revolut study block by comparing In-Memory URL Shortener with Make Account Transfers Safe Under Concurrency. Explain what changes between implementation-level correctness and the broader engineering tradeoff.
- Name the invariant shared by both exercises.
- Contrast their state, scale, and failure assumptions.
- Choose one follow-up and defend the next test you would run.
02 · Broader technical practice
Practice beyond standalone coding questions.
These public Revolut-tagged exercises cover additional technical formats. They are included only when a verified catalog record and a crawlable practice page both exist.
03 · Evidence boundary
What “Revolut interview questions” means here.
It means practicing transferable implementation, testing, and technical reasoning with public catalog assets FastPrep tags to Revolut. It does not mean FastPrep has access to the company's assessments or any private interview bank.
Repeated public sightings and last-reported dates can help you prioritize practice, but they cannot predict the questions, format, or platform in a specific interview.
- Only Revolut-tagged FastPrep catalog problems appear above.
- Stage labels and report dates remain visible as context.
- No official, private, leaked, or proprietary questions are claimed.
04 · Plain answers
Revolut interview practice questions, answered plainly.
This page owns technical-practice intent for Revolut. Hiring activity, timelines, and market signals remain on the separate hiring-insights page.
01What evidence supports this Revolut interview practice page?
The launch review verified 1 coding exercise, 1 project-coding exercise (2 total public practice items). The strongest reviewed themes are deterministic code generation and reverse lookup, atomic balance transfers under contention. Counts and report labels can change, so use this as a focused practice library and follow your own invitation for the current format, timing, and permitted tools.
02Is FastPrep affiliated with Revolut?
No. FastPrep is an independent interview-preparation product and is not affiliated with Revolut. The page uses FastPrep's public practice catalog and does not claim official, private, leaked, or proprietary employer questions.
03How are Revolut problems assigned to interview stages?
Stage labels come from FastPrep's public problem metadata. A problem can carry more than one reported stage, and hiring processes can change by role, level, location, and date. Treat the labels as preparation context, not a guarantee.
04Which Revolut interview stage should I practice first?
Start with the stage named in your invitation or recruiter message. If no stage is known, use the largest available set to build general problem-solving fluency, then rehearse explanation and testing separately.
05Does this page predict the Revolut interview process?
No. Public catalog counts, stage tags, and last-reported dates can help prioritize practice, but they cannot predict a specific interview's questions, sequence, timing, or platform.
Your next stage, made concrete
Pick a problem. Solve it end to end.
Start with the stage named in your invitation, then use public evidence as context—not as a promise of what you will be asked.
Open the practice set