GitLab
About this role
A technical lead role inside GitLab's Product Security department, covering the security of the cloud infrastructure that runs GitLab Dedicated, Cells and the self managed offering. It is a Staff level individual contributor job, so the influence comes from setting architectural patterns and reference implementations that other engineering teams adopt, not from managing people. Expect deep cloud security work across AWS, GCP and Azure, Kubernetes, and Infrastructure as Code security in Terraform, Ansible and CloudFormation, plus policy as code and automated compliance. GitLab also wants a point of view on where AI genuinely helps security workflows. You would write production quality tooling in Go, Python and Ruby. GitLab publishes no years figure for this role, and it is open to candidates in India, Israel, the UK and the US.
Who this is for
What the posting asks for:
- Expert knowledge of cloud infrastructure security (AWS, GCP or Azure), container orchestration with Kubernetes, and related infrastructure and data security topics.
- Proficiency in multiple programming languages (Go, Python, Ruby) with a track record of shipping production quality security tooling.
- Extensive experience with Infrastructure as Code security (Terraform, Ansible, CloudFormation), policy as code and automated compliance.
- Hands on experience applying AI to security workflows, with a view on where it creates real leverage.
- A track record of leading multi team technical initiatives from an ambiguous problem statement to a measurable outcome, setting direction that peer teams adopt.
- Strong written and verbal communication, including explaining security tradeoffs to senior leadership.
- Familiarity with security certifications and frameworks: FedRAMP, ISO 27001, SOC 2, PCI DSS.
The day to day: setting architectural patterns, reference implementations and foundational security automation; leading security initiatives from problem framing through delivery; running security reviews and threat modelling for complex infrastructure; setting the team's approach to AI assisted security engineering; acting as the authoritative technical voice for Infrastructure Security with stakeholders; and mentoring engineers. GitLab also expects the team to secure GitLab's own infrastructure using GitLab, which they call dogfooding.
Experience: no years figure is published anywhere in the posting, so we left it blank. Staff at GitLab is a senior individual contributor level, and the responsibilities listed (multi quarter ambiguous initiatives, setting direction other teams follow) point well above entry level even though no number is given.
Location: remote, and open to India, Israel, the United Kingdom and the United States. GitLab notes some roles carry location based eligibility rules.
Who should apply: an experienced infrastructure or cloud security engineer who wants scope over a platform rather than a queue of findings, and who is comfortable writing the tooling instead of only reviewing it. This is a leadership role without direct reports.
- Expert knowledge of cloud infrastructure security (AWS, GCP or Azure), container orchestration with Kubernetes, and related infrastructure and data security topics.
- Proficiency in multiple programming languages (Go, Python, Ruby) with a track record of shipping production quality security tooling.
- Extensive experience with Infrastructure as Code security (Terraform, Ansible, CloudFormation), policy as code and automated compliance.
- Hands on experience applying AI to security workflows, with a view on where it creates real leverage.
- A track record of leading multi team technical initiatives from an ambiguous problem statement to a measurable outcome, setting direction that peer teams adopt.
- Strong written and verbal communication, including explaining security tradeoffs to senior leadership.
- Familiarity with security certifications and frameworks: FedRAMP, ISO 27001, SOC 2, PCI DSS.
The day to day: setting architectural patterns, reference implementations and foundational security automation; leading security initiatives from problem framing through delivery; running security reviews and threat modelling for complex infrastructure; setting the team's approach to AI assisted security engineering; acting as the authoritative technical voice for Infrastructure Security with stakeholders; and mentoring engineers. GitLab also expects the team to secure GitLab's own infrastructure using GitLab, which they call dogfooding.
Experience: no years figure is published anywhere in the posting, so we left it blank. Staff at GitLab is a senior individual contributor level, and the responsibilities listed (multi quarter ambiguous initiatives, setting direction other teams follow) point well above entry level even though no number is given.
Location: remote, and open to India, Israel, the United Kingdom and the United States. GitLab notes some roles carry location based eligibility rules.
Who should apply: an experienced infrastructure or cloud security engineer who wants scope over a platform rather than a queue of findings, and who is comfortable writing the tooling instead of only reviewing it. This is a leadership role without direct reports.
Apply on company site
Opens job-boards.greenhouse.io, the employer's own application page. Applying is always free.