GitLab
Engineering Manager
Found: Today
You'll lead the globally distributed Observability team. The team builds and operates the metrics, logging, alerting, and capacity planning platforms that GitLab engineers use to understand GitLab.com and GitLab Dedicated. You'll help determine how the team collects, stores, queries, and acts on telemetry, balancing reliable signals with scale and cost.
In your first year, you'll guide improvements to Prometheus-based metrics pipelines, log ingestion and retention, alerting driven by service-level objectives (SLOs), and capacity forecasting. You'll work with Site Reliability Engineering, Product Engineering, and other Infrastructure Platforms teams to make it easier for engineers to observe the services they own. You'll also take part in incident response and help keep the team's on-call work sustainable.
What you’ll do
- Lead, hire, onboard, and develop a distributed engineering team working asynchronously.
- Set priorities with Site Reliability Engineering, Product Engineering, and GitLab Dedicated teams, and help the team deliver observability services iteratively.
- Own the reliability, scalability, and cost of the team's metrics, logging, alerting, and capacity planning platforms.
- Reduce noisy or missing alerts and telemetry gaps, and use SLOs, error budgets, and self-service instrumentation to help engineers maintain the health of their services.
- Guide technical decisions about time-series storage, high-cardinality metrics, log pipelines, and distributed tracing.
- Participate in the Incident Manager On Call (IMOC) rotation, coordinating the response to high-severity incidents affecting GitLab.com.
- Keep the team's on-call rotation sustainable through coverage across time zones, useful runbooks, better alerts, and follow-through on post-incident actions.
- Use AI tools and agents to support engineering workflows and incident triage, reviewing their output while engineers retain responsibility for decisions.
- Experience leading an observability, platform engineering, or site reliability engineering team operating at scale, including supporting people in a distributed, asynchronous environment.
- Technical knowledge of metrics systems such as Prometheus and long-term storage, logging platforms such as Elasticsearch or cloud-native services, and alerting design.
- Experience using SLOs, error budgets, and capacity forecasts to make reliability and investment decisions.
- Experience operating a large software-as-a-service platform and investigating production issues such as telemetry gaps, ingestion limits, or noisy and missing alerts.
- Experience participating in and improving production on-call rotations, including incident coordination and balancing operational load with project work.
- The ability to explain technical tradeoffs to engineering partners and other stakeholders.
- Experience using AI tools or agents in engineering or management work; you can describe how you would apply them to operational problems such as incident triage.