Intermediate Security Engineer, Security Incident Response Team (SIRT)
GitLab
Intermediate Security Engineer, Security Incident Response Team (SIRT) at GitLab is a full time role based in Remote · Australia, Australia (remote). It was published on 9 September 2026 and was open at last check.
| Role | Intermediate Security Engineer, Security Incident Response Team (SIRT) |
|---|---|
| Company | GitLab |
| Location | Remote · Australia, Australia (remote) |
| Employment type | Full Time |
| Published | 9 September 2026 |
| Status | Open at last check |
GitLab is the intelligent orchestration platform for DevSecOps. GitLab enables organizations to increase developer productivity, improve operational efficiency, reduce security and compliance risk, and accelerate digital transformation. More than 50 million registered users and more than 50% of the Fortune 100* trust GitLab to ship better, more secure software faster.
The same principles built into our products are reflected in how our team works: we embrace AI as a core productivity multiplier, with all team members expected to incorporate AI into their daily workflows to drive efficiency, innovation, and impact. GitLab is where careers accelerate, innovation flourishes, and every voice is valued. Our high-performance culture is driven by our values and continuous knowledge exchange, enabling our team members to reach their full potential while collaborating with industry leaders to solve complex problems. Co-create the future with us as we build technology that transforms how the world develops software.
- Fortune 500® is a registered trademark of Fortune Media IP Limited, used under license. Claim based on GitLab data. Fortune 100 refers to the top 20% ranked companies in the 2025 Fortune 500 list, published in June 2025. Fortune and Fortune Media IP Limited are not affiliated with, and do not endorse products or services of GitLab.
An overview of this role
As an Intermediate Security Engineer on GitLab's Security Incident Response Team (SIRT), you will be on the frontline of protecting both GitLab.com and GitLab the company from security threats. This role operates on a compressed 4-day work schedule, with a full-time week's hours condensed into four longer working days. Shifts run either Sunday through Wednesday or Wednesday through Saturday to provide 24/7/365 security coverage.
Your primary focus will be detecting and responding to security incidents during your scheduled shifts. You'll work extensively with our incident response automation tools to investigate, analyze, and resolve security events. You'll also have opportunities to contribute to our security tooling and automation, helping to improve our detection and response capabilities.
In this role, you'll develop expertise using our security infrastructure to monitor for threats, analyze potential incidents, and coordinate response efforts across teams. This position is ideal for someone who wants to grow their incident response skills while working within GitLab's established security framework. You'll learn to think both tactically and strategically about security, while getting hands-on experience handling real-world incidents.
Successful Security Engineers thrive in high-pressure environments, remaining calm while following prepared runbooks and thinking critically about security challenges. In this role, you will learn to think like both an attacker and defender, developing proactive and preventative security measures to keep GitLab and its users' data safe in our ever-changing threat landscape. Through hands-on experience and mentorship, you'll develop the skills needed to anticipate security risks, respond effectively to incidents, and contribute to GitLab's robust security posture.
Find out more about the Security Operations team and responsibilities here:
What you’ll do
- Lead security incident response in our 24/7 global rotation, managing incidents from detection through containment and recovery
- Create and maintain comprehensive incident response documentation, including runbooks and standard procedures
- Conduct post-incident analysis through RCA and lessons-learned reviews to strengthen our incident response program
- Design and implement automated security processes to improve operational efficiency and reduce manual intervention
- Drive continuous improvement by identifying security gaps and implementing advanced detection and response capabilities
- Collaborate across GitLab teams to develop new security capabilities and deliver technical projects that enhance our infrastructure
What you’ll bring
- Demonstrated ability to learn and lead incident response processes independently
- Experience with SIEM/security logging tools
- Experience with cloud platforms (GCP and/or AWS)
- Python programming skills or strong willingness to learn
- A passion for technical documentation
- Proactive approach to identifying and investigating security threats
- Interest in conducting forensic analysis of infected hosts
- Experience or strong desire to learn cloud-based security investigations
About the team
Security Operations is a globally distributed team of engineers split across 3 core regions; AMER, APAC and EMEA, and is at the forefront of security events that impact both GitLab.com and GitLab. We are both reactive and proactive, leading security investigations, incident response support and response resolution, through to cyber threat analysis and detection and response engineering. Even though we’re a global team, we work together in a cross-regional manner and have automation and processes to facilitate collaboration when resolving incidents, handovers, and general collaboration for project work as well.
How GitLab Supports Full-Time Employees
Benefits to support your health, finances, and well-being
Equity Compensation & Employee Stock Purchase Plan
Please note that we welcome interest from candidates with varying levels of experience; many successful candidates do not meet every single requirement. Additionally, studies have shown that people from underrepresented groups are less likely to apply to a job unless they meet every single qualification. If you're excited about this role, please apply and allow our recruiters to assess your application.
Country Hiring Guidelines: GitLab hires new team members in countries around the world. All of our roles are remote, however some roles may carry specific location-based eligibility requirements. Our Talent Acquisition team can help answer any questions about location after starting the recruiting process.
Privacy Policy: Please review our Recruitment Privacy Policy. Your privacy is important to us.
GitLab is proud to be an equal opportunity workplace and is an affirmative action employer. GitLab’s policies and practices relating to recruitment, employment, career development and advancement, promotion, and retirement are based solely on merit, regardless of race, color, religion, ancestry, sex (including pregnancy, lactation, sexual orientation, gender identity, or gender expression), national origin, age, citizenship, marital status, mental or physical disability, genetic information (including family medical history), discharge status from the military, protected veteran status (which includes disabled veterans, recently separated veterans, active duty wartime or campaign badge veterans, and Armed Forces service medal veterans), or any other basis protected by law. GitLab will not tolerate discrimination or harassment based on any of these characteristics. See also GitLab’s EEO Policy and EEO is the Law. If you have a disability or special need that requires accommodation, please let us know during the recruiting process.
Create your free OnJob profile to apply — we'll take you to GitLab's application after sign-up. · Posted 9 Sept 2026.
Intermediate Security Engineer, Security Incident Response Team (SIRT) at GitLab — questions answered
What does the Intermediate Security Engineer, Security Incident Response Team (SIRT) role at GitLab pay?
GitLab does not publish a salary on this Intermediate Security Engineer, Security Incident Response Team (SIRT) listing, so OnJob shows no figure for it rather than an estimate. For what this role pays across the market, the OnJob salary guides aggregate the live listings that do disclose pay.
Is the Intermediate Security Engineer, Security Incident Response Team (SIRT) role at GitLab remote?
Yes — GitLab advertises this Intermediate Security Engineer, Security Incident Response Team (SIRT) role as remote, tied to Remote · Australia, Australia, and it is listed as full time work. Remote terms come from the employer's own posting, so confirm the expected working hours, timezone and any on-site days with GitLab before you apply.
Is the Intermediate Security Engineer, Security Incident Response Team (SIRT) role at GitLab still open?
The Intermediate Security Engineer, Security Incident Response Team (SIRT) posting at GitLab was open at OnJob's last check of the employer's careers page, having been published on 9 September 2026. OnJob re-checks source listings on each build and marks a role closed once it disappears, but listings can close without notice, so the employer's own page is the final word.
How do you apply for the Intermediate Security Engineer, Security Incident Response Team (SIRT) role at GitLab?
Apply to the Intermediate Security Engineer, Security Incident Response Team (SIRT) at GitLab role through OnJob with a free profile: OnJob scores your fit against the listing, shows the skills lowering that score, and submits an ATS-ready profile to GitLab's own application page. Creating a profile is free and needs no card.
Explore more on OnJob
Hiring for a role like this?
Post a job on OnJob and reach AI-matched candidates.
