The SQL-first finance role at tech, fintechs, and modern CPG: variance bridges, gross-margin decomposition, running cash burn, YoY revenue growth, and board-ready P&L rollups against a realistic ledger with planted reconciliation issues. Also a strong foundation for traditional FP&A — the SQL patterns are identical, but entering corporate FP&A usually wants CPA or CFA alongside. caseSQL targets the technical variant first.
30 missions (10 free · 20 Pro incl. 5 Master) · 6 tables · finance ledger with planted reconciliation traps
Read the briefing
A Slack message from your manager
Explore the schema
5 tables in a star schema
Write your query
Full SQL editor with autocomplete
Get expert feedback
Graduated hints, not just pass/fail
Answer questions from the CFO, FP&A Manager, Treasury Analyst, Controller, and Senior Auditor — MBR variance packs, budget attainment, revenue seasonality, cash burn, and vendor concentration.
Duplicate vendors, un-posted journal entries, inconsistent account-type casing, refund leakage, and duplicate payments — the reconciliation traps that quietly wreck a variance narrative.
A vs B vs F vs PY variance, gross margin decomposition, running cash burn, YoY revenue growth, percentile ranking, cohort onboarding, and late-posting analysis.
Every mission maps to a real Finance Data Analyst task — MBR packs, QBR decks, CFO-ready variance bridges, and the SQL Stripe / Meta / Google finance teams actually screen for.
Each mission is a real request from someone at the company. Difficulty increases as you go.
A company ledger star schema with 5 tables, 5,500+ rows, and planted reconciliation issues. Duplicate vendors that inflate spend rankings, un-posted journal entries hiding from totals, inconsistent account-type casing that splits your GROUP BYs, refund leakage, and duplicate payments that quietly skew vendor risk.
●dimension tables ● fact tables
The P&L has to tie out and the CFO wants a variance story — in SQL, not a spreadsheet.
Looking for something different?