The retail-banking analyst role at a regional or money-center bank: deposit growth decomposition, deposit beta on MMAs, NSF/OD fee revenue post-CFPB, branch consolidation scoring, NII decomposition, primary-banking-relationship classification, churn leading indicators, and FTP-allocated branch P&Ls against a realistic retail bank with planted reconciliation traps.
30 missions (estimated) · 9 tables · retail bank core with planted ledger and snapshot mess
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 Retail COO, Branch Ops Manager, Treasurer, and Customer Insights Lead — weekly retail dashboards, ALCO-ready deposit beta, NSF/OD scenario modeling, and branch P&L with FTP allocation.
6-table retail_* core (customers, accounts, products, branches, transactions, daily balances) plus retailops_* specialty tables for branch activity, fees, and ATM events. Numbers anchor to 2024-2026 retail banking realities.
Average daily balance, weighted deposit beta, primary-relationship EXISTS logic, churn lag features, FTP curve allocation, and the multi-CTE rollups that real retail-bank dashboards run on.
Every mission maps to a real retail-banking-analyst task — weekly retail packs, ALCO submissions, branch-strategy memos, and the SQL that retail teams at JPMC / BofA / PNC actually screen for.
Each mission is a real request from someone at the company. Difficulty increases as you go.
A retail-bank star schema with 11 tables, 60K+ rows, and planted reconciliation traps. Trailing-space vendor names that split GROUP BYs, miscoded products, weekend snapshot gaps, late-posted transactions, joint-account dupes, and test accounts that need filtering before anything ties to the GL.
●dimension tables ● fact tables
Deposit beta has to tie, the branch P&L has to net to the GL, and the COO wants the story — in SQL.
Looking for something different?