Sr. SRE Engineer

Language View profile Search by Keyword Search by Location Search by Postal Code Show More Options Clear Select how often (in days) to receive an alert:

Sr. SRE Engineer

Date: 15 Oct 2026 Company: QualityAI Country/Region: AR

Are you interested in working with the World’s leading AI-powered Quality Engineering Company? Ready to advance your career, team up with global thought leaders across industries and make a difference every day? Join us at QualityAI We are looking for a Sr. SRE Engineer to join our growing team in Argentina/Mexico

Location

Argentina/Mexico (remote)

This is the role specification for a senior reliability leader who can combine SRE discipline, platform operations, and automation-first thinking across the NewLeaf Azure application estate.

Role Summary

• We are hiring a hands-on SRE Lead to own reliability across the full NewLeaf application platform on Azure.
• This role covers customer-facing websites, backend services, APIs, integrations, event-driven workflows, observability, incident management, self-healing automation, on-call operations, and operational reporting.
• The goal is to build a resilient operating model for the entire product ecosystem, not just the underlying cloud infrastructure.

What "Platform" Means Here

• Public and internal websites
• Backend services and APIs
• Azure-hosted application workloads
• Integrations and event processing
• Monitoring, alerting, dashboards, and reporting
• Incident response, postmortems, and reliability improvements
• Runbooks, operational standards, and self-healing automation
• On-call rotation design and engineering readiness

Primary Responsibilities

• Define the reliability strategy for the NewLeaf platform and keep it aligned with business priorities.
• Own incident detection, triage, escalation, communication, and post-incident follow-through.
• Build operational dashboards that show service health, user impact, and reliability trends.
• Design self-healing and auto-remediation workflows for recurring failure modes.
• Create and maintain runbooks, playbooks, and a living reliability rulebook.
• Design and support a sustainable on-call rotation model for engineering teams.
• Drive root-cause analysis and convert recurring issues into permanent fixes or automation.
• Partner with application, integration, and platform teams to reduce operational risk across boundaries.

Required Skill Set

• Strong SRE or platform engineering background with direct ownership of production systems.
• Deep incident management experience, including severity classification, incident command, and postmortem rigor.
• Practical observability expertise across logs, metrics, traces, dashboards, alerting, and service health reporting.
• Ability to build or influence automation for detection, triage, remediation, and follow-up tasks.
• Experience shaping on-call practices, escalation paths, and team readiness.
• Comfort operating across application services, integrations, asynchronous processing, and release workflows.
• Clear communication skills for translating technical risk into operational and executive language.
• Ability to coach engineers and raise the maturity of a team without creating unnecessary process overhead.

Azure and Platform Stack Familiarity

• Microsoft Azure operations and governance.
• Azure Monitor, Application Insights, and Log Analytics.
• Azure Service Bus, Event Grid, Event Hub, and timer-driven/background processing patterns.
• Azure Functions, App Service, and other cloud-hosted application runtimes.
• Key Vault, Storage, and identity-aware service configuration.
• CI/CD pipelines and safe deployment practices, including release validation and rollback readiness.
• Infrastructure-as-code tooling such as Bicep or Terraform, where used by the team.
• Kusto Query Language and operational reporting from telemetry data.

Agentic Operations and Automation

• Use agents or automation to assist with analysis, incident summarization, runbook execution, and follow-up work.
• Treat automation as a reliability control, not a novelty layer.
• Apply safety checks, approvals, logging, and rollback paths before any automated remediation is allowed to act on production systems.