Intermediate Backend Engineer, Authorization

This role involves building and maintaining access control systems for GitLab's platform. You'll work on Ruby on Rails and a new Rust-based authorization service, ensuring security and performance. Ideal for someone with experience in authorization concepts and a security mindset.

• Fully remote, so where you live is not a constraint.

Summarised by InternDoor from GitLab’s posting, in our own words. The posting itself is the source of truth, so check it before you apply.

• Implement authorization changes in Ruby on Rails to ensure access control
• Work on fine-grained token permissions and REST/GraphQL API enforcement
• Refactor legacy policy code while maintaining existing behavior
• Collaborate with AI and auth teams on interface contracts for new authorization service

Required

• Authorization Concepts Hands-on experience with authorization concepts, such as role-based access control or fine-grained permissions, from work or projects
• Security Mindset
• Codebase Experience Experience making careful changes to existing codebases, including incremental refactors and feature-flagged rollouts that preserve existing behavior
• GraphQL/API Authorization Familiarity with GraphQL or API authorization patterns
• Performance Awareness Awareness of performance, including how repeated permission checks can add up on every request

Nice to have

• PostgreSQL Helpful, but not required: hands-on PostgreSQL experience
• Rust Helpful, but not required: experience with Rust
• gRPC/Protocol Buffers Helpful, but not required: experience with gRPC or Protocol Buffers
• Policy Languages Helpful, but not required: experience with Cedar or other policy languages
• Zanzibar Helpful, but not required: experience with Zanzibar-style authorization systems
• Go Helpful, but not required: experience with Go
• Service-Oriented Architecture Helpful, but not required: experience with service-oriented architecture

Read from GitLab’s posting. Its own wording is the one that counts.

1. Check what they ask for. Read the requirements above: GitLab asks for 2–4 years.
2. Tailor your resume to the role. Put the work that matches these skills first. InternDoor’s resume tailor does it against this posting.
3. Apply on GitLab’s careers site. The application is on job-boards.greenhouse.io, not on InternDoor. We never ask for a fee.

Apply soon: postings like this can close without notice, and this one states no deadline.

Posted

3 Nov 2026, on LinkedIn

First seen by InternDoor

3 Nov 2026, within 43 minutes of being posted

Last checked

3 Nov 2026: the posting was still in LinkedIn’s search results. We have not checked its application page.

Application deadline

GitLab has not stated one

Leaves InternDoor

By 3 Dec 2026, our 30-day limit for LinkedIn listings, or sooner if the application closes

Application page

job-boards.greenhouse.io

What we checked, and what the dates mean

The date this listing leaves InternDoor is our own rule, not a deadline set by GitLab. Postings can close earlier, at any time.

InternDoor has recorded 4 engineering postings from GitLab in India since Oct 2026.

When this listing comes down, this address says the role has closed and lists open roles like it, instead of a dead end.

Hiring at GitLab? Post a role on InternDoor, free

Full-time roles at other employers, closest first: the experience they ask for, the specialisation, the city, then the work mode. Internships are left out.

• BC Associate- Back end Engineer(PEG)Bain & Company · Backend development Gurugram · Hybrid2–5 years →
• RL .NET DeveloperReveation Labs · Full Stack Developer India · Remote2–3 years →
• U Application DeveloperUPS · Production Engineering Chennai · On-site2–4 years →
• C Java Development Programmer AnalystCiti Chennai · Hybrid2–5 years →

All backend development roles →

More at GitLab

• Intermediate Data EngineerBengaluru · Remote
• Intermediate Backend Engineer, IndiaBengaluru · Remote

All GitLab roles →