SQL Quest › SQL Interview Prep › Chime

Chime SQL Interview Questions

Two data scientist reports from late 2025 describe Chime's SQL on two tables, users and transactions: timestamps to truncate, CTEs, then ranking, the row before and a rolling sum — and, in one hiring-manager screen, a retention question with no schema given. Practise that shape here, on a card-transaction ledger.

Solve Chime question 1 now: JOIN with a Filter — free, no sign-up Check my readiness

16 practice challenges · 5 Easy / 7 Medium / 4 Hard · your first 10 solves free · runs in the browser

What is sourced: Chime 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 Chime has asked.

How the interview runs (sourced)

The Chime SQL interview, as candidates report it

Chime 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 testedTwo of the reports are for Data Scientist; a third, for a software engineering role leaning toward data engineering, also had SQL.[1][2][3]
Technical screenOne data scientist report (interview October 2025) describes a technical screen of one hour of SQL and one hour of a business case on a spreadsheet of metrics. The candidate wrote that a fast candidate gets through five or six SQL questions in the hour.[1]
Hiring-manager screenAnother data scientist report (interview November 2025) describes a recruiter screen, then a one-hour hiring-manager screen split in two: 30 minutes on background, 30 minutes writing SQL. The candidate was told Chime no longer gives a take-home and the next step was the virtual onsite.[2]
The dataBoth data scientist reports describe two tables, users and transactions. In the hiring-manager screen no schema was given: the candidate queried the rows first to learn the columns, then had to define a retention metric before writing it.[1][2]
Software engineering roleA report for a software role leaning toward data engineering (October 2025) calls the SQL very basic and says it did not include window functions.[3]
What is not settledAll three are single candidate reports from late 2025. None names the coding tool, and none describes a data analyst loop; no source we could read states one format for every Chime data role. (no reliable source)
  1. [1] PracHub — Chime Data Scientist technical screen, SQL and a business case (candidate report, interview Oct 2025) (25 Aug 2026)
  2. [2] PracHub — Chime Data Scientist hiring-manager screen, a retention question with no schema (candidate report, interview Nov 2025) (25 Aug 2026)
  3. [3] PracHub — Chime Software Engineer, basic SQL without window functions (candidate report, Oct 2025) (17 Sep 2026)

Sources: PracHub — Chime Data Scientist technical screen, SQL and a business case (candidate report, interview Oct 2025) (25 Aug 2026); PracHub — Chime Data Scientist hiring-manager screen, a retention question with no schema (candidate report, interview Nov 2025) (25 Aug 2026); PracHub — Chime Software Engineer, basic SQL without window functions (candidate report, Oct 2025) (17 Sep 2026). Accessed 22 Nov 2026.

The SQL that comes up

What Chime SQL questions test

Reported most often, in order

  • 1Timestamps truncated to a day or month before grouping
  • 2Layered CTEs
  • 3Ranking with ties kept
  • 4Comparing a row with the one before it
  • 5Rolling sums over a window
  • 6Defining a retention metric from users and transactions
  • 7Basic joins and aggregation (the software engineering report)

Difficulty: Reported as medium in the October 2025 technical screen and easy in the November 2025 hiring-manager screen, which ended in a rejection; the software engineering report calls its SQL easy. The data is users and their transactions, with the transaction time stored as a full timestamp.

Our Chime practice set, by skill

The 16 SQL Quest challenges tagged Chime, 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 Chime’s interview.

Sample questions

Chime SQL question shapes, and where to practise them

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 Chime 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.

Open all 16 Chime practice challenges →
Topic practice

Every challenge in the Chime set, by topic

These are SQL Quest challenges matched to the topics candidates report for Chime — not questions Chime 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 Chime set leans on, one at a time: GROUP BY exercises · JOIN practice · CTE practice · Window function practice · Date function practice — or browse every SQL practice question.

Every question in the Chime set, one page each with the schema and a hint: JOIN with a Filter · LEFT JOIN: Watch the NULLs Appear · Monthly Spend Per Account · Signup-Month Cohort Spend · The Ledger's First Week, Day by Day · Multi-Month Active Customers · RANK vs DENSE_RANK Side-by-Side · The Previous Order's Total (LAG) · Dormant Cards — No Transactions in the Last 14 Days · Spend and Disputes Per Cardholder — Without the Fan-Out · Busiest Merchants, and What a Tie Does to the Rank · Running Total of Daily Card Spend · 7-Day Rolling Revenue Average · Customer Retention Cohort · Peak Rolling 30-Day Spend Per Account · First-to-Second Transaction Latency.

Skillmap

How ready are you for the Chime SQL round?

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.

Check my Chime readiness Start the Chime set

Frequently asked

Ready for the Chime SQL round?

No signup, no card. Your first 10 challenge solves are free; the Skillmap shows what to fix before the interview.

Start the Chime set — free