Chime Data Scientist interview questions

9 Data Scientists have shared notes from their Chime interviews, with the questions they were asked in each round. That is 32% of the 28 Chime interview notes on Screna AI.

9 Data Scientist interview notes

Chime·Data Scientist·Technical Phone Screen

Jun 2026
Chime data scientist interview with a single heavy SQL question that covered basically every window function you've ever heard of. The kind of problem where you finish writing it and still aren't sure if it's right.
  • Given a users table and a transactions table, write a single SQL query using CTEs that returns, per user per calendar week: weekly revenue, a 4-week rolling sum of revenue, week-over-week percent change, and a dense rank of users by rolling revenue within each week. Also return each user's first purchase date and the number of days between their first and second purchase. Filter to rows where weekly revenue dropped at least 20% versus the prior week, and only show the top 3 ranks per week. Users with fewer than 2 purchases should still appear with a NULL for days to second purchase.

“This thing had like five requirements stapled together and I kept losing track of which CTE was supposed to feed which.”

View Post

Chime·Data Scientist·Technical Phone Screen

Jun 2026
Chime data scientist interview with a heavy SQL focus. Four questions built around two tables and a single e-commerce scenario, each one layering on more complexity than the last. The window functions and cohort retention parts were where things got interesting.
  • Given a table of user acquisitions with channel and date, write a query to return each acquisition channel alongside the count of distinct users acquired through it.
  • For each acquisition channel, rank users by their total cumulative spend and return the top three spenders per channel along with their totals.
  • Build a monthly cohort retention table showing, for each acquisition month, what percentage of users made at least one purchase in any month after their acquisition month.
  • Within 90 days of each user's acquisition date, compute the average revenue per user broken down by acquisition channel, then identify which channel has the highest ARPU in that window.

“Warmup question, basically.”

View Post

Chime·Data Scientist·Technical Phone Screen

Jun 2026
Chime Data Scientist interview that was basically one long experiment design question stretched across the whole session. Covers a lot of ground: metric selection, power analysis, pitfall detection, stakeholder comms. Dense but fair.
  • Walk through the full process of setting up, running, and analyzing an A/B test for a new recommendation widget, including how you'd handle pitfalls, determine sample size, pick primary metrics, and present results to stakeholders.

“This is a lot to cover in one question and I think I underestimated how much they wanted on the pitfall side.”

View Post

Chime·Data Scientist·Technical Phone Screen

Jun 2026
SQL take-home style question from Chime for a Data Scientist role. The problem was meaty enough that it felt more like a mini project than a screen, covering cohort definitions, bucketing, and retention logic all in one query.
  • Given a users table and a transactions table, write a SQL query that buckets users by how many transactions they made in their first 7 days after signup (0, 1, 2, 3+), then computes Day-30 retention rate per bucket, where retention means having at least one transaction in the window from day 30 to day 37 post-signup.

“The join logic is straightforward but the window math trips you up if you're not careful.”

View Post

Chime·Data Scientist·Take-home Assignment

May 2026
Chime DS interview that was basically a full case study dropped in your lap as a spreadsheet. One big multi-part question covering profit math, LTV/CAC, break-even algebra, and a launch recommendation. Felt more like a take-home than a live screen.
  • You're given segment-level A/B test data in an Excel file. Compute profit for Control and Feature variants in each segment, then calculate the incremental profit (Feature minus Control) for each.
  • Calculate LTV/CAC for each segment and variant. For new users, use CPA directly as CAC. For existing users, explain how you treat CPA given that most of those customers already exist.
  • If you can only make one global launch decision (ship to everyone or no one), what CPA cap for Segment A would make a full launch profit-neutral compared to Control? Show the formula and the numeric answer.
  • If Segment B is x% of total traffic and Segment A is the remaining (100 minus x)%, derive the minimum x at which launching to both segments is profit-improving overall. Give the answer as a percentage with your algebra shown.
  • Make a launch recommendation: ship to Segment B only, ship to everyone, or hold. Include two key risks or trade-offs and one follow-up analysis you'd run before a final go/no-go.

