Job description template

Site Reliability Engineer

You will help build and run reliable systems by owning the reliability lifecycle: monitoring, incident response, and continuous improvements to availability, performance, and operational excellence. This is a hands-on Site Reliability Engineer role where you work independently on well-defined work and partner with engineering teams to reduce risk and prevent recurring issues.

Responsibilities

Own key service reliability components, including alerting, dashboards, and operational runbooks
Participate in incident response (triage, mitigation, communication, and post-incident follow-ups) to restore service and reduce recurrence
Design and implement reliability improvements across infrastructure and application dependencies
Work with engineering teams to improve observability and troubleshoot production issues using logs, metrics, and traces
Proactively identify reliability risks (capacity, dependency failures, deployment regressions) and propose mitigations
Automate operational tasks and implement safe rollouts to reduce manual effort and increase consistency
Document operational processes and contribute to knowledge sharing to raise team operational maturity

Must-have qualifications

Hands-on production experience operating and improving monitoring/alerting using metrics and logs
Proven experience troubleshooting distributed systems in production using observability signals
Experience with incident response, including root-cause analysis and post-incident action planning
Working knowledge of reliability engineering practices (SLOs/SLIs, error budgets, or equivalent reliability metrics)
Experience improving reliability through automation (runbooks, tooling, or self-healing patterns)
Competence with cloud infrastructure operations and basic reliability concepts (deployments, networking, capacity, or failure modes)

Nice to have

Experience with SLO/SLA management and reliability reporting for engineering teams
Hands-on experience with common reliability tooling (e.g., incident management, alert routing, or log aggregation platforms)
Knowledge of CI/CD deployment reliability practices (canaries, progressive delivery, rollback strategies)
Experience contributing to engineering culture around blameless postmortems and operational excellence

What success looks like in 12 months

Reduce incident impact through better detection and faster triage
Increase reliability by preventing recurring failures
Improve observability coverage and actionability
Operationalize reliability practices with measurable service targets
Increase resilience of deployments and reduce operational toil

Logistics

Full-time (40 hours a week), remote from Latin America.
Working hours overlap with US business hours.

About the company

[About your company: what you build, your stage and team size]

Want it tailored to your stack, seniority and time zone?

Customize with the free generator →

Interview scorecard

Score every candidate against the same bar

Improve and maintain system reliability by enabling fast detection, safe mitigation, and continuous prevention of incidents.

Outcomes to measure

What this hire should deliver in the first year. Replace [N] with your own targets.

Reduce incident impact through better detection and faster triage. Measure: achieve [X]% reduction in mean time to acknowledge (MTTA) and [Y]% reduction in mean time to restore (MTTR) for priority services over the first 12 months
Increase reliability by preventing recurring failures. Measure: reduce repeat incident volume for the top [N] incident drivers by [X]% within 12 months, using post-incident action tracking
Improve observability coverage and actionability. Measure: instrument [N] critical user journeys and key dependencies with actionable dashboards/alerts; maintain alert coverage for [X]% of defined SLI signals
Operationalize reliability practices with measurable service targets. Measure: define or refine SLO/SLI coverage for [N] services and establish reliable reporting cadence (e.g., monthly); achieve [X]% adherence to target alerting based on SLO burn-rate thresholds or equivalent reliability metrics
Increase resilience of deployments and reduce operational toil. Measure: automate or standardize at least [N] recurring operational tasks/runbooks and reduce manual operational interventions by [X]% during high-change periods

Competencies and weights

What to evaluate, how much it counts and what a strong answer looks like.

Observability mastery · 23%
Reliability work depends on using metrics, logs, and traces to detect issues early and guide remediation. Evaluated in Round 1.

Weak: Uses dashboards inconsistently or can describe tools without explaining how signals drive decisions
Meets the bar: Explains alert design and can connect observed metrics/logs to probable failure modes
Strong: Designs/updates alerts and dashboards with clear thresholds and ownership, demonstrates signal-to-decision reasoning, and distinguishes noise from actionable events

Production troubleshooting · 21%
A mid-level SRE must independently diagnose complex, distributed incidents using evidence-based debugging. Evaluated in Round 1.

Weak: Relies on speculation or broad steps without narrowing hypotheses using observability evidence
Meets the bar: Leads structured troubleshooting (hypothesize → test → confirm) using logs/metrics/traces and dependency thinking
Strong: Rapidly isolates faults across service boundaries, validates causality with evidence, and proposes the next best mitigation or verification step

Incident response rigor · 19%
Consistent incident leadership and post-incident follow-through are core to reducing recurrence and restoring trust. Evaluated in Round 2.

Weak: Focuses only on immediate fixes without clear communication or corrective action planning
Meets the bar: Runs disciplined triage, communicates clearly, and documents post-incident learnings and actions
Strong: Leads blameless incident review, identifies contributing factors beyond symptoms, and drives tracked improvements with measurable outcomes

