GitLab
About this role
GitLab is an all remote company whose DevSecOps platform has more than 50 million registered users, and this role sits on the Trust and Safety team that keeps abusive behaviour off GitLab.com. The work is building and maintaining the systems that detect and prevent platform abuse: spam, AI and token abuse, SEO optimisation and redirect abuse, and other financially motivated campaigns. You would become a core maintainer of the in house abuse platform, a Ruby on Rails monolith, and expand its agentic AI capabilities, including improving multi agent reasoning patterns with the goal of reducing human in the loop operational load. The posting makes one thing explicit that is worth highlighting: formal security engineering experience is not a hard requirement, and it says the role is an ideal fit for candidates with a software engineering background who want to move into security engineering. GitLab publishes no years figure, so we have marked it not stated.
Who this is for
What the posting asks for. GitLab publishes no years of experience figure, so judge yourself against the skills:
- Strong software development skills with experience in Ruby on Rails. This is stated as required.
- Experience working on distributed applications with large codebases deployed in cloud environments, described as strongly preferred.
- A passion and desire to proactively develop security engineering skills. Note that formal security engineering experience is explicitly not a hard requirement for this role.
- Comfort working in an all remote environment where results and impact matter above hours worked.
- Strong experience with cloud native development on Google Cloud Platform and/or AWS.
- Interest in thinking like a hacker and defending against attacks with an automation first mindset.
- Interest in handling trust and safety security incidents and collaborating with engineering to harden platform defences.
- Experience working on an AI native development team maintaining teams of agents, acting as a code reviewer, and abstracting your role away from writing code in most cases.
What the work actually looks like:
- Maintain core abuse prevention systems and build new abuse detection rules for evolving platform abuse including spam, AI and token abuse, SEO optimisation and redirects, and other financially motivated campaigns.
- Become a core maintainer of the in house abuse platform, a Ruby on Rails monolith, supporting and building new features for it.
- Improve and expand agentic AI capabilities in the abuse mitigation tools, including improving multi agent reasoning decision patterns with a target of reducing human in the loop operational load.
- Lead collaboration with peer engineering teams to deliver safety improvements to the GitLab product.
- Resolve automation gaps and create efficient automated processes.
- Create and maintain documentation such as runbooks and procedures.
About the team: Trust and Safety is a global team that keeps abusive behaviour off GitLab.com using automation, LLM aided anomaly detection and user behaviour analysis. It works closely with Security Incident Response, Signals Engineering, Threat Intelligence and the Red Team.
Location and working pattern: GitLab states that all of its roles are remote, with some carrying location based eligibility requirements its talent acquisition team can clarify. This listing includes India.
One more thing worth knowing: GitLab treats AI as a core productivity multiplier and expects team members to use it in daily workflows.
Honest fit guidance: this is the clearest route on today's board from software engineering into security engineering, because the posting says so itself. Rails is the non negotiable part.
- Strong software development skills with experience in Ruby on Rails. This is stated as required.
- Experience working on distributed applications with large codebases deployed in cloud environments, described as strongly preferred.
- A passion and desire to proactively develop security engineering skills. Note that formal security engineering experience is explicitly not a hard requirement for this role.
- Comfort working in an all remote environment where results and impact matter above hours worked.
- Strong experience with cloud native development on Google Cloud Platform and/or AWS.
- Interest in thinking like a hacker and defending against attacks with an automation first mindset.
- Interest in handling trust and safety security incidents and collaborating with engineering to harden platform defences.
- Experience working on an AI native development team maintaining teams of agents, acting as a code reviewer, and abstracting your role away from writing code in most cases.
What the work actually looks like:
- Maintain core abuse prevention systems and build new abuse detection rules for evolving platform abuse including spam, AI and token abuse, SEO optimisation and redirects, and other financially motivated campaigns.
- Become a core maintainer of the in house abuse platform, a Ruby on Rails monolith, supporting and building new features for it.
- Improve and expand agentic AI capabilities in the abuse mitigation tools, including improving multi agent reasoning decision patterns with a target of reducing human in the loop operational load.
- Lead collaboration with peer engineering teams to deliver safety improvements to the GitLab product.
- Resolve automation gaps and create efficient automated processes.
- Create and maintain documentation such as runbooks and procedures.
About the team: Trust and Safety is a global team that keeps abusive behaviour off GitLab.com using automation, LLM aided anomaly detection and user behaviour analysis. It works closely with Security Incident Response, Signals Engineering, Threat Intelligence and the Red Team.
Location and working pattern: GitLab states that all of its roles are remote, with some carrying location based eligibility requirements its talent acquisition team can clarify. This listing includes India.
One more thing worth knowing: GitLab treats AI as a core productivity multiplier and expects team members to use it in daily workflows.
Honest fit guidance: this is the clearest route on today's board from software engineering into security engineering, because the posting says so itself. Rails is the non negotiable part.
Apply on company site
Opens job-boards.greenhouse.io, the employer's own application page. Applying is always free.