Revolut Data Engineer candidates report time-pressured SQL, Python exercises, and technical follow-ups. Prepare for multi-table financial data problems and explain your reasoning clearly.
$128K
Avg. Base Comp
$165K
Avg. Total Comp
4-5 rounds
Typical Rounds
3-5 weeks
Process Length
Revolut Data Engineer interviews reported here concentrate on hands-on SQL and Python rather than abstract theory. One candidate described five stages: an HR conversation, HackerRank assessment, live SQL coding, live Python coding, and a hiring-manager round. Other reports describe different technical structures, so the exact sequence may vary.
Live SQL is the clearest recurring signal. Candidates describe multi-table financial-style schemas, joins, rolling averages, ranking, and time-based comparisons under pressure. Two accounts describe four live SQL questions on one schema within 45 minutes. Practice moving from joins and aggregations to window functions while checking assumptions about dates, transaction states, duplicates, nulls, and grouping logic.
Python preparation should stay practical. A reported assessment included basic string and collection tasks, and candidates also describe timed Python evaluation as part of a broader assessment or live-coding process. Narrate your approach and respond to follow-up questions: the reports indicate that interviewers may probe reasoning, edge cases, and implementation choices rather than considering only the final syntax.
For technical and hiring-manager conversations, be ready to connect your choices to reliable data work. Keep explanations concrete: describe the schema or pipeline, the calculation or transformation, validation checks, and tradeoffs before presenting the final solution. Review how Python, SQL, orchestration, and transformation tools fit into pipelines you have personally built.
Synthesized from 7 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Revolut process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Revolut
Write a query that returns all neighborhoods that have 0 users.
| Question | |
|---|---|
| Rolling Bank Transactions | |
| Top Three Salaries | |
| Experiment Validity | |
| Last Transaction | |
| Like Tracker | |
| Month Over Month | |
| Daily Logins | |
| Top 3 Users | |
| Third Purchase | |
| Rolling Average Steps | |
| Retailer Data Warehouse | |
| Total Spent on Products | |
| Find the First Non-Repeating Character in a String | |
| Daily Retention Summary | |
| Post Composer Drop | |
| Cumulative Reset | |
| Size of Joins | |
| Real-Time Transaction Streaming | |
| Google Maps Improvement | |
| Subscription Retention | |
| Sort Strings | |
| Hurdles In Data Projects | |
| Word Frequency | |
| Duplicate Rows | |
| Digitizing Student Test Scores | |
| Count Transactions | |
| Payments Received | |
| Time on FB Distribution | |
| Slow SQL Query |
Synthesized from candidate reports. Individual experiences may vary.
One candidate described an initial HR conversation that covered the process before technical evaluation. Treat it as an opportunity to clarify the role and subsequent stages; this sequence comes from one account rather than every candidate.
One candidate reported a HackerRank test containing SQL and Python exercises. Reported examples included a seven-day moving average and basic Python string or collection tasks, so candidates may benefit from practicing clear, correct solutions under timed conditions.
Several candidates report live SQL work involving multiple tables, joins, rolling calculations, window functions, and financial-style data. Two accounts specifically describe four questions in a 45-minute SQL round, with follow-ups and escalating difficulty.
One five-stage account included a live Python round, while another candidate reported an in-memory URL shortener exercise with core tests. The evidence supports practical coding and edge-case discussion, but not a universal Python-round format.
One candidate listed a hiring-manager round after technical coding. Candidates may be asked to explain technical choices and how they reason through data problems, consistent with reports that follow-up questions mattered during the live interview.
