Practice the messy, ambiguous problems that happen after the interview.
Sarah Chen
VP Product · Monday · 9:14 AM
Premium churn is up 8.3% MoM. Marketing thinks it's pricing. Engineering thinks it's a bug. I need data. Give me a recommendation by EOD.
Investigate→Traditional practice
“Find the second-highest salary.”
Real work
“Premium churn is up 8.3%. Marketing says pricing. Engineering says a bug. What's actually driving it?”
SQL, Python, and storytelling aren't separate subjects. In real work, they're one continuous flow.
A business question doesn't come with a schema hint or an expected output. SmartGoose gives you the ambiguity that makes it meaningful.
How it works
Every scenario flows through the exact same workflow you'll use on the job.
Write CTEs, window functions, and cohort queries against a simulated 4-table corporate schema. The data has intentional messiness: nulls from a migration, weird joins, edge cases that bite you on the job.
Load your SQL output into Pandas. Handle the messy data your query returned. Build the chart that tells the story, then decide which one actually answers the VP's question.
Retention by cohort
6-month viewStructure your findings using the Pyramid Principle. Lead with the delta, not the methodology. Give a VP something they can act on immediately.
Executive Summary
23% churn vs 8% average · 2.9× the baseline
Trial-to-paid friction at day 14, not pricing sensitivity
Reduce paywall friction for the free-to-paid upgrade flow
~40% reduction in Feb-cohort churn if addressed in Q2
Scenario 001
Monday · 9:14 AM · VP Product
“Premium churn is up 8.3% MoM. Marketing thinks it's pricing. Engineering thinks it's a bug. I need data. Give me a recommendation by EOD.”
Your task
Find what's actually driving the churn spike.
~60 min · SQL Module · more coming soon
Example output from Scenario #001
Illustrative only — not a real company result. The point isn't the number. It's that a recommendation, not a query, is the deliverable.
Executive Summary
23% churn vs. 8% average across all cohorts
Trial-to-paid friction at day 14, not pricing sensitivity
Reduce paywall friction in the free-to-paid upgrade flow
Meaningful reduction in Feb-cohort churn if addressed next quarter
Ambiguous business questions instead of isolated technical exercises.
Messy data, investigation, iteration, and more than one analytical path.
A recommendation a stakeholder could actually act on.
You write solid SQL. Now connect it to real business outcomes.
You understand the product. Now back your instincts with evidence.
You build dashboards people use. Now move into strategic analysis.
Just starting out? Aspiring analysts are welcome too — it's the same workflow you'll use on day one.
Vision, not roadmap commitments
The long-term opportunity is bigger than practice. Analytics education today is fragmented around isolated technical skills — we think the interconnected workflow is the real product.
“Every SQL course I found taught me to write queries. None of them taught me what to do when the answer wasn't obvious — when the question itself was the hard part.”
— Likhitha, Founder of SmartGoose
We're building the first scenarios now. Try the SQL module today, or join the waitlist for what's next.