- You are here:
- Roles
- Engineering Roles
- Security Engineer
As a member of the security team at GitLab, you will be working towards raising the bar on security. We will achieve that by working and collaborating with cross-functional teams to provide guidance on security best practices.
The Security Team is responsible for leading and
implementing the various initiatives that relate to improving GitLab's security.
Responsibilities
- Develop security training and guidance to internal development teams
- Provide subject matter expertise on architecture, authentication and system security
- Assess security tools and integrate tools as needed, particularly open-source tools
- Assist with recruiting activities and administrative work
- Technical Skills
- Familiar with common security libraries, security controls, and common security flaws that apply to Ruby on Rails applications.
- Ability to discover and patch SQLi, XSS, CSRF, SSRF, authentication and authorization flaws, and other web-based security vulnerabilities (OWASP Top 10 and beyond).
- Knowledge of common authentication technologies including OAuth, SAML, CAs, OTP/TOTP.
- Knowledge of browser-based security controls such as CSP, HSTS, XFO.
- Experience with standard web application security tools such as Arachni, Brakeman, and BurpSuite.
- There should also be time to participate in development of GitLab.
- Code quality
- Proactively identify and reduce security risks.
- Find and remove outdated and vulnerable code and code libraries.
- Communication
- Consult with other Developers and Product Managers to analyze and propose application security standards, methods, and architectures.
- Handle communications with independent vulnerability researchers and design appropriate mitigation strategies for reported vulnerabilities.
- Educate other developers on secure coding best practices.
- Ability to professionally handle communications with outside researchers, users, and customers.
- Ability to communicate clearly on technical issues.
- Performance & Scalability
- An understanding of how to write code that is not only secure but scales to a large number of users and systems.
Requirements
- You have a passion for security and open source
- You are a team player, and enjoy collaborating with cross-functional teams
- You are a great communicator
- You employ a flexible and constructive approach when solving problems
- You share our values, and work in accordance with those values
- Ability to use GitLab
Levels
- Leverage understanding of fundamental security concepts
- Triages/handles basic security issues
- Be positive and solution oriented
- Good written and verbal communication skills
- Constantly improve product security
Senior Security Engineer
The Senior Security Engineer role extends the Intermediate Security Engineer role.
- Leverages security expertise in at least one specialty area
- Triages and handles/escalates security issues independently
- Conduct security architecture reviews and makes recommendations
- Great written and verbal communication skills
- Screen security candidates during hiring process
A Senior Security Engineer may want to pursue the security engineering management track at this point. See Engineering Career Development for more detail.
Staff Security Engineer
The Staff Security Engineer role extends the Senior Security Engineer role.
- Recognized security expert in multiple specialty areas, with cross-functional team experience
- Make security architecture decisions
- Provide actionable and constructive feedback to cross-functional teams
- Implement security technical and process improvements
- Exquisite written and verbal communication skills
- Author technical security documents
- Author questions/processes for hiring and screening candidates
- Write public blog posts and represent GitLab as a speaker at security conferences
Specialties
Application Security
Application Security specialists work closely with development, product security PMs, and third-party groups (including paid bug bounty programs) to ensure pre and post deployment assessments are completed. Initiatives for this specialty also include:
- Pre and post deployment security assessments/tests
- Capture of flaws in software environment configuration
- Malicious code detection
- Patch/upgrade
- IP filtering
- Lock down executables
- Monitoring of programs at runtime to enforce the software use policy
- Developing and implementing a Secure Software Development Lifecycle (S-SDLC)
- Training and coaching developers on current security best practices
Application Security Responsibilities
- Own vulnerability management and mitigation approaches
- Conduct threat modeling tied to security services
- Conduct application security reviews
- Implement secure architecture design
- Provide security training and outreach to internal development teams
- Develop security guidance documentation
- Assist with recruiting activities and administrative work
- Define, implement, and monitor security measures to protect GitLab.com and company assets
Application Security Requirements
- Familiarity with common security libraries, security controls, and common security flaws that apply to Ruby on Rails applications
- Some development experience (Ruby and Ruby on Rails preferred; for GitLab debugging)
- Experience with OWASP, static/dynamic analysis, and common exploit tools and methods
- An understanding of network and web related protocols (such as, TCP/IP, UDP, IPSEC, HTTP, HTTPS, routing protocols)
- Familiarity with cloud security controls and best practices
Application Security Hiring Process
Candidates for Application Security can expect the hiring process to follow the order below. Please keep in mind that candidates can be declined from the position at any stage of the process. To learn more about someone who may be conducting the interview, find her/his job title on our team page.
Screening call with Recruiter
Round 1 (Scheduled in Parallel)
- 60 Minute Interview with Hiring Manager
- 45 Minute Peer Interview
Round 2
- 60 Minute Interview with Director of Security
As always, the interviews and screening call will be conducted via a video call.
See more details about our hiring process on the hiring handbook.
Security Automation
Security Automation specialists help us scale by creating tools that perform common tasks automatically. Examples include building automated security issue triage and management, proactive vulnerability scanning, and defining security metrics for executive review. Initiatives for this specialty also include:
- Assist other security specialty teams in their automation efforts
- Assess security tools and integrate tools as needed
- Define and own metrics and KPIs to determine the effectiveness of security programs
- Define, implement, and monitor security measures to protect GitLab.com and company assets
Security Automation Responsibilities
- Build security tooling and automation for internal use that enable the security team to operate at high speed and wide scale
- Define and own metrics and key performance indicators to determine the effectiveness of security programs
- Define, implement, and monitor security measures to protect GitLab.com and company assets
Security Automation Requirements
- Previous experience on a Security Operations team, especially experience coordinating responses to security incidents
- Scripting/coding experience with one or more languages
- Extensive knowledge of Internet security issues, cloud architectures, and threat landscape
- Solid understanding of the Software as a Service (SaaS) model
- Experience with Cloud Computing Platforms - GCP experience a plus
Security Engineers at GitLab work on securing our product and on internal security. On the product side, this includes the open source version of GitLab, the enterprise editions, and the GitLab.com service. Security Engineers work with peers on cross-functional teams dedicated to areas of the product. They also work together with product managers, developers, and the infrastructure teams to solve common goals.
Security Operations
Security Operations Engineers are the firefighters of the GitLab Security Team. As a Security Engineer in Operations your daily duties will include incident response, log analysis, forensics, tooling and automation development, as well as contributing to strategic improvements to the GitLab products and GitLab.com services. Successful Security Engineers thrive in high-stress environments and can think like both an attacker and defender, have the ability to engage with and mentor more junior Security Engineers, and can help come up with proactive and preventative security measures to keep GitLab and its user’s data safe.
Security Operations Responsibilities
- Detect and respond to company-wide security incidents
- Log analysis
- Security forensics
- Develop and implement preventative security measures (detection, monitoring, exploitation)
- Build security tools that enable the GitLab Security Team to operate at speed and scale
- Incorporate current security trends, advisories, publications, and academic research
- Engineer CND technologies to monitor and analyze (e.g. IDSes, Data collection tools)
- Vulnerability management - triage and manage vulnerabilities identified through scanning and manual efforts
- Identify and mitigate complex security vulnerabilities before an attacker exploits them
- Communicate risks and mitigations across multiple audiences with varying levels of sensitivity
Security Operations Requirements
- 5+ years of demonstrated experience in web or cloud security engineering, log aggregation, and/or penetration testing
- 2+ years of direct experience with incident response
- Experience with log analysis systems
- Engineer, not an analyst mindset
- In-depth knowledge of Linux tools/architecture and logging systems
- Experience with Google Cloud Platform (GCP), AWS, and/or Azure
- Experience with one or more programming languages (Ruby on Rails, Go, PHP and/or Python)
- Proficiency to communicate over a text-based medium (Slack, GitLab Issues, Email) and can succinctly document technical details.
Security Operations Hiring Process
Candidates for Security Operations can expect the hiring process to follow the order below. Please keep in mind that candidates can be declined from the position at any stage of the process. To learn more about someone who may be conducting the interview, find her/his job title on our team page.
Screening call with Recruiter
Round 1
- 60 Minute Interview with Hiring Manager
Round 2 (Scheduled in Parallel)
- 45 Minute Peer Interview
- 45 Minute Peer Interview
Round 3
- 60 Minute Interview with Director of Security
As always, the interviews and screening call will be conducted via a video call.
See more details about our hiring process on the hiring handbook.
Anti-Abuse
Anti-Abuse Engineers are the builders of the Anti-Abuse world. They develop the tools needed to monitor, mitigate and report on abusive behavior and are an essential part of our goal to be good internet citizens.
A successful candidate is someone who wants to make the internet a safer place and do the right thing because it’s right.
Your daily duties will include building tooling and automation for curbing abuse, assist with incident response, as well as contributing to strategic improvements to the GitLab products and GitLab.com services.
Anti-abuse Responsibilities:
- Initiatives for this specialty include:
- Three main abuse types:
- Continuous Integration
- Content
- Spam
- DMCA Notice and Counter-Notices (dmca@gitlab.com)
- Mitigation of abusive/non-responsive customers
- Verifying the proper classification of abuse reports
- Escalating to stakeholders while continuing to monitor
- Monitoring logs and queues for trends
- Research and prevention trending abuse methodologies
Anti-Abuse Requirements:
- 3+ years of demonstrated experience in a developer role
- 2+ years experience in Anti-Abuse processes or mitigation
- Broad knowledge of technology, and be passionate about it. Able to discuss and explain popular, internet-based technologies with ease, and present their experience with them.
- Development, scripting, or automation experience - A successful candidate is a builder. They dislike repetitive tasks and have a history of automating their daily workflows to make their days more productive. They are comfortable writing in Python, Ruby, or similar scripting languages, while also being able to read and interpret code from other languages.
- Good communication and documentation skills
- Knowledge of Linux tools/architecture and logging systems
Experience with SQL
- Nice to Have: Experience with Google Cloud Platform (GCP), AWS, and/or Azure
Anti-Abuse Hiring Process
Candidates for Anti-Abuse can expect the hiring process to follow the order below. Please keep in mind that candidates can be declined from the position at any stage of the process. To learn more about someone who may be conducting the interview, find her/his job title on our team page.
Screening call with Recruiter
Round 1
- 60 Minute Interview with Hiring Manager
Round 2 (Scheduled in Parallel)
- 45 Minute Peer Interview
- 45 Minute Peer Interview
Round 3
- 60 Minute Interview with Director of Security
As always, the interviews and screening call will be conducted via a video call.
See more details about our hiring process on the hiring handbook.
Compliance
Compliance specialists enables Sales by achieving standard as required by our customers. This includes SaaS, on-prem, and open source instances.
Red Team
Red Team specialists emulate adversary activity to better GitLab’s enterprise and product security. The role requires the ability to think like an advanced persistent threat. Creativity is key. For example, develop attack plans and stealthily execute them to compromise sensitive information on GitLab.com such as private repos, or develop and distribute malware to GitLab team-members to demonstrate how the corporate enterprise could be compromised.
- Utilize threat modeling concepts and frameworks such as MITRE ATT&CK, STRIDE, etc. to continually identify ways to protect and defend GitLab assets by executing attacks that emulate a range of adversaries
- Focus on designing, researching, and executing attacks to challenge the blue team
- Strive to identify weaknesses within GitLab products and corporate network and demonstrate the associated risks
- Contribute to the GitLab Secure and Defend products
- Incorporate current security trends, advisories, publications, and academic research
- Understand CND technologies to bypass these security controls and stay undetected
- Report on the Red Team engagements providing an in-depth analysis of the security issues identified
- Identify complex security vulnerabilities and exploit them before an external attacker can exploit them
- Determine the level of effort required to compromise sensitive data
- Publish blog posts and present talks at security conferences
- Contribute to GitLab products by testing and proposing new features
Strategic Security
Strategic security specialists focus on holistic changes to policy, architecture, and processes to reduce entire categories of future security issues. Initiatives for this specialty also include:
- Cluster related historical security issues and examine them as a larger set
- Identify and generate trends associated with each set
- Propose actionable changes to GitLab architecture, processes, and infrastructure to mitigate future issues within each set
- Generate metrics which measure the effectiveness of each mitigation implemented
Security Research
Security research specialists conduct internal testing against GitLab assets, and against FOSS that is critical to GitLab products and operations. Initiatives for this specialty also include:
- Conduct vulnerability research against all GitLab and GitLab.com assets
- Research FOSS tools that are integrated with GitLab
- Develop proof-of-concept code to be included in security findings
- Report findings to tool developers and track mitigation process
- Follow responsible disclosure policies for community disclosure
- Author blog posts on vulnerabilities discovered
Hiring Process
Candidates for this position can expect the hiring process to follow the order below. Please keep in mind that candidates can be declined from the position at any stage of the process. To learn more about someone who may be conducting the interview, find her/his job title on our team page.
Screening call with Recruiter
Round 1 (Scheduled in Parallel)
- 60 Minute Interview with Hiring Manager
- 45 Mintue Senior Peer Interview
Round 2 (Scheduled in Parallel)
- 60 Minute Interview with Director of Security
- 60 Minute Interview with VP of Engineering
- Successful candidates will subsequently be made an offer via email
As always, the interviews and screening call will be conducted via a video call.
See more details about our hiring process on the hiring handbook.
Security Engineers have the following job-family performance indicators.
Application Security
Security Operations
Abuse Operations and Handling
Apply
Please note that if we are actively hiring for a position, you will see it
listed on our jobs page, where all of our current openings are
advertised. To apply, please click on the name of the role you are
interested in, which will take you to our applicant tracking system (ATS),
Greenhouse.
Avoid the confidence gap; you do not have to match all the listed
requirements exactly to apply. Our hiring process is described in more
detail in our hiring handbook.
About GitLab
GitLab Inc. is a company based on the GitLab open-source project. GitLab is
a community project to which over 1,000 people worldwide have contributed.
We are an active participant in this community, trying to serve its needs
and lead by example. We have one vision: everyone can
contribute to all digital content, and our mission is to change all creative
work from read-only to read-write so that everyone can contribute.
We value results, transparency, sharing, freedom,
efficiency, self-learning, frugality, collaboration, directness, kindness, diversity and inclusion,
boring solutions, and quirkiness. If these values match your personality,
work ethic, and personal goals, we encourage you to visit our
primer to learn more. Open source is our culture, our way of
life, our story, and what makes us truly unique.
Top 10 reasons to work for GitLab:
- Work with helpful, kind, motivated, and talented people.
- Work remote so you have no commute and are free to travel and move.
- Have flexible work hours so you are there for other people and free to plan
the day how you like.
- Everyone works remote, but you don't feel remote. We don't have a head
office, so you're not in a satellite office.
- Work on open source software so you can interact with a large community and
can show your work.
- Work on a product you use every day: we drink our own wine.
- Work on a product used by lots of people that care about what you do.
- As a company we contribute more than we take, most of our work is released
as the open source GitLab CE.
- Focused on results, not on long hours, so that you can have a life and
don't burn out.
- Open internal processes: know what you're getting in to and be assured
we're thoughtful and effective.
See our culture page for more!
Work remotely from anywhere in the world. Curious to see what that looks
like? Check out our remote manifesto and guides.
