GitLab
About this role
This is a Staff Backend Engineer seat at GitLab on the Events and Messaging Platform team, and it is a genuinely foundational one. GitLab runs two separate systems for asynchronous work today, Sidekiq for short background jobs and a purpose built event bus for longer workflows, and this role consolidates both into a single durable, multi tenant messaging and event processing platform that sits underneath almost everything GitLab ships, including webhooks and external triggers. The engineering is hard in the interesting way: durability under real load, tenant isolation, horizontal scalability, and migrating live production traffic off the legacy systems without dropping any of it. The language is Go. As with GitLab's other roles it is remote within India and asynchronous. GitLab publishes no years figure, so treat this as a senior, high ownership systems role and judge yourself on distributed systems depth.
Who this is for
GitLab does not state a years requirement in this posting, so the experience figure is left blank rather than guessed. This is a Staff level role, so expect the bar to be high.
What the posting asks for:
- Strong distributed systems instincts: durability, tenant isolation and horizontal scalability, and the judgement to tell a design that is durable from one that only looks durable under light load.
- Go backend depth and the ability to decompose complex architecture into shippable work for a team.
- Experience owning reliability end to end and migrating production workloads off legacy systems without disruption.
The day to day: you lead technical execution on the consolidated messaging and event platform, solve high complexity problems, set and hold the technical bar, and own the migration of existing production traffic off Sidekiq and the legacy event bus.
Location and ways of working: all remote and asynchronous. Tagged Bangalore, India, meaning remote within India in GitLab's model. Some roles carry location based eligibility, so confirm yours.
Honest read: a rare remote, Staff level distributed systems seat with real architectural ownership. Narrow pool, since durable multi tenant messaging is a specific skill, which cuts both ways.
What the posting asks for:
- Strong distributed systems instincts: durability, tenant isolation and horizontal scalability, and the judgement to tell a design that is durable from one that only looks durable under light load.
- Go backend depth and the ability to decompose complex architecture into shippable work for a team.
- Experience owning reliability end to end and migrating production workloads off legacy systems without disruption.
The day to day: you lead technical execution on the consolidated messaging and event platform, solve high complexity problems, set and hold the technical bar, and own the migration of existing production traffic off Sidekiq and the legacy event bus.
Location and ways of working: all remote and asynchronous. Tagged Bangalore, India, meaning remote within India in GitLab's model. Some roles carry location based eligibility, so confirm yours.
Honest read: a rare remote, Staff level distributed systems seat with real architectural ownership. Narrow pool, since durable multi tenant messaging is a specific skill, which cuts both ways.
Apply on company site
Opens job-boards.greenhouse.io, the employer's own application page. Applying is always free.