Mercury is the leading fintech for startup banking — checking, savings, credit cards, treasury, and increasingly accounting tools. Series C, $1.6B+ valuation. The interview emphasizes payment-systems engineering, regulated-industry constraints, and the thoughtful product engineering that defines Mercury’s reputation.
Process
Recruiter screen → take-home or coding phone → onsite virtual: 2 coding, 1 system design, 1 craft deep-dive, 1 behavioral. Take-home is common at senior+ levels. Cycle: 3–4 weeks.
What they actually ask
- Design an ACH and wire transfer system with reconciliation
- Design a transaction-monitoring system for fraud detection
- Design a virtual-card issuance platform
- Coding: medium DSA, plus practical real-world engineering
- Behavioral: customer empathy, ownership, taste for thoughtful product engineering
Levels and comp (2026)
- SE: $175K–$235K total
- Senior SE: $250K–$340K total
- Staff: $355K–$485K total
- Principal: $490K–$650K total
Prep priorities
- Be fluent in Haskell (yes, primary backend) and TypeScript (frontend)
- Understand payment rails (ACH, wire, FedNow, RTP, card networks)
- Brush up on financial-data engineering, audit trails, and compliance constraints (BSA/AML, KYC)
Frequently Asked Questions
Is Mercury remote-friendly?
Distributed-first since founding. Hub in San Francisco; most engineers remote across US/Canada.
Why Haskell for a fintech?
Strong type system reduces money-handling bugs; the team has deep Haskell expertise. The bar to onboard is high but the codebase is famously clean.
How does Mercury compare to Brex or Ramp?
Brex is corporate cards focused on later-stage. Ramp is corporate cards plus expense automation. Mercury is banking-first with cards as a complement. Comp is comparable across the three; product surface differs.