Staff-Level Narratives

Story Formula

Use this shape:

1. Context: system, scale, stakes.
2. Problem: failure mode, ambiguity, customer or team impact.
3. Constraints: time, risk, politics, legacy, capacity.
4. Action: your specific decisions and technical contribution.
5. Leadership: how you aligned people or changed the operating model.
6. Result: metrics and durable change.
7. Reflection: what you would do differently.

Story 1: Incident Leadership

Prompt:

“Tell me about a major incident.”

Answer targets:

• You established command structure.
• You separated mitigation from root cause.
• You communicated on a cadence.
• You used evidence, not guesswork.
• You produced prevention work after recovery.

Punchline:

The durable win was not that we recovered. It was that the same failure class stopped paging us.

Story 2: Automation With Guardrails

Prompt:

“Tell me about automation you built.”

Answer targets:

• Manual workflow was frequent or risky.
• You measured toil or incidents.
• You built dry run, prechecks, rollback, and audit.
• You started narrow and expanded after trust.

Punchline:

I treated automation as a production system, not as a script.

Story 3: Deep Debugging

Prompt:

“Tell me about a hard technical problem.”

Answer targets:

• You moved through layers methodically.
• You falsified hypotheses.
• You found a root cause below the obvious abstraction.
• You added observability or validation afterward.

Punchline:

The symptom was at the service layer, but the cause was in the substrate. I kept narrowing until the evidence matched one layer.

Story 4: Cross-Team Alignment

Prompt:

“Tell me about a disagreement.”

Answer targets:

• You understood incentives.
• You clarified shared goals.
• You made tradeoffs explicit.
• You created a standard or contract.

Punchline:

I did not try to win the argument. I reframed it around the operational invariant we all needed to preserve.

Story 5: Raising The Bar

Prompt:

“Tell me about improving engineering quality.”

Answer targets:

• You changed defaults.
• You created checks, templates, tests, or runbooks.
• Adoption happened beyond your immediate work.
• Metrics improved.

Punchline:

The bar moved because the better path became the easier path.