Dear Hiring Manager,
After several years in an adjacent role, I am moving deliberately into site reliability engineer work because the strongest part of my recent job has been SLO design, production debugging, automation, capacity planning, and blameless incident follow-up. Over the last year I have built hands-on evidence with Go, Python, Linux, Kubernetes, Prometheus, Grafana, Terraform, and incident review practices, so this is a planned move rather than a loose interest.
I am not asking you to infer the connection between my old title and 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 chance to talk through how this transition maps to your team needs. 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