Copy-ready job description
Edit the bracketed fields for your requirement.
Site Reliability Engineer
About the role
We are looking for a Site Reliability Engineer to join our team. You will define and track service level objectives.
Responsibilities
- Define and track service level objectives.
- Respond to incidents and write post-incident reviews.
- Automate toil and improve observability.
- Plan capacity and test failure modes.
- Work with developers on reliable design.
Required
- Linux
- Kubernetes
- Observability (Prometheus, Grafana, Datadog)
- Incident response
- Python or Go
Preferred
- Terraform
- SLOs and error budgets
- AWS or GCP
- Chaos engineering
Tools and stack
Kubernetes, Prometheus and Grafana, Datadog or similar, Terraform, Python or Go, PagerDuty or similar
Employment type: [Contract / W2 / C2C / Full-time]
Location: [City, ST / Remote]
Duration: [months]
Work authorization: [accepted types]Responsibilities explained
Each responsibility maps to something a candidate should be able to describe.
- Define and track service level objectives.
- Respond to incidents and write post-incident reviews.
- Automate toil and improve observability.
- Plan capacity and test failure modes.
- Work with developers on reliable design.
Required skills
Treat these as the screen. If a candidate cannot speak to them, they are rarely a fit.
- Linux
- Kubernetes
- Observability (Prometheus, Grafana, Datadog)
- Incident response
- Python or Go
Preferred skills
Use these to rank candidates who meet the required list.
- Terraform
- SLOs and error budgets
- AWS or GCP
- Chaos engineering
Other titles this role appears under
Search and post under the variants your clients use.
- Site Reliability Engineer
- SRE
- Production Engineer
Seniority guide
Pick the level you need and state it plainly in the posting.
- Junior: handles alerts with runbooks.
- Mid: improves monitoring and owns services.
- Senior: sets SLOs, leads incidents and designs resilience.
Tailoring a resume to this description
When you submit a consultant, mirror the required skills and tools in the summary and the most recent role, using only experience the candidate really has. MatchWire’s resume tailoring drafts this from the candidate’s stored work history and the posting.
Frequently asked questions
How long should a job description be?
Long enough to list the responsibilities, required and preferred skills, tools and logistics, usually 300 to 500 words.
Should I list a rate in the description?
If the client allows it, a range helps candidates self-select. Otherwise state it as “rate to be discussed” and confirm it before submitting.