Dear Hiring Manager,
I am returning to work after a planned career break and targeting site reliability engineer roles where my previous experience in SLO design, production debugging, automation, capacity planning, and blameless incident follow-up is directly useful. During the break I kept current through focused practice with Go, Python, Linux, Kubernetes, Prometheus, Grafana, Terraform, and incident review practices and rebuilt a recent sample around added SLO dashboards, tightened alert routing, and helped reduce noisy pages while preserving coverage for real incidents.
The break has not changed the way I approach the core work of this role. Your team needs service ownership, observability, incident response, automation, and reliability tradeoff judgement, and my strongest examples sit in that exact area. I would use this letter to show the connection with one specific project, the constraints I worked under, and the judgement I brought to the decision points.
A recent example is that I added SLO dashboards, tightened alert routing, and helped reduce noisy pages while preserving coverage for real incidents. That work required Go, Python, Linux, Kubernetes, Prometheus, Grafana, Terraform, and incident review practices, but the more important point is how I made decisions, explained tradeoffs, and followed the result through after release.
I would welcome the opportunity to discuss the role and the recent work I can show now. SRE teams need evidence that reliability work improves systems without slowing product delivery, so I would keep the letter concise, evidence-led, and tied to the outcomes the hiring team is likely to care about.
Yours sincerely, Alex Morgan