Senior SRE: Observability & Incident Response

EPAM Systems

México

On-site

MXN 900,000 - 1,300,000

Full time

40 hours ago

Be an early applicant

Application generator

Turn this role into an interview — a resume and cover letter built around what this employer wants.

Get past ATS filters

Benefits offered by this job

Healthcare benefits

Paid time off

Upskilling and certification courses

LinkedIn Learning access

Global career opportunities

Volunteer and community involvement

Job summary

EPAM Systems is seeking a Senior Site Reliability Engineer to maintain and enhance a Java services ecosystem, strengthening reliability, observability, and operational readiness. You will partner with engineering stakeholders, participate in on-call rotations, and drive measurable improvements to SLOs.

The role requires hands-on AWS experience, strong incident response skills, and solid observability capabilities.

Qualifications

3+ years of SRE/DevOps experience supporting production services.
On-call support experience for backend service ecosystems.
Proven incident response skills using logs and telemetry to find root causes.
Hands-on Amazon Web Services experience.
DynamoDB experience.
ElastiCache experience.
Git for contributing and reviewing code changes.
Gradle knowledge in Java service environments.
Observability and troubleshooting skills in distributed systems.
Clear written communication skills for live incident updates.
Fast learning ability to absorb information quickly under pressure.
English proficiency: B2 Upper-Intermediate.

Responsibilities

Provide on-call support for Java backend services during business hours.
Troubleshoot complex distributed system issues using logs and telemetry.
Identify root causes and drive incident resolution through actionable changes.
Prepare and deploy patches to address cloud infrastructure issues.
Define and improve service metrics and dashboards to assess platform health.
Improve reliability and observability posture for key services.
Create and refine runbooks to standardize operational response.
Track and improve SLOs through repeatable processes.
Submit code changes that improve SLOs when errors occur.
Communicate operational issues clearly and concisely in writing during incidents.