Get SRE Engineers
Site reliability engineers from Brazil, Argentina, and Colombia who eliminate toil, improve observability, and run production systems that actually stay up. They write software to fix operational problems — not just respond to alerts.
Senior SREs in the US earn $170k-$220k. LATAM equivalents deliver at $75k-$115k — significant for high-skill roles with ongoing on-call and incident response responsibilities.
LATAM's UTC-3 to UTC-5 range overlaps 4-8 hours with US teams. On-call rotation is shared without requiring engineers to be available at 3am for a US East Coast incident.
SREs write. Blameless postmortems, runbooks, capacity planning documents, and SLO reports are part of the work. LATAM SREs in our network are disciplined about this.
SRE is fundamentally a software engineering role applied to operations problems. LATAM engineers who move into SRE bring strong coding fundamentals alongside systems experience.
LATAM SREs manage production workloads on AWS, GCP, and Azure with Kubernetes, Terraform, and modern observability stacks. They operate at scale in real environments.
Every candidate completes all five stages before you see their profile. You can also run your own technical round after our screening.
A timed test measuring analytical thinking, pattern recognition, and problem-solving clarity, independent of specific programming language knowledge.
A structured interview assessing communication style, conflict resolution, ownership mindset, and English proficiency in a professional context.
A 90-minute live session covering three areas. First, SLO design: given a service description, candidates define meaningful SLOs, choose appropriate error budget burn rate alerts, and explain how they'd communicate the error budget to the development team. Second, incident simulation: a production service is throwing 500s and latency is spiking — candidates walk through the diagnosis using Prometheus metrics and distributed traces, the mitigation steps, and the postmortem structure. Third, toil reduction: given a description of a manual operational task that runs 10 times a week, they design an automation approach and estimate the ROI against SRE labor cost.
Verification of work history, education, and identity with written consent, aligned with applicable privacy rules including LGPD where relevant.
We speak with at least two professional references who worked with the candidate in an engineering context, not personal contacts.
After our screening, you can optionally run your own technical round before making an offer.
Sample profiles
Anonymized profiles from our vetted talent pool. Actual candidates may vary.
São Paulo, Brazil
4+ years experience
Buenos Aires, Argentina
7+ years experience
Bogotá, Colombia
10+ years experience
Want to see profiles matched to your specific requirements?
Request matched profilesWhat to expect
SRE engineers in our network treat reliability as an engineering problem, not a firefighting problem. They build systems that tell you when something is about to break before it does, automate the work that shouldn't require a human, and document what they learn so the next incident is resolved faster. They use AI tools to speed up runbook generation and incident triage assistance.
AI-assisted runbook generation from incident history — they use Copilot or Claude to create first drafts of runbooks for known failure modes, then refine them with real operational context.
Automated incident triage: they build preliminary investigation bots that query Prometheus and Loki during a PagerDuty alert, so the on-call engineer has context before they're fully awake.
Error budget tracking dashboards are built before the team has burned through the first SLO period. They don't wait for a P1 to start measuring reliability.
Blameless postmortems are written within 48 hours of every significant incident: what broke, why, how it was detected, how it was resolved, and what's being changed to prevent recurrence.
They quantify toil. If a task takes 30 minutes, runs 20 times a month, and can be automated, they build the case, prioritize the automation, and track the hours recovered.
Junior SRE Engineer
Mid SRE Engineer
Senior SRE Engineer
Lead SRE Engineer
FAQ
Related roles
Tell us your current reliability posture and what's breaking. We'll have a shortlist in 3 days.
Prometheus + Grafana
OpenTelemetry (traces, metrics, logs)
Kubernetes (EKS, GKE, AKS)
Terraform / Pulumi
Python / Go (automation scripting)
Bash (operational scripts)
AWS / GCP / Azure