The Engineering Leadership
Scenario & Simulation Library

4-week roadmap, 3 full LLD interview prompts (Rate Limiter, Notification Engine, Key-Value Store), and PR code review rehearsals.

Master scale, failure domains, blast radius, Conway's law, and defending architectural trade-offs under pushback.

SEV1 outage command, post-mortems, negotiating 20% technical debt allocations, and risk pre-mortems.

Master the Altitude Rule, executive BLUF communication, translating technical debt into unit economics, and aligning VP/PM expectations.

Rehearse disagree & commit, cross-functional diplomacy, performance turnarounds, and executive pushback loops.

Start a light but focused conversation about growth, skill-building, and mindset

Counterpart: Raymond Cho (Early-career engineer who's unsure how to grow)

Surface blockers, clarify expectations, and co-create a forward path

Counterpart: Jules Hart (Mid-level engineer unsure how to reach the next level)

Create space for honest frustration, clarify growth signals, and re-engage ownership of the path forward

Counterpart: Noah Tan (Senior engineer who feels overlooked and stagnant)

Run a light 1:1 that builds trust, encourages open sharing, and shows you care

Counterpart: Nina Alvarez (Junior engineer early in their onboarding)

Open the door to conversation about morale, motivation, or personal challenges

Counterpart: Alex Chen (Mid-level engineer who's been quieter and less engaged)

Rebuild trust, open the door for honest conversation, and understand what’s driving the change

Counterpart: Priya Nair (Senior engineer who's emotionally checked out)

Give clear, constructive feedback early without discouraging enthusiasm

Counterpart: Isabel Nguyen (Junior engineer with unclear or sloppy communication)

Give clear, behavior-based feedback and reset tone expectations

Counterpart: Tasha Green (Mid-level engineer with subtle but corrosive communication patterns)

Deliver high-stakes feedback clearly while preserving respect and the potential for change

Counterpart: Renee Walker (Senior engineer whose tone and actions are eroding team safety)

Clear up the confusion, rebuild trust, and clarify communication expectations

Counterpart: Dina Malik (Engineer from a partnering team confused by a recent change)

Acknowledge the tension, reset expectations, and propose coordination improvements

Counterpart: Omar Khan (Tech lead from a parallel team frustrated by repeated coordination issues)

Escalate the technical disagreement respectfully while pushing for resolution

Counterpart: Linda Zhou (Senior engineer from another team pushing an incompatible direction)

Clarify the problem behind the proposal and co-define the ‘why’ before implementation

Counterpart: Zoe Lin (New product manager proposing unclear feature scope)

Raise product–engineering misalignment constructively and advocate for alignment with team or user goals

Counterpart: Marcus Holt (Experienced PM prioritizing features that don’t align with team goals)

Raise the strategic and cultural risks of continuing down a misaligned path — firmly but respectfully

Counterpart: Rohan Mehta (Senior product manager pushing a direction that compromises engineering principles)

Clarify scope and timing without conflict — and build shared expectations

Counterpart: Melissa Shaw (Product manager requesting a fast turnaround)

Negotiate scope or timing while protecting quality and maintaining trust

Counterpart: Daniel Reyes (Product manager asking for timeline cuts to meet a milestone)

Push back on unrealistic pressure while staying calm, professional, and collaborative

Counterpart: Riya Kapoor (Product leader pressing for aggressive delivery at risk to team)

Support her curiosity, ask thoughtful questions, and help her take one next step

Counterpart: Isabelle Nguyen (Junior engineer testing out long-term interests)