Weekly business analysis cases

Analytics Challenges

Most practice sites test whether you can write SQL. These test whether you can find the real story in messy data and convince someone to act on it, which is the part interviews actually fail people on.

Free to enter
Everyone who submits is scored and ranked
Written feedback
A certificate for every submission

Leaderboard My challenges

Take a real business problem

Not a puzzle with one clean answer. A messy dataset, a stakeholder with a theory, and a deadline.

Submit your analysis

A public GitHub repo, your answers to the objective questions, and a recommendation short enough for a board to read.

Get scored on both

40% on whether your numbers are right, 60% on whether your analysis would survive a real stakeholder.

Past challenges

Each brief and dataset stays online, with the results once they are published.

See the leaderboard

Challenge #009Closed

The Stickiness Cliff

DAU/MAU fell from 35% to 28% the week the new release shipped, and growth has called an engagement emergency. Rebuild the metric from the raw events, find out who was in the numerator, and decide whether anything happened to real users at all.

SQLProduct AnalyticsData QualityMetrics Design

IntermediateClosed 14 Sept 2026View

Challenge #008Closed

The Pipeline Mirage

Win rate has fallen from about 31% to 10% since the new SDR team started, and the VP of Sales wants it disbanded. Check what the dashboard is dividing by, and whether the two teams are being compared at the same stage, before six people lose their jobs.

SQLSales AnalyticsFunnel AnalysisBusiness Analysis

IntermediateClosed 21 Sept 2026View

Challenge #006Judging

The Slow Support Queue

Average resolution time rose a third the month the support team's new helpdesk went live, and the VP wants it rolled back. Find out what happened to the typical ticket, and what happened to the average, before anyone signs a rollback.

SQLOperations AnalyticsData CleaningData Storytelling

BeginnerClosed 11 Oct 2026View

Challenge #005Closed

The Power User Myth

Users who create a Goal retain six times better, so growth wants to make it a required onboarding step. Work out whether the Goal is what keeps them — or whether staying is what lets them set one — then make the call.

Product AnalyticsCausal InferenceRetentionSQL

AdvancedClosed 4 Sept 2026View

Challenge #004Judging

The Last-Touch Trap

A brand's dashboard runs on last-touch attribution, and Paid Social barely registers — so growth wants to cut it. Check whether last-touch is hiding what Paid Social actually does, then make the call on the budget.

Marketing AnalyticsAttributionSQLData Storytelling

IntermediateClosed 28 Aug 2026View

Challenge #003Judging

The Winning Variant

An A/B test on a new pricing screen shows the new variant converting far better, and growth wants to ship it to everyone. Check whether the win is real before it goes live — and give the call on shipping it.

A/B TestingExperiment AnalysisSQLData Storytelling

AdvancedClosed 21 Aug 2026View

Challenge #002Closed

The Churn Spike

Monthly churn nearly tripled in June at a subscription app, a week after a price rise. Product wants to roll the price back. Work out whether the price is actually what happened — and say whether to roll it back.

SQLCohort AnalysisRetentionBusiness Analysis

IntermediateClosed 14 Aug 2026View

Challenge #001Closed

Diagnose the E-commerce Revenue Drop

The dashboard shows September revenue down about 15% at a home-goods retailer, and the team blames soft demand. Check whether that holds — and whether 15% is even the real number — then make the call on the paid social budget.

SQLBusiness AnalysisData StorytellingData Cleaning

IntermediateClosed 7 Aug 2026View

Why these are different

Every dataset here is generated with deliberate mess in it: duplicate rows from a retry bug, refunds recorded separately, timestamps in the wrong timezone, inconsistent codes. That is not to be annoying. It is because the gap between a junior analyst and a good one is almost never SQL syntax. It is noticing that the number looks wrong before the stakeholder does.