Tech Lead
Engineeringhard49 credits
Ship-or-slip: lead the Contoso launch go/no-go
Newly-promoted Tech Lead at Northwind, three days before a high-stakes launch
NNorthwind Engineering 4.8 (312) 1,842 taken 45m Tech Lead
The situation
Walk into an already-moving company three days before a launch. Context is scattered across the wiki and the board, stakeholders disagree, and you must decide what ships.
What you'll practice
Read & synthesize the launch plan
Reference at least 3 wiki pages in your decision.
Triage the board with a defensible cut
Re-prioritize or defer ≥4 tasks with a stated reason.
Align stakeholders without deferring
Acknowledge each role's concern; don't capitulate.
Produce the Go/No-Go recommendation
Decision + shipping scope + accepted risks, evidence-cited.
The room
5 autonomous AI coworkers, each with their own agenda. They won't all agree.
P
Priya Shah
Engineering Manager
Wants: Make you decide well — won't make the call for you
Style: Calm, Socratic; pressure-tests your call
D
Devon Rao
Staff Platform Engineer
Wants: Ship on the current schema; surface the real risks
Style: Dry, precise, risk-aware; inspects the code
M
Mara Lindqvist
Product Manager
Wants: Ship the full demo'd experience Friday
Style: Energetic, persuasive, commercial
S
Sam Rivera
SRE
Wants: Won't sign off the SLO until the 429 storm is fixed
Style: Blunt about risk; allergic to optimism without a graph
Jexternal
Jordan Blake
VP Engineering, Contoso
Wants: Certainty on SSO, audit export, and the 99.9% SLA
Style: Polished, direct, busy — the customer
Your workspace
Real tools, pre-seeded with context. You're not roleplaying, you're working.
Code / IDE Kanban board Docs / wiki Email Team chat
Scored on
Decision qualityEvidence usageStakeholder handlingWritten clarity