SQL Quest › SQL Interview Prep › Monzo
Monzo's own hiring posts describe the SQL as a take-home, not a live test: a business question answered in SQL or Python in your own time, then an interview that walks through your logic, trade-offs and testing. Practise that shape here, on data that looks like a bank account's ledger.
16 practice challenges · 5 Easy / 6 Medium / 5 Hard · your first 10 solves free · runs in the browser
What is sourced: Monzo does not publish its interview format, so every specific about their process on this page is what candidates and prep guides described publicly — each one carries its source and the date it showed. Formats change; treat them as reported, not official. What is ours: the practice questions are SQL Quest challenges, picked because their SQL matches the patterns those sources report. They are not questions Monzo has asked.
Monzo does not publish the format. Each row is what candidates and prep guides have described publicly, with its source; where sources disagree, the row says so. Formats change — treat every specific as reported, not official.
| Roles where SQL is tested | Data Science (the take-home is written in SQL or Python) and Analytics Engineering (Monzo names its stack as dbt, BigQuery, Looker, SQL and some Python).[1][2] |
|---|---|
| Stages (Data Science, 2026) | A 15-minute recruiter call, a 45-minute initial call with a senior or lead data scientist, a technical screen, then final interviews of 2–3 hours: an open-ended case study and a behavioural interview. Senior and lead roles may add a leadership interview.[1] |
| Where the SQL is | In the technical screen, as a take-home coding task: clear, sensible SQL or Python that answers business questions with data, done in your own time rather than live in front of a panel. Monzo lists the technical screen as one hour; the post does not say how that hour divides between the task and the interview.[1] |
| The review | A technical interview with a data science manager or lead goes through the submission — its logic, trade-offs and testing — then an analytical discussion (experimentation, success metrics) and a communication part (explaining results, spotting misleading charts). Monzo says it is less about trivia than about reasoning.[1] |
| Time limit | The 2026 post sets none; the 2022 post says the take-home had no time limit and usually ended in a slide deck. The Analytics Engineering post gives its take-home one week.[1][3][2] |
| How it has changed | The 2022 post describes a ~30-minute recruiter call and a take-home presented as slides; the 2026 Data Science post a 15-minute call and a technical interview on the code. A data scientist who joined in 2022 describes his take-home as metric formulation with extensive SQL and data visualisation.[3][1][4] |
| Environment | Monzo's analytics run on BigQuery, dbt and Looker. None of the sources we could read says which tool the take-home itself is done in.[2][4] |
Sources: Monzo blog — Interviewing for Data Science at Monzo (Monzo's recruiting team) (27 Apr 2026); Monzo blog — Interviewing for Analytics Engineering at Monzo (Monzo's recruiting team) (25 May 2026); Monzo blog — Data hiring at Monzo: the interview process (21 Mar 2022); Monzo blog — Joining Monzo as a data scientist (first-person account) (17 May 2022). Accessed 13 Sep 2026.
Reported most often, in order
Difficulty: No source we could read grades it; Monzo describes the bar as clear, sensible code and sound reasoning rather than trivia, and the 2022 post set no time limit on the take-home. The data is accounts (signup date, plan, country), card transactions (merchant, category, amount, status, timestamps), transfers in and out between customers, and money moved into and out of savings pots.
Our Monzo practice set, by skill
The 16 SQL Quest challenges tagged Monzo, resolved onto the nine Skillmap skills. A challenge exercises several skills, so shares do not sum to 100%. This is the composition of the practice set on this page, not a measurement of Monzo’s interview.
Shapes candidates and guides report (paraphrased)
Practise now — SQL Quest challenges matched to those patterns
Our challenges, chosen because their SQL matches the shapes above; not questions Monzo has asked. Each card opens the challenge in the browser — no signup; a card marked Free can be one of your 10 free challenge solves.
These are SQL Quest challenges matched to the topics candidates report for Monzo — not questions Monzo has asked.
Every query here runs on SQLite in your browser. Joins, GROUP BY, CTEs and window functions are written the same way in PostgreSQL, MySQL and Snowflake; dates are where they differ (SQLite's strftime('%Y-%m', ts) is to_char(ts, 'YYYY-MM') in PostgreSQL), and the app lists each difference beside every challenge.
Drill the skills the Monzo set leans on, one at a time: GROUP BY exercises · CTE practice · JOIN practice · Window function practice · Date function practice — or browse every SQL practice question.
Every question in the Monzo set, one page each with the schema and a hint: Counting Across a JOIN · Monthly Spend Per Account · Card Spend by Country · Spend by Day of Week · The Ledger's First Week, Day by Day · Active Spender Cohort (HAVING) · Dormant Cards — No Transactions in the Last 14 Days · Month-over-Month Spend Growth by Category · Each Merchant's Share of Its Category · Running Total of Daily Card Spend · How Long Has Each Card Been Active? · Multi-CTE Revenue Pipeline · Customer Retention Cohort · Peak Rolling 30-Day Spend Per Account · Cards That Never Spend at Home · How Concentrated Is the Spend?.
Skillmap
Ten questions, no signup. You get a readiness score weighted to the SQL this page covers, your Skillmap across joins, window functions, aggregation and the rest, and the weakest skill to practise first.
No signup, no card. Your first 10 challenge solves are free; the Skillmap shows what to fix before the interview.
Start the Monzo set — free