Incident Manager

Databricks · United States · Support · listed June 30, 2026

The shape of it

Seniority
Manager
Experience asked
5+ years
Where
Remote
Stated pay
$103,900 – $145,525 USD
Requirements listed
9
Length
866 words

In the posting’s own words

As an Incident Manager, you will lead Databricks’ most critical production incidents while providing clear, accurate, and timely communication to customers, executives, and engineers. You’ll serve as both incident commander and reliability engineer; orchestrating multi-team responses, driving real-time status updates, and partnering with engineering to analyze and prevent failures. Your work will ensure Databricks maintains not only technical resilience but also customer and stakeholder confidence during high-impact events.

What it asks for · 9

  • 5+ years of experience in incident management, site reliability engineering, or production operations supporting large-scale, cloud-native systems.
  • Proven ability to lead and coordinate high-severity incidents, including identifying impact, isolating fault domains, and managing multi-team response efforts.
  • Strong understanding of cloud infrastructure (AWS, Azure, or GCP) — including compute, networking, storage, and observability components.
  • Deep expertise in log analysis and debugging:
  • Familiarity with log aggregation and search tools (e.g., Datadog, Elasticsearch, Splunk, Cloud Logging, or OpenTelemetry).
  • Hands-on experience with observability systems — metrics, logging, and tracing frameworks (Prometheus, Grafana, OpenTelemetry, etc.).
  • Proficiency in at least one major programming or scripting language (Python, Go, or Bash) for automating diagnostics, data collection, or analysis.
  • Excellent contextual interpretation and writing skills, as well as the ability to effectively summarize and communicate to both technical and business audiences, are required.
  • BS, Master's or other advanced degree in Computer Science or Computer Engineering, or related Engineering field.

What the job covers

  • Lead critical incidents — coordinate multi-disciplinary response efforts across Databricks’ cloud-based services to rapidly mitigate impact and restore operations.
  • Drive technical root cause analysis and reliability improvements:
  • collaborate with engineering teams to trace and document underlying causes across distributed systems, services, and data stores.
  • Summarize key learnings, clearly communicate action items, and ensure that technical and procedural improvements are followed through.
  • Own communications during incidents — deliver frequent, high-quality updates to internal stakeholders (executives, engineering leadership, support) and compose and publish customer-facing notifications that are accurate, timely, and empathetic.
  • Mentor and train peers in both incident communication and technical response disciplines to raise the overall quality of Databricks’ incident response.

Degree language

  • BS, Master's or other advanced degree in Computer Science or Computer Engineering, or related Engineering field.

Tools and skills named

Cloud & infra
  • Observability2×
  • AWS
  • Azure
  • Datadog
  • Distributed systems
  • GCP
  • Grafana
  • Prometheus
  • Site reliability
Data
  • Databricks5×
  • Elasticsearch
Languages
  • Bash
  • Go
  • Python
Product & design
  • User experience

Words the posting leans on

  • incident12×
  • engineering7×
  • technical7×
  • data6×
  • communication5×
  • response5×
  • systems4×
  • analysis3×
  • customers3×
  • engineers3×
  • ensure3×
  • experience3×
  • impact3×
  • improvements3×
  • infrastructure3×
  • lead3×

Counted from the posting after the mission statement and the legal notices are set aside. The ones near the top are the ones a screener is looking for.

The posting, your resume, and the gaps between them. One click loads all three.

More open at Databricks

every open role at Databricks

How this page was made

An automated read of a public job posting, fetched August 29, 2026 and last changed by Databricks on August 18, 2026. Every list above is pulled from the posting’s own sentences — nothing rewritten, nothing added, no judgment about the role or the company. Counts and seniority are read off the text by rule, so they can be wrong where the posting is unusual. The original is the only thing that binds. Openings close without warning; check the source before spending an evening on it.