Team Lead - Platform Monitoring Engineer

Databricks · Bengaluru, India · Support · listed October 28, 2026

The shape of it

Seniority
Senior
Experience asked
2–6 years
Where
Not stated
Requirements listed
8
Length
657 words

In the posting’s own words

We are seeking an experienced, hands-on Team Lead to shape the future of platform observability and proactive customer monitoring. This is a high-impact technical role for someone who thrives at the intersection of platform reliability, incident response, and customer obsession.

What it asks for · 8

  • Minimum of 6 years of experience as an SRE, DevOps Engineer, CRE, Production Engineer, or similar role.
  • 2+ years of experience leading engineers, whether as a people manager or team lead, with clear mentorship and coaching responsibilities.
  • Production-level experience with at least one major cloud provider (AWS, Azure, GCP) and proficiency in container and orchestration technologies (Docker, Kubernetes).
  • Hands-on experience with monitoring, logging, and alerting tools such as ELK, Prometheus, Grafana, PagerDuty, etc. Ability to architect monitoring solutions that correlate metrics, logs, and traces.
  • Strong proficiency in Python or similar languages with the ability to build production-quality automation tools.
  • Experience owning critical phases of the incident lifecycle from detection through resolution and post-mortem analysis in demanding production environments.
  • Excellent communication skills, with the ability to influence cross-functional partners.
  • BS, Master's, or PhD in Computer Science or Computer Engineering, or a related Engineering field.

What the job covers

  • Lead platform incident investigation, coordinating cross-functional teams through rapid detection, mitigation, and resolution to minimize customer impact.
  • Conduct thorough post-incident root cause analysis across infrastructure, services, and cloud providers to identify systemic patterns and prevent future occurrences.
  • Guide the design and implementation of customer-focused alerting pipelines and end-to-end observability workflows that expand detection coverage and reduce mean time to detection.
  • Build automation tools, establish reusable monitoring patterns, and resolve reliability gaps that directly impact customer experience.
  • Participate in and help structure the on-call rotation, leading by example during high-severity incidents.
  • Collaborate with internal customer stakeholders to design and execute the customers' reliability plan, focusing on observability and monitoring.
  • Participate in growing the local team of Platform Monitoring Engineers, including hiring and onboarding.
  • Act as the local point of leadership and a connection to the broader global team, aligning local execution with global goals.

Degree language

  • BS, Master's, or PhD in Computer Science or Computer Engineering, or a related Engineering field.

Tools and skills named

Cloud & infra
  • Observability3×
  • AWS
  • Azure
  • Docker
  • GCP
  • Grafana
  • Kubernetes
  • Prometheus
  • Site reliability
Ways of working
  • Cross-functional3×
  • Mentorship2×
  • On-call
Data
  • Databricks
Languages
  • Python

Words the posting leans on

  • monitoring8×
  • customer7×
  • engineer6×
  • experience6×
  • incident6×
  • platform6×
  • detection5×
  • lead4×
  • leadership4×
  • reliability4×
  • tools4×
  • alerting3×
  • cross-functional3×
  • engineering3×
  • impact3×
  • local3×

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 November 2, 2026 and last changed by Databricks on October 31, 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.