Skip to main content

About the role

Overview: In this role, you will lead high-severity incident response and own the data pipelines that enable reliable AI cloud services. You’ll work closely with cross-functional teams to identify failure patterns, track corrective actions, and drive improvements in on-call readiness. You’ll build and maintain data streams for incident reporting and run trend analyses that inform leadership priorities. This position combines hands-on data engineering with operational excellence to reduce customer impact and strengthen reliability. You will use modern AI tools to speed analysis and documentation, shaping scalable reliability practices across the platform. Compensation / Benefits equity benefits remote work options competitive base salary career growth opportunities global or hybrid work environment
Responsibilities: Serve as incident commander for high-severity incidents, coordinating responders across teams through mitigation and recovery Build and maintain data pipelines that collect incident, alert, and change data into a clean, queryable source for reliability reporting Run incident trend analysis to identify recurring failure patterns, regressions in time-to-detection (TTD), time-to-mitigation (TTM), and time-to-resolution (TTR), and identify services driving customer impact Translate trend findings into prioritized recommendations for engineering leadership and track corrective actions to completion Strengthen operational excellence practices (runbooks, on-call readiness) using data-driven insights Lead postmortem reviews and operational health forums, driving clear owners and follow-up actions
Key requirements: 5+ years of experience in data engineering, incident management, or a closely related engineering role Bachelor's Degree or equivalent experience Strong data engineering skills in SQL and Python with experience building and maintaining pipelines for operational reporting Proven ability to analyze incident trends and present findings used to prioritize reliability work Hands-on experience with incident management platforms (e.g., PagerDuty, Rootly, ServiceNow) and dashboarding tools (Tableau, Grafana, Databricks) Experience facilitating blameless postmortems or operational reviews and ensuring follow-up actions Clear, calm communication with engineers, leadership, and stakeholders during high-pressure incidents Hands-on experience with AI tools to accelerate analysis, debugging, and documentation clear communication calm under pressure cross-functional collaboration SQL Python data pipeline development

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this