Systems Engineer, AWS Incident Response

As a Systems Engineer on AWS Incident Response, you will be on the front line of AWS incident response. You will lead high-severity calls, triage complex failures across distributed systems, coordinate resolver teams, and drive incidents to mitigation in real time while millions of customers depend on the outcome. Between incidents you will obsess over metrics and detection analysis, building dashboards and mechanisms that surface problems before customers notice, and you will drive operational improvements that make the incident management ecosystem faster and more accurate.

You will make real-time decisions under pressure, deep-diving the largest and most complex technical environment in the world. You will develop expertise across AWS services, networking, and infrastructure, building a breadth of knowledge that few roles offer. Your scope spans all of AWS rather than a single service. You will own operational processes end to end and use data to find the next improvement in how we detect and mitigate faster. You will also have the opportunity to grow your development skills by taking on coding projects that accelerate incident response and reduce toil.

This role includes participation in an on-call rotation covering weekdays, weekends, and holidays. On-call shifts fall within your local daytime hours.


Key job responsibilities
- Lead high-severity incident response calls end to end: assess impact, coordinate resolvers across AWS service teams, communicate clearly under pressure, manage escalations, and drive the incident to mitigation with documentation throughout.
- Own and run operational health reviews, and build and maintain the dashboards, metrics, and monitoring that surface trends before they become incidents.
- Improve detection accuracy and speed. Identify patterns across events and build proactive mechanisms that prevent recurrence.
- Deep-dive operational data to find systemic issues, measure response effectiveness, and prioritize improvements against what the data shows is degrading.
- Identify gaps in operational processes, documentation, and tooling, and build or improve mechanisms that reduce time-to-detection and time-to-mitigation.
- Apply scripting, automation, and generative AI to accelerate incident response and reduce toil, including where AI can augment human judgment during an incident or surface insight from operational data at scale.
- Work with service teams so that learnings from each incident drive corrective actions to completion, closing the loop between what broke and what gets fixed.
- Mentor peers in your areas of technical and operational strength.

A day in the life
When you are on call, incidents take priority. You join the incident bridge, assess the scope of impact from real-time metrics and dashboards, engage the resolver teams that own the affected services, and drive the event to mitigation, escalating when progress stalls. Off-call, you work to reduce time-to-detection and time-to-mitigation: deep-diving recent events for detection that lagged the impact or alarms that trigger without customer impact, correcting the signal behind them, leading operational health reviews, driving other teams' corrective actions to completion, and owning projects that strengthen AIR's detection and incident management, including automation you can build yourself.

About the team
AWS Incident Response (AIR), part of the AWS Resilience organization, ensures high availability of AWS. When major incidents hit, AIR leads the response, coordinating resolver teams across AWS and driving mitigation. We move fast, but not carelessly, obsessing over observability of the cloud and continuously improving our detection and response speed and accuracy. Each incident feeds improvements to our detection, processes, and tooling, making the next one shorter or preventing it entirely. This is a high-visibility, high-impact role with a global view of AWS health that few teams get to see.