Dear Hiring Manager,
I have been contracting on reliability and platform work and I am now looking for a permanent SRE role where I can own the systems past the first quarter. Short engagements sharpened my ability to learn a service map quickly, but reliability is a long game and I want to be there for the slow improvements. On my last contract I added SLO dashboards, tightened alert routing, and helped reduce noisy pages while keeping coverage for real incidents.
Contracting forced me to understand an unfamiliar production estate fast, read the dashboards, and find the noisy alerts within days, and that skill transfers cleanly into a permanent seat. Your team needs service ownership, observability people trust, steady incident response, automation, and honest reliability trade-offs, which is the work I keep being brought in to do. What I want now is to stay long enough to see error budgets settle and to fix the root causes rather than patch and move on.
That work used Go, Python, Linux, Kubernetes, Prometheus, and Grafana, but the value was in cutting alert noise without dropping real coverage. I tuned the routing so the on-call rota stopped chasing false alarms, tied the dashboards to clear SLOs, and ran the change through a blameless review so the team understood the reasoning. Permanent work means I get to keep refining that instead of handing it to whoever comes next.
I would value a conversation about the reliability measures that worry you most right now and where you would point me first. SRE teams need evidence that reliability work improves systems without slowing product delivery, so I will keep this short and let the alerting work speak for itself.
Yours sincerely, Alex Morgan