Reliability engineering practices · 17%
SLO/SLI-style thinking aligns work to customer impact and enables quantitative reliability management. Evaluated in Round 2.

Weak: Understands reliability concepts but cannot map them to measurable targets and operational behaviors
Meets the bar: Can explain how SLIs/SLOs/err budget (or equivalent) connect to alerting and prioritization
Strong: Builds or improves reliability targets and uses them to guide alerting, escalation, and roadmap decisions with clear tradeoffs

Automation and runbooks · 12%
Automation reduces toil and standardizes response, enabling safer changes and faster recovery. Evaluated in Round 3.

Weak: Improves reliability with ad-hoc scripts and incomplete documentation
Meets the bar: Creates or refines runbooks, automates routine checks, and reduces reliance on tribal knowledge
Strong: Implements robust automation with safeguards, clear failure modes, and demonstrable reductions in manual operational work

Cloud operations mindset · 8%
SREs must understand infrastructure failure modes to design practical mitigations and safe rollouts. Evaluated in Round 3.

Weak: Can describe cloud services but struggles to connect them to reliability and failure modes
Meets the bar: Explains how networking/capacity/deployments impact reliability and how to validate hypotheses
Strong: Proactively designs around infrastructure constraints and failure modes; describes safe rollout/rollback strategies and capacity planning approaches

Interview questions

Questions for every interview round

Each round has an owner, a time box and questions that test the competencies above.

Round 1: Observability & Troubleshooting
Senior SRE · 45 min

Tell us about a production incident you troubleshot. What signals (metrics/logs/traces) did you use first, and how did those observations shape your next hypotheses?
Describe how you design or improve monitoring/alerting. How do you choose thresholds, reduce alert noise, and ensure alerts are actionable by the right team?
Give an example of how you traced an issue through service dependencies. What evidence did you use to confirm causality rather than correlation?

Round 2: Incident Response & Reliability Practices
Engineering Manager, Reliability · 45 min

Walk through your approach to incident response from detection to post-incident follow-up. What do you do to keep communication clear and the team aligned?
Describe a post-incident review you contributed to. How did you identify root causes vs. contributing factors, and how did you ensure action items were completed and validated?
How have you used SLO/SLI-style thinking (or an equivalent reliability metric framework) to prioritize reliability work? Describe how it influenced alerting or engineering decisions.

Round 3: Automation & Cloud Reliability
Staff SRE · 45 min

Describe an automation you built or significantly improved (runbook tooling, checks, self-healing, or deployment safety). What problem did it solve, and how did you validate it worked reliably?
Tell us about a time you improved deployment or operational safety (canary/progressive rollout, rollback strategy, or reducing manual steps). What failure modes did you account for?
How do you ensure runbooks and operational documentation stay current after changes? Give an example of how you measured or observed the improvement.

Red flags to watch for

Relies on guesswork during troubleshooting without evidence from monitoring/observability signals
Cannot describe how alerts are made actionable or how alert noise is managed
Treats incidents as purely reactive work without driving measurable prevention through follow-ups
Views reliability only as tooling rather than engineering practices tied to customer impact (e.g., SLO-style thinking or equivalent)

How much does it cost to hire a Site Reliability Engineer in Latin America?

In 2026, a senior Site Reliability Engineer in Latin America costs $7,375 to $8,375 a month all-in, versus $14,250 in the US: up to 48% less. Mid-level starts at $4,875.

Country

Mid-level

Senior

Argentina

$4,875

$7,375

Brazil

$5,375

$8,125

Colombia

$4,875

$7,375

Mexico

$5,625

$8,375

United States

$11,625

$14,250

Monthly cost in USD, all-in: the talent's salary plus Teilur's flat 20% fee, from our 2026 rates. The United States row shows what the same role typically costs there.

Compare costs in the calculator →

Frequently asked questions

What does a Site Reliability Engineer do?

Typical responsibilities include: own key service reliability components, including alerting, dashboards, and operational runbooks; participate in incident response (triage, mitigation, communication, and post-incident follow-ups) to restore service and reduce recurrence; design and implement reliability improvements across infrastructure and application dependencies. The full list is in the template above.

How much does it cost to hire a Site Reliability Engineer in Latin America?

In 2026, a senior Site Reliability Engineer in Latin America costs $7,375 to $8,375 a month all-in, versus $14,250 in the US: up to 48% less. Mid-level starts at $4,875.

Can I customize this Site Reliability Engineer job description?

Yes. Teilur's free Job Description & Scorecard Generator rewrites it for your stack, seniority, time zone and hiring urgency in about 15 seconds. No sign-up needed.

Book a Free Consultation

Site Reliability Engineer Job Description Template