SRE
SLOs that page on user pain, runbooks people follow at 3 a.m., and postmortems that change something.
Open to SRE, platform and security engineering roles
I keep production up and access tight.
Site reliability, DevSecOps and identity engineering. I build the guardrails that let teams ship daily without handing everyone admin.
Reliability and security fail together. I work across all four so the fixes don't fight each other.
SLOs that page on user pain, runbooks people follow at 3 a.m., and postmortems that change something.
Infrastructure as code from the first commit, pipelines that finish in minutes, environments anyone can recreate.
Signed builds, scanned images and policy checks in CI, so security review happens before merge.
Least privilege people can live with: SSO everywhere, short-lived credentials, access that expires on its own.
Replaced standing admin roles with time-boxed, approved access requested from Slack and logged end to end.
Rebuilt paging around error budgets so on-call wakes up for customer pain, not CPU graphs.
Every container that reaches production is built in CI, scanned, signed and checked at admission. Nothing else gets scheduled.
1:30 · Pitch
Ninety seconds on my background, the problems I like, and the roles I'm looking for.
Walkthroughs and deep dives →youtubeId to publish this video.The answers to the first-call questions, so we can spend that call on the role.
Replace these, then set sample: false:
src/data/profile.tssrc/data/resume.tssrc/content/projects/just-in-time-aws-access.mdsrc/content/projects/signed-supply-chain.mdsrc/content/projects/slo-burn-rate-alerting.mdsrc/content/videos.json (4)