New RJRP now shows Market-Observed Roles alongside verified postings — scored by our Hiring Activity algorithm. How it works →
🔍
Market-Observed Role 🔍 Observed Likely Active (65-79)
This role was detected through GitLab's hiring system and hasn't been verified directly by the employer. Our algorithm scored it as Likely Active (65-79) based on freshness, specificity, and company patterns. What does this mean? →

Senior Backend Engineer, Analytics Instrumentation (Golang)

GitLab
🔍 Observed
78
Hiring Activity Score
Likely Active (65-79)
  • Base score
  • Posted 1 days ago
  • has location, quality description (11176 chars)
  • 176 new listings in 30d (×0.98 age 1d)
  • 3 skills
  • Direct ATS (greenhouse)
How the Hiring Activity Score works →
Remote, Canada; Remote, US First seen 1 day, 4 hours ago Last seen 4 hours, 54 minutes ago Greenhouse
Apply on Greenhouse Search Google for This Role

ATS links often expire — Google search finds the latest posting

Job Description

GitLab is the intelligent orchestration platform for DevSecOps. GitLab enables organizations to increase developer productivity, improve operational efficiency, reduce security and compliance risk, and accelerate digital transformation. More than 50 million registered users and more than 50% of the Fortune 100* trust GitLab to ship better, more secure software faster.

The same principles built into our products are reflected in how our team works: we embrace AI as a core productivity multiplier, with all team members expected to incorporate AI into their daily workflows to drive efficiency, innovation, and impact. GitLab is where careers accelerate, innovation flourishes, and every voice is valued. Our high-performance culture is driven by our values and continuous knowledge exchange, enabling our team members to reach their full potential while collaborating with industry leaders to solve complex problems. Co-create the future with us as we build technology that transforms how the world develops software.

*Fortune 500® is a registered trademark of Fortune Media IP Limited, used under license. Claim based on GitLab data. Fortune 100 refers to the top 20% ranked companies in the 2025 Fortune 500 list, published in June 2025. Fortune and Fortune Media IP Limited are not affiliated with, and do not endorse products or services of GitLab.

An overview of this role

As a Senior Backend Engineer, you'll lead the design and development of a unified, Go-based instrumentation service that consolidates analytics instrumentation across GitLab's engineering organization. You'll architect and own critical backend systems that help the company understand customer usage patterns across GitLab SaaS and Self-Managed deployment environments. That data directly informs strategic product decisions. This role offers the opportunity to build foundational infrastructure that simplifies instrumentation for every team at GitLab, replacing the complexity of multiple language-specific SDKs with a single, unified solution that all teams can rely on.

What you'll do

  • Design, build, and maintain a unified Go-based instrumentation service that consolidates instrumentation across the entire company, eliminating the need for multiple language-specific SDKs while maintaining reliability and performance.
  • Own the responsibility for handling the sending, transit, and quality of instrumentation data across the system, ensuring data integrity that directly impacts the company's strategic decision-making and usage billing accuracy.
  • Train and support product development teams across the company on how to instrument their features using the unified service, providing documentation, guidance, and technical support.
  • Manage on-call responsibilities during working hours for systems responsible for usage billing and instrumentation, ensuring system reliability and quick response to critical issues.
  • Lead collaboration across research and development teams and the enterprise data organization to understand requirements and deliver solutions that serve multiple stakeholders.
  • Make strategic architectural decisions that balance the needs of product teams (who need ease of use) with data consumers (who need reliability and correctness), ensuring the system serves as a foundational service for the company.

What you'll bring

  • Proficiency in the Go programming language, with experience building and maintaining production services.
  • Strong backend development experience, with the ability to design scalable, reliable systems serving internal and external customers.
  • Experience with infrastructure concerns such as system reliability, performance at scale, data quality, and observability.
  • Experience designing and building APIs (REST, gRPC, or similar) that other teams integrate with.
  • Experience working in collaborative, cross-functional teams with product teams, data consumers, and other internal stakeholders across team boundaries.
  • Experience with instrumentation, analytics, data systems, or similar foundational infrastructure is helpful, along with Ruby on Rails experience.

