GitLab
About this role
GitLab sells a DevSecOps platform used by more than 50 million registered accounts, and this role sits in the part of the company that handles how customers actually buy and renew it. You would join a brand new team building the telemetry that catches billing and event problems before a customer feels them: dropped usage events, abuse spikes, and mismatches between CustomersDot, Salesforce and Zuora. The stack is Ruby on Rails with Prometheus, Grafana and OpenTelemetry, plus ClickHouse and event streaming for the reporting side, and some Python for the anomaly detection work. It suits a backend engineer who likes reliability work and does not mind that a mistake here touches revenue. GitLab is fully remote and publishes no years figure for this posting.
Who this is for
What the posting asks for:
- Professional experience with Ruby on Rails.
- A background in site reliability or observability engineering: monitoring, alerting, SLOs, SLIs, runbooks, incident handling, and tools such as Prometheus, Grafana and OpenTelemetry.
- Experience building anomaly detection, monitoring or risk management tooling.
- Exposure to reporting data stores, especially ClickHouse, and the change data capture and event streaming pipelines that feed them (Siphon, NATS JetStream).
- Experience with billing, financial or other business critical systems.
- Experience owning a project from concept to production, including proposal, discussion, execution and monitoring.
- Clear written communication in English, because the team is remote and largely asynchronous.
Counts as a bonus:
- Working knowledge of Python for anomaly detection and data work.
- Hands on experience with Zuora or Salesforce.
The day to day: designing metrics, logs and traces across the Monetization stack, building automated detection for billing and event anomalies and routing those alerts to the right feature team, writing reconciliation and data integrity checks across usage and billing pipelines, defining SLOs and SLIs, writing runbooks, taking part in incident handling, and reviewing other engineers' merge requests. You would report to the Engineering Manager for Observability, Monitoring and Integrations.
Experience: GitLab publishes no years figure anywhere in this posting, so we have left it blank rather than guess. What the posting does say is that the role is open at both the Senior Software Engineer and Staff Software Engineer levels, and that GitLab welcomes candidates with varying levels of experience because many successful hires do not meet every requirement.
Location: fully remote. GitLab states that all of its roles are remote, though some carry location based eligibility rules, so confirm yours with the recruiter early.
Who should apply: a backend engineer who is comfortable in Rails and genuinely enjoys observability work. This is a greenfield team, so you would help set its operating rhythm and quality bar rather than inherit one. If you want a tightly specified ticket queue, this is not that.
- Professional experience with Ruby on Rails.
- A background in site reliability or observability engineering: monitoring, alerting, SLOs, SLIs, runbooks, incident handling, and tools such as Prometheus, Grafana and OpenTelemetry.
- Experience building anomaly detection, monitoring or risk management tooling.
- Exposure to reporting data stores, especially ClickHouse, and the change data capture and event streaming pipelines that feed them (Siphon, NATS JetStream).
- Experience with billing, financial or other business critical systems.
- Experience owning a project from concept to production, including proposal, discussion, execution and monitoring.
- Clear written communication in English, because the team is remote and largely asynchronous.
Counts as a bonus:
- Working knowledge of Python for anomaly detection and data work.
- Hands on experience with Zuora or Salesforce.
The day to day: designing metrics, logs and traces across the Monetization stack, building automated detection for billing and event anomalies and routing those alerts to the right feature team, writing reconciliation and data integrity checks across usage and billing pipelines, defining SLOs and SLIs, writing runbooks, taking part in incident handling, and reviewing other engineers' merge requests. You would report to the Engineering Manager for Observability, Monitoring and Integrations.
Experience: GitLab publishes no years figure anywhere in this posting, so we have left it blank rather than guess. What the posting does say is that the role is open at both the Senior Software Engineer and Staff Software Engineer levels, and that GitLab welcomes candidates with varying levels of experience because many successful hires do not meet every requirement.
Location: fully remote. GitLab states that all of its roles are remote, though some carry location based eligibility rules, so confirm yours with the recruiter early.
Who should apply: a backend engineer who is comfortable in Rails and genuinely enjoys observability work. This is a greenfield team, so you would help set its operating rhythm and quality bar rather than inherit one. If you want a tightly specified ticket queue, this is not that.
Apply on company site
Opens job-boards.greenhouse.io, the employer's own application page. Applying is always free.