People Systems Engineer at GitLab, Bengaluru

People systems engineer at GitLab Bengaluru, building the automations and integrations - Workday, Greenhouse, Slack, Workato - that run the employee lifecycle.

This full-time Bengaluru role was posted on 9 October 2026. GitLab is the DevSecOps platform company, famously all-remote, and this role applies its own product's principles to internal systems: build, test and maintain People-system automations across Workato, Google Cloud Platform, Workday, Greenhouse and Slack; develop integrations using Workday Web Services and Slack's API; and write clean automation code in Ruby or a comparable scripting language, versioned in GitLab with documentation and peer review. The listing asks for hands-on automation or integration experience, ideally with HR or business systems, and production experience with Workato or a comparable iPaaS.

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

This is an engineering role in every way that matters - code in version control, peer review, documentation - applied to People systems instead of customer product. That shape is increasingly valuable: companies want HR automation built like software, and this listing literally stores the code in GitLab. The toolchain is specific and modern (Workato, Workday, Greenhouse, Slack, plus AI tooling in the workflow), so you build a rare, portable skill set at the intersection of integrations and people operations.

The team and the work

GitLab is all-remote with a globally distributed team, which makes People-system automation disproportionately important - onboarding, offboarding and employee data flows have no office to paper over gaps. The company expects every team member to incorporate AI into daily workflows, and this role names Claude among the tools. Collaboration happens asynchronously across time zones, so written communication carries extra weight.

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:

Hands-on experience building automations or integrations, ideally with human resources or business systems.
Experience writing and maintaining code in Ruby or a comparable scripting language, such as Python or JavaScript, and a willingness to learn Ruby if you...
Hands-on experience with Workato or a comparable integration platform as a service (iPaaS) in a production environment.
Experience working with APIs and web services, including REST and SOAP, and an understanding of how data moves between systems.
Proficiency with Git for version control and code review; you treat automation code like production software.
A forward-thinking, AI-forward mindset: you use AI tools every day to automate tasks, speed up development and improve processes, and you're energized by what AI...
The ability to work independently, solve problems with curiosity, come with options and a recommendation, and collaborate openly. You protect highly confidential information and take...
Additional relevant experience includes Workday integrations (WWS, Reporting as a Service or Workday Studio), Slack apps or bots, CI/CD pipelines, Google Cloud Platform or Amazon...

Who this role suits

Engineers or integration specialists with hands-on automation experience, scripting ability in Ruby, Python or JavaScript, and production iPaaS exposure (Workato or similar). Strong fit for people who like internal tooling with visible company-wide impact. Not for candidates wanting customer-facing product engineering, and HR systems exposure, while preferred, is less important than genuine integration craft.

Practical notes

Willingness to learn Ruby is explicitly acceptable, so do not self-select out over language. Prepare to discuss an integration you built or maintained in production - error handling, retries and monitoring are likely talking points.

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: People Systems Engineer at GitLab. We found this listing on the Greenhouse public job board (job-boards.greenhouse.io), where it was posted on 9 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.