October 17, 2026
Dear [Hiring manager's name],
I define and operate SLOs for 22 services on a freight-tracking platform handling 40,000 requests per second at peak, and for the last three years that platform has held 99.98% availability for 12 million monthly users. I'm applying to [Company name] because reliability at that scale is a discipline, not a department, and it's the discipline I've built my career on.
Wiring automated diagnosis and runbook execution into our paging workflow brought MTTR down from 45 minutes to 9, and Go-based operators I built for certificate rotation and deploy verification return roughly 30 engineer-hours a week to product teams. An error-budget policy I instituted froze feature deploys twice last year, both times to fix issues that would have caused repeat outages otherwise.
I run quarterly chaos game days across 18 services with Litmus, which surfaced 11 resilience gaps we closed before any customer saw them, and I hold a Certified Kubernetes Administrator credential alongside an AWS Solutions Architect Associate certification. I write the postmortems myself and chase every action item to done, not just to assigned.
I'd welcome a conversation about the reliability goals behind [Company name]'s platform and where eight years of treating uptime as an engineering discipline could help. I'm available for an interview at your convenience. Thank you for your time and consideration.
Sincerely,
Marco Wright
