Revolut HackerRank Test: Format, Scoring Threshold, and How to Pass

The Revolut HackerRank test is the first technical filter in Revolut's hiring process. It comes before the recruiter screen, runs 60 minutes, covers medium-difficulty DSA and SQL problems, and requires a score above 70% to advance. The platform logs every tab switch, keystroke cadence, and full-screen exit. At least one candidate in 2026 had their assessment marked invalid due to a floating browser widget briefly covering the Run Code button. This guide covers the format, the difficulty distribution, and exactly how to prepare.

Quick Answer

• The Revolut HackerRank test runs 60 minutes with a mix of data structures and algorithms questions plus SQL. For data and analytical roles, the SQL component is heavier and includes statistics.
• Based on analysis of 2026 Revolut interview data, the difficulty distribution is 42% easy and 58% medium with no hard questions. Correctness and clean implementation matter more than solving advanced puzzles.
• The 70% threshold is the minimum to advance. The platform is fully proctored and logs tab switches, window changes, and paste behavior throughout the assessment.

Where the HackerRank Test Fits in the Revolut Process

The Revolut hiring process for technical roles runs five stages: HackerRank online assessment, recruiter screen, live coding round, take-home task or system design, and bar raiser final round. The HackerRank test is the gate before any human contact with a recruiter. Most candidates who fail Revolut's process do not make it past this first technical filter.

The test is sent to candidates after an application review. You receive a link and a deadline, typically 3 to 7 days from receipt. The 60-minute clock starts when you open the assessment. You cannot pause it once started.

The full Revolut interview process guide covers all five stages including the live coding and bar raiser rounds that follow the HackerRank test for candidates who advance.

Format by Role Track

Software Engineering track: Data structures and algorithms questions in the candidate's language of choice, SQL challenges with a fintech flavor (transaction analysis, aggregations, window functions), and occasionally logic or math puzzles. The DSA questions emphasize arrays and traversal problems most frequently, followed by dynamic programming, two-pointer techniques, and linked list operations. Graph problems appear but are less common than in FAANG assessments.

Data Analyst and Operations track: The data track version runs the same 60-minute format but weights SQL analytics and basic statistics more heavily. Candidates in 2026 report seeing probability questions and hypothesis testing items in the first half, followed by a substantial SQL analytics task in the second half. The SQL task involves interpreting and querying realistic fintech transaction data, not simple JOIN exercises.

For all tracks, the Codility assessment guide covers overlapping problem types and preparation strategies that apply to the Revolut HackerRank format as well.

The 70% Threshold and What It Means for Prep

Candidates who score above 70% on the Revolut HackerRank test move to the recruiter screen. The 70% threshold means you need to produce correct, running solutions on most questions within the time limit. A clean brute-force solution that runs scores better than an optimized solution with syntax errors. Get a working answer first on every problem, then optimize if time remains.

The difficulty distribution of 42% easy and 58% medium with no hard questions is the most important preparation insight: you do not need to solve obscure advanced algorithm puzzles to clear Revolut's test. A solid command of medium-difficulty DSA covering arrays, two-pointer, sliding window, basic tree traversal, and SQL window functions is sufficient preparation for the majority of questions.

Build your preparation around timed practice. Solving 20 medium problems in 3 hours is not the same as solving 5 medium problems under 60-minute time pressure where each problem requires reading comprehension, implementation, and debugging. The time pressure, not the problem difficulty, is where most candidates underperform.

Practice the interview format using AI mock interview sessions that replicate timed technical pressure before your actual HackerRank assessment. Using Final Round AI's Interview CoPilot helps you build the systematic approach to timed assessments that the Revolut test rewards.

Proctoring: What the Platform Logs and What Gets You Flagged

The Revolut HackerRank test is fully proctored. The platform automatically logs every departure from the test window, compares your keystroke timing and paste behavior against expected solving cadence, and records full-screen exits. Violations are reviewed and can result in an invalid assessment even if your code is correct.

Specific behaviors that trigger flags in 2026: switching to another browser tab or window while the timer runs, copying large blocks of code from outside the assessment window, taking screenshots, and using external tools that alter the window size or overlay the test interface. At least one candidate in 2026 had a scheduled recruiter screen withdrawn after a floating browser widget briefly covered the Run Code button and triggered an automatic flag.

Prepare your testing environment before you open the assessment. Close every other browser tab and application. Use a wired internet connection if possible. Disable any browser extensions that alter page layouts, block ads with overlays, or modify how pages render. These are the most common sources of accidental flags.

For prep discussions on coding assessments and what to expect from timed technical screens, read how SWE candidates approached timed technical rounds in the community.

