Intermediate Backend Engineer at GitLab, Bengaluru

Intermediate backend engineer at GitLab (Bangalore-listed, remote-first): Go and Kubernetes platform work on the DevSecOps platform used by millions.

This role was posted on 2 September 2026. GitLab is one of the world's largest all-remote companies, and its listing describes a remote-first, asynchronous organization where written communication and self-direction matter. The stack named: production Go services, Docker, Kubernetes, Helm, CI/CD, PostgreSQL, observability - with Rust called out for systems and security work.

About GitLab

GitLab builds the single DevSecOps platform that covers the software lifecycle from planning and source control to CI/CD, security and monitoring. It is famously all-remote and publishes its operating handbook publicly. The listing notes the team treats AI as a core productivity multiplier and expects everyone to incorporate it into daily workflows. Learn more on GitLab's website.

The role in plain terms

You take backend features and improvements from problem clarification through implementation and rollout: Go services and APIs, concurrency, gRPC, containerized deployment with Kubernetes and Helm, PostgreSQL schema evolution, and observability with metrics, logs and traces. Intermediate level at GitLab means owning features with support, not carrying the architecture alone.

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:

Production Go services, APIs, concurrency, profiling, or gRPC.
Docker, Kubernetes, Helm, CI/CD, or cloud deployment.
PostgreSQL, schema evolution, caching, queues, messaging, or event-driven workflows.
Observability using metrics, logs, traces, dashboards, and alerts.
Rust, particularly for systems, security, performance, or platform work.
Strong written communication and effective collaboration in a remote, asynchronous environment.

Who this role suits

Backend engineers with a few years of Go (or strong adjacent backend experience) who want remote-first, async work at a company that wrote the book on it. Written communication is genuinely assessed here - GitLab's culture runs on documents. Not for people who need in-office collaboration daily.

Practical notes

GitLab interviews are famously transparent - its hiring process is public in the handbook, so read it. Expect a merge-request-style technical exercise; contribute to GitLab's open source beforehand if you can, it is the strongest signal. The listing asks about AI in daily workflows, so have examples.

How to apply

Apply directly on the employer's site: Intermediate Backend Engineer at GitLab. We found this listing on the Greenhouse public job board (job-boards.greenhouse.io), where it was posted on 2 Sep 2026 and was still open when we checked on 31 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.