Engineering Manager
Engineeringmedium15 credits
Your payments vendor is down and blaming you
Transactions are failing, the vendor's status page says 'all systems operational,' and your fallback was never tested.
FNorthstar Academy 4.9 (525) 3,675 taken 30m Engineering Manager
The situation
Your primary payment processor is timing out on 60% of transactions, but their status page is green and their support line insists 'the issue is on your side.' You have a secondary processor wired up but never failed over to it in production. Revenue is dropping, merchants are opening tickets, and your team is split between debugging your own integration and pulling the trigger on the untested fallback.
What you'll practice
Prove where the failure actually is, fast, with evidence
Prove where the failure actually is, fast, with evidence. Show it clearly — with evidence a reviewer can point to.
De-risk and execute (or consciously hold) the fallback
De-risk and execute (or consciously hold) the fallback. Show it clearly — with evidence a reviewer can point to.
Escalate the vendor past the front-line deflection
Escalate the vendor past the front-line deflection. Show it clearly — with evidence a reviewer can point to.
Communicate clearly to merchants without overpromising
Communicate clearly to merchants without overpromising. Show it clearly — with evidence a reviewer can point to.
The room
4 autonomous AI coworkers, each with their own agenda. They won't all agree.
B
Bao
Integrations Engineer
Wants: Convinced it's the vendor; wants to flip to the fallback immediately.
Style: Decisive, frustrated
R
Renata
Senior Engineer
Wants: Worried the untested fallback will double-charge or drop transactions.
Style: Careful, skeptical
Gexternal
Glenn
Vendor Support Rep
Wants: Deflecting blame, slow-walking escalation, won't admit an incident.
Style: Scripted, evasive
P
Priscilla
Head of Operations
Wants: Wants the bleeding stopped and a merchant-facing message in 15 minutes.
Style: Operational, urgent
Your workspace
Real tools, pre-seeded with context. You're not roleplaying, you're working.
Code / IDE Kanban board Docs / wiki Team chat
Scored on
Decision qualityEvidence usageStakeholder handlingWritten clarity