Describe a time you worked on a high-stakes, time-sensitive incident under intense scrutiny.

In Simple Words: Highlight emotional regulation: stay calm, designate clear roles (Incident Commander vs Investigators), communicate on regular cadences, and focus on fast customer mitigation over premature root cause exploration.

The STAR Response:

• Situation: On Cyber Monday morning, our order payment webhook service stopped processing incoming charge confirmations from Stripe, causing thousands of customer orders to remain stuck in "Pending Payment" status while executive leadership was monitoring real-time dashboards.
• Task: Restore payment processing immediately, clear the backlog of stuck orders, and keep leadership informed without getting distracted from the technical fix.
• Action:
  1. Stepped up as Incident Commander: appointed a dedicated communications lead to update executive stakeholders every 15 minutes, allowing investigators to focus on the code without interruptions.
  2. Examined telemetry and discovered that a newly deployed IP allowlist was blocking Stripe's rotated webhook IP addresses.
  3. Rather than writing code under pressure, executed an immediate rollback to the previous known-good deployment, restoring webhook ingestion within 8 minutes.
  4. Ran an idempotent replay script to process the 4,200 queued webhook events safely with zero duplicate charges.
• Result: Fully recovered within 22 minutes with zero lost transactions or revenue impact. Executive leadership praised the calm, structured communication and transparent post-mortem.

Practical Script & Summary Template

### High-Stakes Incident Command Roles:
- **Incident Commander (IC)**: Directs the technical response, assigns investigation leads, and approves rollbacks.
- **Operations Lead**: Executes commands, monitors logs, and runs rollback scripts.
- **Communications Lead**: Posts structured updates to stakeholders every 15-30 minutes, protecting engineers from external pings.