Senior Backend Engineer, Development Health

Overview

As a Senior Backend Engineer on Development Health, you will make the systems that engineering teams rely on more reliable, maintainable, and easier to extend, building the automation, tooling, and data that help teams spot problems early and ship with less friction.

What you'll do

• Own and evolve core Development Health systems, from design through production.
• Improve the reliability, maintainability, and test coverage of long-lived automation, and reduce reliance on undocumented knowledge by documenting and simplifying legacy systems.
• Partner with engineering managers and product teams to identify workflow pain points and turn them into well-scoped, measurable improvements.
• Work with data to show whether changes improve engineering health, and use it to prioritize.
• Mentor intermediate engineers through code review, design feedback, and pairing.
• Communicate clearly in writing and asynchronously, including status, tradeoffs, and proposals for stakeholders across Engineering.
• Monitor the health of production systems, troubleshoot incidents, and contribute to root cause analysis.
• Use artificial intelligence (AI) agents and assistants to analyze issues and problem areas to help shape the team's product roadmap.

What you'll need

• Substantial experience as a backend or tooling engineer, with a track record of owning production systems end to end.
• Strong proficiency in Ruby, or the ability to become productive quickly.
• Experience maintaining or modernizing legacy codebases safely.
• Comfort with CI/CD systems, application programming interfaces (APIs), and automation at scale.
• Independent problem-solving and clear, concise written communication: you spot problems early, raise risks proactively, and drive work to completion without close direction.
• Experience writing automated unit and integration tests and taking part in collaborative code review.
• Experience using AI coding assistants to speed up development while critically reviewing their output.

Nice to have

• Rails.
• Developer productivity, engineering analytics, or internal tooling.
• GitLab's product and open source contribution workflow.
• Data pipelines or metrics reporting.
• Agent-based workflows that run in production.

Details

• Location: Bangalore, India.
• All-remote role, asynchronous by default.
• Some roles may carry specific location-based eligibility requirements.