About the team


Our team is part of the Data Engineering organization and operates as a foundational service supporting all research and development teams at GitLab. We're responsible for consolidating and managing the systems that handle instrumentation data sending, transit, and quality across the entire company. Our work directly enables company strategy and decision-making by providing visibility into customer usage patterns across different product offerings and customer types (GitLab SaaS and Self-Managed deployment environments). This work supports usage billing and product decisions. We're building a unified, Go-based instrumentation service that replaces multiple language-specific SDKs, making it easier for teams to instrument their features while we ensure data integrity for billing and analysis. As a distributed team working asynchronously across multiple time zones, we collaborate closely with product and engineering teams across the company and provide training and support to help them instrument their features effectively.

The base salary range for this role’s listed level is currently for residents of the United States only. This range is intended to reflect the role's base salary rate in locations throughout the US. Grade level and salary ranges are determined through interviews and a review of education, experience, knowledge, skills, abilities of the applicant, equity with other team members, alignment with market data, and geographic location. The base salary range does not include any bonuses, equity, or benefits. See more information on our benefits and equity. Sales roles are also eligible for incentive pay targeted at up to 100% of the offered base salary.

United States Salary Range
$117,600$252,000 USD

How GitLab Supports Full-Time Employees

Please note that we welcome interest from candidates with varying levels of experience; many successful candidates do not meet every single requirement. Additionally, studies have shown that people from underrepresented groups are less likely to apply to a job unless they meet every single qualification. If you're excited about this role, please apply and allow our recruiters to assess your application.

Country Hiring Guidelines: GitLab hires new team members in countries around the world. All of our roles are remote, however some roles may carry specific location-based eligibility requirements. Our Talent Acquisition team can help answer any questions about location after starting the recruiting process.  

Privacy Policy: Please review our Recruitment Privacy Policy. Your privacy is important to us.

GitLab is proud to be an equal opportunity workplace and is an affirmative action employer. GitLab’s policies and practices relating to recruitment, employment, career development and advancement, promotion, and retirement are based solely on merit, regardless of race, color, religion, ancestry, sex (including pregnancy, lactation, sexual orientation, gender identity, or gender expression), national origin, age, citizenship, marital status, mental or physical disability, genetic information (including family medical history), discharge status from the military, protected veteran status (which includes disabled veterans, recently separated veterans, active duty wartime or campaign badge veterans, and Armed Forces service medal veterans), or any other basis protected by law. GitLab will not tolerate discrimination or harassment based on any of these characteristics. See also GitLab’s EEO Policy and EEO is the Law. If you have a disability or special need that requires accommodation, please let us know during the recruiting process.

Skills

rust go git
Job Information
  • Company:
    GitLab
  • Location:
    Remote, Canada; Remote, US
  • Job Type:
    Internship
  • Work Location:
    Remote
  • Experience Level:
    Senior
  • Source:
    Greenhouse
  • Status:
    Active
Activity Score
78 /100
Likely Active (78)

Higher scores indicate more likely active hiring based on listing freshness, company activity, and other signals. Learn more →

+
🔍

We now show two types of job listings

Same commitment to real jobs. More opportunities for you. Here's how it works.

✓ Verified Employer-Verified Posts

These jobs were posted directly to RJRP by the employer. The company has been verified through our multi-step process. This is our gold standard — the employer is real, the job is real, and you can apply with confidence.

✓ 100% employer verified
🔍 Observed Market-Observed Roles

These roles were detected through employer hiring systems like Workday. They haven't been verified by the employer directly, so we score each one using our Hiring Activity Score — an algorithm that analyzes freshness, specificity, company hiring patterns, and more to estimate whether the role is actively being filled.

📊 Only high-scoring listings are shown

Our promise hasn't changed. We will never show you a listing we can't stand behind. Market-observed roles must pass our scoring threshold before they appear on RJRP. Anything that looks like a ghost job, a talent pipeline, or a dead listing gets filtered out — you'll never see it.