Dear Reddit Talent Acquisition team,
I would like to apply for the Site Reliability Engineer role you have open on your careers page. My work over the past several years has been in site reliability work, and I would be glad to put it to work for your team.
Before writing I looked into Reddit, and what stood out was your push to cut downtime and the engineering write-ups your team keeps posting on running blameless postmortems. This strikes me as a good moment to join, and I would gladly put my site reliability work experience behind that effort.
Reading the job description, the three things you need most for this role are SLOs and error budgets, incident response and on-call and monitoring and automation. Those decide whether an SRE hire works out, and I have real results against each.
On SLOs and error budgets, my toolkit is SLIs, SLOs and error budgets. As a Site Reliability Engineer at Dropbox, I handled setting SLOs across the top services and cutting alert noise by tying pages to error budgets. Beyond that, I wrote the reliability runbooks the whole on-call team now works from.
For incident response and on-call, I turn to PagerDuty, runbooks and blameless postmortems. During my time as a Site Reliability Engineer at Dropbox, I took on leading the on-call rotation and bringing mean time to recovery from an hour down to 15 minutes.
On monitoring and automation, I draw on Grafana, Python and Kubernetes. Working as a Site Reliability Engineer at Dropbox, I owned automating the toil out of deploys, cutting manual steps from 20 to 2. On top of that, I built the dashboards that catch a failing service before customers notice.
I would be glad to talk any of this through in an interview and show you why I fit. I am ready to keep your systems reliable and your on-call calm, and to grow with the team.
I hope we can set up a time to talk.
Yours sincerely,
Theo Script
theo.script@gmail.com