Hire me

AWS is green. The product is not. I stay until it is.

AWS status isn’t the outage. Failed failover, a deploy without rollback, the same page again — users failing while the dashboards stay polite.

A deploy without rollback has an answer I reach for: a canary on a Lambda alias. Traffic shifts back. The source layer only moves forward.

For a director, VP, or principal in an active or just-landed incident, or a failover that’s never been proven. Not a Well-Architected slide, not “Amazon will handle it,” not a review with nobody in the pager.

If it’s down: email with LIVE in the subject. First reply is whether I can take it, not incident command from this website. If we start, I join your channel and pager, with access and NDA in the thread. After it holds we harden — a symptom cleared with the cause still in the path is how you get the same runbook, the same people, and the same page next quarter. The same incident should not need you twice.

Taking too long due diligence built in your stack the team runs it
Contract seat corp-to-corp a long engagement no conversion
Standing team an operating cycle, finished
Down now LIVE in the subject I join the pager it holds harden
engraving of a horse-drawn, hand-pumped fire engine in three-quarter view: large spoked wheels, a cylindrical tank, cross-brace pump handles rising at the centre, and a coiled suction hose with its strainer nozzle unrolled in front

Related systems

Start

If it’s down now, tick LIVE on the form.

LIVE — production is down

I’ll tell you in about a day whether I’m the right person. The first conversation is fit, not a free architecture review.