About
I'm a DevOps engineer with deep experience in disaster recovery across cloud-native environments.
Over the years I've helped teams move from untested DR plans to systems that hold up under real conditions — cross-region AWS infrastructure, automated failover, runbooks that make recovery predictable, and the operational discipline to keep it that way.
My background covers infrastructure automation, AWS architecture, and the gap between theory and practice that shows up in every DR engagement. I work with engineering teams directly — not as an auditor, but as someone who's been in the same on-call rotation.
Approach
Good DR work is mostly about asking the right questions early: What breaks first? Who decides when to fail over? How long does recovery actually take, not in theory but when someone's hands are shaking? The answers shape everything.
I focus on recovery systems that are simple enough to execute under pressure, tested regularly enough to stay accurate, and documented well enough that anyone on the team can use them.