Analytics Lead
Dataexpert39 creditsInterview mode

The Numbers Don't Tie, and the Board Meets at Nine

Three reports, three different revenue figures. Pick the truth tonight.

FNorthstar Academy 5 (72) 504 taken 50m Analytics Lead

The situation

At 8 PM the CFO forwards you the board deck with a one-line message: 'Finance says revenue was $4.2M, the product dashboard says $3.8M, and the billing export says $4.05M. Which one is right and why? I present at 9 AM.' Each number comes from a system that defines 'revenue' slightly differently — recognized vs. billed vs. collected, refunds handled three ways, one pipeline silently dropping a customer segment. You can't fix every pipeline tonight, but you have to reconcile the figures, produce one defensible number with a clear definition, and arm the CFO to answer the inevitable board question: 'can we even trust our own data?'

What you'll practice

Traces each figure to its definition (recognized vs. billed vs. collected) instead of guessing which 'feels' right.
Traces each figure to its definition (recognized vs. billed vs. collected) instead of guessing which 'feels' right.. Show it clearly — with evidence a reviewer can point to.
Isolates the specific discrepancies (refund handling, dropped segment) that explain the gaps.
Isolates the specific discrepancies (refund handling, dropped segment) that explain the gaps.. Show it clearly — with evidence a reviewer can point to.
Produces one reconciled number with an explicit, stated definition the CFO can defend.
Produces one reconciled number with an explicit, stated definition the CFO can defend.. Show it clearly — with evidence a reviewer can point to.
Honestly frames remaining data-trust risk and a credible fix-forward plan without overpromising.
Honestly frames remaining data-trust risk and a credible fix-forward plan without overpromising.. Show it clearly — with evidence a reviewer can point to.

The room

3 autonomous AI coworkers, each with their own agenda. They won't all agree.

L
Lena Whitfield
CFO
Wants: Needs one number she can defend to the board and a reason to trust the data team again.
Style: Composed under pressure, unforgiving of vague answers.
O
Owais Khan
Data Engineer
Wants: Knows the billing pipeline has a known refunds bug he never prioritized; reluctant to expose it.
Style: Tired, honest if pressed, defensive about backlog.
B
Becca Stone
Revenue Operations
Wants: Maintains the finance figure and insists it's authoritative; resists reconciling 'down' to a smaller number.
Style: Territorial, process-driven, certain she's right.

Your workspace

Real tools, pre-seeded with context. You're not roleplaying, you're working.

Code / IDE Docs / wiki Team chat

Scored on

Analytical rigorValidityCommunicationActionability

More in Data