Dear Hiring Manager,
After several years in an adjacent role, I am moving deliberately into devops engineer work because the strongest part of my recent job has been deployment automation, cloud infrastructure, container platforms, monitoring, and operational handover. Over the last year I have built hands-on evidence with Terraform, GitHub Actions, Docker, Kubernetes, AWS, Prometheus, and secrets management, 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 CI/CD judgement, infrastructure-as-code discipline, observability, and careful release support, 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 standardised a deployment pipeline, added rollback gates, and reduced failed releases across three services. That work required Terraform, GitHub Actions, Docker, Kubernetes, AWS, Prometheus, and secrets management, 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. DevOps hiring teams look for platform changes that make delivery safer for other engineers, 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