Browse more technical prep in our technical interview guides collection.

Author's Comment

"The Revolut HackerRank test is not a puzzle-solving competition. It is a correctness-under-time-pressure filter. The candidates who fail it are almost never the ones who don't know the algorithms. They are the ones who know the algorithm but can't implement it cleanly within the time limit because they have not practiced that specific format. Timed mock practice where you write working code under a countdown is the preparation that actually moves the needle."

Jaya Muvania - SEO Specialist, Final Round AI

Preparation Plan for the Revolut HackerRank Test

The week before your Revolut HackerRank assessment, structure your practice around timed sessions rather than topic-by-topic review. Set a 60-minute timer, open a fresh HackerRank environment, and solve 2 to 3 problems without stopping the clock for searches or reference material. Log the types of problems where you ran over time or produced incorrect output. Those are your preparation priorities for the remaining days.

For DSA, prioritize arrays and string manipulation first, then two-pointer techniques, then sliding window, then basic graph traversal. Dynamic programming appears but is less common than at FAANG companies. For SQL, practice window functions, aggregations with HAVING clauses, self-joins, and transaction analysis queries that involve calculating running totals or detecting outliers. These formats appear most frequently in Revolut's fintech-flavoured SQL challenges.

For the data and analytical track, add statistics review to your preparation. The 2026 Revolut ops test included probability and statistics items in the first half before the SQL task. Reviewing basic probability, conditional probability, expected values, and interpreting summary statistics takes less time to review than DSA and is disproportionately important for the data track version of the test.

One day before your assessment, do a full environment check: clean browser with all extensions disabled, wired connection if possible, no background applications running. The proctoring system logs everything from the moment you open the assessment link. Starting with a clean environment prevents the most common accidental flags.

After the HackerRank Test: What the Recruiter Screen Tests

Candidates who clear the Revolut HackerRank assessment advance to a recruiter screen. The recruiter screen is a 30-minute video call covering your background, your interest in Revolut, and your understanding of the role. Unlike the HackerRank test, the recruiter screen evaluates communication clarity and cultural fit rather than technical correctness.

Revolut specifically evaluates alignment with its "Think Deeper, Never Settle, and Dream Team" values starting at the recruiter screen. Having a clear, specific answer to "Why Revolut?" that goes beyond "I think fintech is interesting" is the most common differentiator between candidates who advance and those who do not after clearing the technical assessment.

For engineering roles, the recruiter screen is followed by a live coding round and a take-home technical task. For data and analytical roles, it is followed by a structured case interview. The full Revolut process typically runs 4 to 6 weeks from the HackerRank submission to offer for candidates who advance through all stages.

Alongside technical practice, use Final Round AI's Interview CoPilot to prepare your recruiter screen story. The Goal feature lets you configure the session with Revolut's role description and practice articulating why Revolut specifically and how your background maps to the fintech challenges Revolut is solving. Passing the HackerRank test opens the door to the recruiter screen, and preparing for that conversation before you submit the test means you are ready for the full process if you advance.

Related Interview Guides

• Revolut Interview Process: All five rounds from HackerRank to bar raiser explained
• Codility Assessment Guide: Format and prep strategy for timed coding assessments
• Revolut Bar Raiser Interview: What the final values assessment actually tests

Frequently Asked Questions

How long is the Revolut HackerRank test? The Revolut HackerRank test runs 60 minutes. The timer starts when you open the assessment link. It cannot be paused once started. The clock applies to the full assessment regardless of how many questions are included.

What score do you need to pass the Revolut HackerRank test? Candidates who score above 70% on the Revolut HackerRank assessment advance to the recruiter screen. This is the minimum threshold based on 2026 candidate reporting. Scores are calculated based on test cases passed, not by question count alone.

What topics does the Revolut HackerRank test cover? Software engineering tracks cover data structures and algorithms (arrays, linked lists, dynamic programming, two-pointer techniques) and SQL with a fintech flavor. Data and analytical tracks cover SQL analytics more heavily plus probability and statistics. The difficulty distribution is 42% easy and 58% medium with no hard questions.

Is the Revolut HackerRank test proctored? Yes. The platform logs tab switches, full-screen exits, keystroke cadence, and paste behavior. Violations are reviewed automatically. At least one candidate in 2026 had their assessment invalidated due to a browser widget interfering with the test interface.

Can I use Python for the Revolut HackerRank test? Yes. Candidates can use their language of choice including Python, Java, JavaScript, and other standard languages. The platform scores based on whether your code produces the correct output on the test cases, not on the language used.