Incident Response
claim element
Diagnosing production issues under pressure and closing the loop with a post-mortem.
cited in: 2 proving documents · 1 companies
proving documents
Responding to a production incident with the missing architecture decision, not just a patch
Root-caused a customer-blocking production incident to an undocumented architecture assumption, rebuilt the affected consumer with a post-mortem, an ADR, and business-rules documentation, then, after rollout exposed a database deadlock, diagnosed it to a Kafka partitioning mismatch and replaced silent message loss with retry, a dead-letter queue, and per-user serialization.
Correcting production data safely with reversible, auditable tooling
Corrected tens of thousands of corrupted production records (~33k in one case) with no maintenance window, using reusable CLI commands with dry-run, rollback files, batch auditing and event re-publishing, a "correction command" pattern the team then reused.
exercised at