Senior Software Engineer, SSCS : Authentication at GitLab

Senior software engineer on GitLab's SSCS Authentication team in Bengaluru, building token issuance, validation and identity services in Go and Ruby.

This full-time Bengaluru role was posted on 15 October 2026. The listing describes shaping the roadmap for GATE and GitLab's authentication services with the team, and designing and implementing token issuance, validation and identity services in Go and Ruby across the Rails monolith and GATE. Requirements include professional experience with Go and/or Ruby in scaling or mission-critical SaaS products, and familiarity with authentication and authorization technologies such as OAuth, OIDC, SAML, SSO, SCIM and LDAP.

About GitLab

GitLab builds a DevSecOps platform that covers source code management, CI/CD, security scanning and planning in a single application. Its listings state that more than 50 million registered users and more than half of the Fortune 100 use the platform.

GitLab operates as an all-remote company with team members in many countries, including India. Its public handbook and listing pages describe an asynchronous, documentation-heavy way of working, and its listings note that team members are expected to use AI tooling in daily workflows. Learn more on GitLab's website.

The role in plain terms

Authentication services sit on the critical path of every request, so the mission-critical SaaS requirement in the listing is literal - token issuance downtime means no one logs in. The dual-stack reality (Go services alongside the Rails monolith) reflects GitLab's architecture and means comfort in both is valuable. The roadmap-shaping responsibility is notable for a senior IC seat: the listing gives the team, including this role, a voice in direction.

The team and the work

Per the listing, the work spans token issuance, validation and identity services across two runtimes. The protocol list - OAuth, OIDC, SAML, SSO, SCIM, LDAP - defines the domain vocabulary expected. Performance work is named in the listing as well.

What the employer asks for

These requirements are quoted from the employer's listing, kept in their exact words so eligibility details are not distorted:

Professional experience with Go and/or Ruby in scaling or mission-critical SaaS products.
Familiarity with authentication and authorization technologies or techniques, such as OAuth, OIDC, SAML, SSO, SCIM, LDAP, JSON Web Tokens (JWTs), role-based access control (RBAC), or...
Knowledge of token systems, cryptographic signing, and key management.
Experience building or contributing to a service from concept to production, including proposal, discussion, and execution.
Proficiency in written and verbal English, with the ability to communicate complex problems and solutions clearly in a remote, largely asynchronous work environment.
Experience diagnosing, preventing, and resolving performance and optimization problems.
Experience working in an iterative software development process, managing your work effectively, staying organized, and following through on priorities.

Who this role suits

Backend engineers with production Go and/or Ruby on mission-critical SaaS, plus working knowledge of authentication protocols. Not for engineers without any identity-domain exposure - the protocol familiarity is a stated requirement.

Practical notes

For authentication engineering roles, expect protocol questions (OAuth flows, token validation, SAML assertions) and scaling questions about high-throughput validation paths. Security vulnerability response experience is worth mentioning - it is part of the team's remit per the listing.

Working at GitLab

Roles at GitLab span the product itself (backend in Ruby and Go, frontend, security, infrastructure) plus internal systems teams that build the company's own tooling and automations.

How to apply

Apply directly on the employer's site: Senior Software Engineer, SSCS : Authentication at GitLab. We found this listing on the Greenhouse public job board (job-boards.greenhouse.io), where it was posted on 15 Oct 2026 and was still open when we checked on 30 Oct 2026. Before applying, re-read the employer's own description in full, since eligibility details, deadlines and process steps can change at any time and the employer's page is always the final word. Tailor your resume to the specific requirements above rather than sending a generic one: mirror the skills and tools the listing names where you genuinely have them. A short, specific note on why this team and this problem interest you goes further than a long generic cover letter. Never pay a fee to apply or interview; genuine employers, including this one, do not charge candidates.

Related openings on GetFirstJob

If this role is not the right fit, these current openings are in a similar area:

We write and maintain this page from the employer's public listing and link straight to their application page. We do not act as a recruiter, and applying is always free. If the link above stops working, the role has likely been filled.

This is our short summary of the employer's listing. The full description, eligibility and deadline are on the employer's page.