Incident Response
Diagnosing production issues under pressure and closing the loop with a post-mortem.
evidenced in: 2 case studies · 1 companies
proving documents
The role-binding incident—and the separate deadlock found later
A role-cleanup change I implemented treated a user's access as global and removed it across workspaces. I owned the incident response, documented the missing rule, and led the architecture direction for a replacement consumer built by the squad. Months later, I traced a separate deadlock to Kafka partitioning and contributed per-user locking and recoverable failure handling; the later error rate was not measured.
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