“The formula itself isn't hard: revenue minus cost minus (CPA times new customers).”

View Post

Chime·Data Scientist·Technical Phone Screen

May 2026
Chime data scientist interview with a single massive case study built around a messy A/B test for a fitness tracker launch. The whole thing is one long scenario with six sub-questions layered on top of each other, which felt more like a take-home than a live interview. Dense but fair if you've done experimentation work before.
  • For a user-level A/B test with overlapping marketing activity across channels, what randomization unit and exposure rule would you use to limit contamination? How do you handle users who receive ads but were never formally randomized, or who end up in both variants across different platforms?
  • Define a primary success metric and at least three guardrail metrics for this experiment, including how each is computed, the measurement window, and any exclusion rules.
  • What specific diagnostics would you run to check for sample ratio mismatch, instrumentation gaps, novelty effects, and day-of-week seasonality? For each, what test or threshold would you use, and what would you do if it fails?
  • How would you adjust for the concurrent marketing push that overlapped the test period? Walk through at least one concrete method, and explain the trade-offs versus alternatives.
  • With a 6% baseline conversion rate, a 50/50 split, alpha of 0.05 two-sided, 80% power, and roughly 2.8 million eligible users over the test window, what is the minimum detectable relative lift? Is the experiment adequately powered?
  • After all your adjustments, the estimated lift in 14-day conversion is +3.5% with a 95% CI of -0.5% to +7.5%, ARPU is up 1.2%, and refund rate increased by 1.1 percentage points. Do you recommend launch, rollback, or an extended test? What thresholds drive that decision and how do you communicate it?

“This is where I spent the most time and probably said too much.”

View Post

Chime·Data Scientist·Technical Phone Screen

May 2026
Chime data science interview with a meaty A/B testing case study around a fintech spend-tracking feature. The whole thing was basically one big scenario with a bunch of layered follow-ups, which I wasn't fully expecting from a phone screen format.
  • A fintech app ran an A/B test on a new Spend-Tracker feature, with results segmented by income level. Given the test and control metrics for each segment, walk through how you'd decide whether to launch. What factors, calculations, and thresholds would you use?
  • Out of all the metrics available (average revenue, total revenue, profit, acquisition cost), which two or three would you prioritize for this launch decision and why?
  • The High-Income and Non-High-Income segments show divergent results from the test. How do you interpret that, and what does it mean for the launch decision?
  • Before making a final launch recommendation, what additional analyses or data would you want to see?

“This is where I spent most of my time and honestly fumbled the structure a bit.”

View Post

Chime·Data Scientist·Technical Phone Screen

Apr 2026
Chime data scientist interview with a meaty A/B testing design question that covered basically the whole experimentation lifecycle in one shot. Felt more like a product analytics case than a pure stats exam, which I wasn't fully expecting.
  • Walk through how you would design and run an A/B test end-to-end for a new mobile recommendation algorithm. Include how you'd define success metrics, calculate sample size and test duration, and what pitfalls you'd watch out for.

“This is a broad question and I kind of froze deciding where to start.”

View Post

Chime·Data Scientist·Technical Phone Screen

Sep 2025
Chime data scientist interview with a heavy SQL/stats focus. Two-part question covering experiment analysis and SRM detection, all in PostgreSQL. The schema had enough gotchas baked in that you couldn't just wing it.
  • Given a multi-table schema for an A/B experiment (users, exposures, sessions, orders), write a single PostgreSQL query using CTEs that: assigns each user to their earliest exposure variant and drops crossovers, filters to non-bot qualified users, and computes per-variant and per-country (US/CA only) metrics including 14-day converters, conversion rate, revenue from non-refunded orders, and refund rate. Also exclude orders in a specific outage window for iOS users.
  • Write a second SQL query that performs a chi-square goodness-of-fit test for sample ratio mismatch across variants among qualified users, assuming a 50/50 expected split. Output observed counts per variant, expected count, the chi-square statistic, and an approximate p-value using only built-in functions like ln(), exp(), and power().

“This took me way longer to structure than I expected.”

View Post