How Mercury Interviews in 2026: Process, Sample Questions & What They Score
The complete process, sample questions, and what interviewers score.
Mercury / Interview snapshot
8
stages from
application to offer
36
reported questions
15
public sources
Independent: SupaCV is not affiliated with or endorsed by Mercury. This is one well-documented shape of Mercury's interviews, not a script: processes change and vary by role, team, level, and region, so confirm specifics with your recruiter.
On this page
01 / For every Mercury candidate
The process, start to finish.
Mercury (mercury.com) is the startup-banking fintech, not Mercury Systems, Mercury Insurance/Mercury General, or Mercury Financial, which are unrelated companies with similar names. This playbook covers the track Mercury is best known for: product and backend software engineering. Mercury runs roughly two million lines of Haskell in production, with React/TypeScript/Redux on the frontend, and its product engineering job postings ask for "knowledge of or excitement to learn Haskell, React, TypeScript, and Redux," so prior Haskell experience is not required.
Mercury publishes no interview-process page and no interview rubric. It does publish six company values on its official careers page ("Think actively", "Be super helpful", "Act with humility", "Appreciate quality", "Focus on the outcome", "Build relentlessly"), and those are listed here as the framework with the caveat that Mercury never states they are interview criteria.
The process reported by third-party guides runs about six rounds over roughly three to five weeks: recruiter screen, a SQL and code-review technical screen, an applied coding exercise or take-home, a banking-domain system design round, a distinctive craft / type-system conversation, and a hiring-manager behavioral round, with some candidates also reporting a final round built around a presentation plus STAR questions.
One of the two coaching guides used here also describes two additional algorithmic coding rounds inside its onsite loop that the other guide does not mention at all. Round count and take-home length differ between sources, so treat durations as approximate. Applications go through Greenhouse.
Stage 1: Recruiter screen
about 30 minutes
Background, interest in Mercury, team preference and compensation. Blind posters describe a recruiter conversation as the first step. Both third-party guides put it at 30 minutes; Mercury itself publishes no stage list.
Stage 2: Technical screen: SQL and code review
about 60 minutes
Blind posters report the first technical round for a Senior Backend Engineer role is on SQL and schema, with one commenter saying Mercury usually asks simple SQL questions to gauge level. One guide labels the round SQL/Code Review at 60 minutes; another labels the same slot a 60-minute technical phone screen with one applied coding problem in any mainstream language, so the exact format varies by role and team.
Stage 3: Applied coding exercise or take-home
varies
Sources disagree and the format appears to vary by level and role. One guide describes a 3-hour synchronous exercise (15 to 30 minutes of briefing, about 2 hours coding, 30 to 40 minutes of code walkthrough); another describes a 4 to 6 hour take-home for senior and staff roles, plus two further algorithmic/applied coding rounds inside its onsite loop that no other source in this playbook mentions; a Blind commenter describes an open-ended problem with supplied text and data files and about an hour and a half to work, in the candidate's own language and IDE.
Stage 4: System design, banking domain
about 60 minutes
Prompts reported are money-movement problems (ACH orchestration, reconciliation against partner-bank feeds, fraud scoring) rather than generic consumer-scale designs. Both guides state 60 minutes for this round; not confirmed by a first-hand account.
Stage 5: Craft / type-system round
varies
A conversational round on types, invariants, error handling and code design. One guide puts it at 60 minutes; the other describes the round in detail but states no duration for it. Reported only by third-party guides, not by any public first-hand account.
Stage 6: Hiring manager / behavioral round
about 45 to 60 minutes
Past projects, collaboration, comfort in regulated environments and customer empathy. Blind posters also mention a meeting with a lead before the final stage.
Stage 7: Final round with presentation
about 2 hoursRole dependent
A Blind poster describes a final round of roughly two hours combining a presentation with STAR-format behavioral questions; an older Blind thread asks whether Mercury still runs its 'passion presentation' interview. Not reported for every role, and not confirmed by Mercury.
Stage 8: Decision and offer
varies
Third-party guides put the whole loop at roughly three to five weeks from first recruiter contact to offer. Mercury does not publish a target timeline, and reported speed varies by team and role.
A tag is the condition given in brackets in the stage name.
Reported interview time, one scale in minutes
Where the minutes go
- Recruiter screen~30 min
- Technical screen: SQL and code review~60 min
- System design, banking domain~60 min
- Hiring manager / behavioral round~60 min
Not drawn: Applied coding exercise or take-home, Craft / type-system round, Final round with presentation and Decision and offer, whose durations are not given in minutes.
02 / What Mercury scores
Mercury values
01
Think actively
02
Be super helpful
03
Act with humility
04
Appreciate quality
05
Focus on the outcome
06
Build relentlessly
These six value names, which match mercury.com/careers and mercury.com/jobs word for word, appear with one-line descriptions ("Think actively: Lead with curiosity. Question, experiment, and find better ways to do things." and so on, through "Build relentlessly: Act as an unstoppable force in bringing vision into reality."). They are published as company values, not as an interview rubric: Mercury does not state anywhere public that interviewers score candidates against them, and publishes no interview evaluation framework. Use them as vocabulary for framing answers, not as a scoring sheet. The same six values appear on mercury.com/jobs.
03 / Coach's notes
Coach's tips.
The coach's tips are part of Interview Prep, which is included with Career.
04 / The research
Where this page comes from.
Compiled from public sources across 10 sites. Mercury's own page is among them: mercury.com/careers.
- sites
- 10
- coaching and prep guides
- 8
- Mercury's own pages
- 4
- candidate reports and forums
- 3
Source composition
Where the research comes from
Grouped by the kind of site that published each source: Mercury's own domain, candidate forums, and everything else.
- Coaching and prep guides8
- Mercury's own pages4
- Candidate reports and forums3
05 / The questions
Sample questions, by category.
Roles in the full set
Roles are grouped by the category each question fits, not by the source. Switching roles is part of Interview Prep, included with Career. The counts show what each role holds in the full set.
Sample question, SQL and code review screen
Given an accounts table, a transactions table and a partner_banks table, write a query that returns the top 10 customer accounts by net inflow over the last 30 days, excluding test accounts.
Tests SQL joins, aggregation, and a time-windowed exclusion filter across three tables.
Sample question, Applied coding and take-home
Build a small backend service to the requirements we brief you on, then walk us through your code and the decisions behind it.
Tests service design, code organization, and justifying tradeoffs in a live walkthrough.
Sample question, Craft and type-system round
Show me a time you caught a bug through the type system.
Showing 3 of 36 reported questions. The rest are in Interview Prep.
Practice Mercury questions in Interview Prep
Interview Prep is included with Career. Add Mercury as a Target Role and it builds an 8-question practice session from Mercury's reported questions, scores your answers, and adds the coach's tips.
Start free: score your resume, no credit card. Prep for Mercury comes next, in Interview Prep on Career.
Common questions
Quick answers.
How many stages are in Mercury's interview process?
Mercury has 8 stages, set out in The process.
What framework does Mercury use to evaluate candidates?
Mercury evaluates candidates against Mercury values, set out in What Mercury scores.
What kinds of questions does Mercury ask?
Mercury's questions fall into 6 categories, grouped in The questions.
How reliable is this Mercury interview playbook?
It is compiled from public sources, and the evidence is in The research.
Sources (15)
Every public source this page was compiled from. Links open in a new tab.
10 sites, by sources
- mercury.com4
- teamblind.com3
- job-boards.greenhouse.io1
- blog.haskell.org1
- builtin.com1
- techinterview.org1
- jobsbyculture.com1
- news.ycombinator.com1
- scoutify.com1
- tryexponent.com1
- 01mercury.com/careers
- 02mercury.com/jobs
- 03mercury.com/faq
- 04mercury.com/legal/terms
- 05job-boards.greenhouse.io/mercury/jobs/5832775004
- 06blog.haskell.org/a-couple-million-lines-of-haskell
- 07builtin.com/job/software-engineer-product/3223326
- 08techinterview.org/companies/mercury
- 09jobsbyculture.com/blog/mercury-interview-prep-2026
- 10teamblind.com/post/Mercury-Interviews-AEedOr1i
- 11teamblind.com/post/interview-with-mercury-oli8xuke
- 12teamblind.com/company/Mercury/posts/mercury-interview
- 13news.ycombinator.com/item
- 14scoutify.com/companies/mercury
- 15tryexponent.com/companies/mercury
Related reading
- STAR, XYZ, or CAR: Which Resume Bullet Formula Actually Works?STAR, XYZ and CAR all collapse to the same bullet in practice, why "quantify everything" is more contested than it sounds, and the one modern use of STAR that actually earns its keep.
- Jake's Resume: Why One LaTeX Template Took Over Tech HiringThe history behind the internet's most-copied resume template, why its formatting choices actually work, and how to get the same layout without touching LaTeX.
How similar companies interview
Compare Mercury's process with other Fintech & Payments companies in this playbook: