Staff Software Engineer, Security Factory: Static Analysis

Staff Software Engineer, Security Factory: Static Analysis

Full-Time 63000 - 77000 £ / year (est.) Remote
GitLab Inc.

At a Glance

  • Tasks: Lead the development of a cutting-edge static analysis engine to enhance software security.
  • Company: Join GitLab, a trusted platform for over 50 million users in DevSecOps.
  • Benefits: Enjoy flexible paid time off, equity compensation, and a supportive work environment.
  • Other info: Remote work opportunities with a focus on career growth and mentorship.
  • Why this job: Make a real impact on software security while working with innovative AI technologies.
  • Qualifications: Experience in software development, particularly in Rust or Go, and a passion for security.

The predicted salary is between 63000 - 77000 £ per year.

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.

As a Staff Backend Engineer on GitLab's Security Factory: Code Scanning team, you help developers find and fix security issues. Those issues live in the code they write, and you set the technical direction for the static analysis engine that finds them.

Your work spans two complementary parts of a complete security analysis:

  • On the engine side, you shape how the static analysis toolkit models a program: parsing source into intermediate representations, resolving symbols, building call graphs, and tracking tainted data across files and languages.
  • On the evaluation side, you build and apply tooling that tests, measures, and validates what the engine finds against benchmark applications with known vulnerabilities.

As a Staff engineer, you hold the picture of what the engine can model and how we measure what it finds, shape the long-range technical goals of the team, and raise the bar for every engineer on it.

What You Do

  • Act as the directly responsible individual (DRI) for the team's highest-scope initiatives from design through delivery, shipping large features with minimal guidance and shaping the long-range goals of the team.
  • Bring systems built by one engineer to team ownership through documentation, tests, and shared review.
  • Set the technical direction for the AI-assisted tooling that implements, reviews, and validates engine changes and findings.
  • Own the architecture of the program model and of the pipeline that turns source code into findings.
  • Solve technical problems of the highest scope and complexity, actively seek out difficult impediments affecting the whole team, and advocate for improvements to quality, security, and performance.
  • Mentor all engineers on the team through code review and pairing, remove blockers to their autonomy, and shepherd the definition and improvement of our internal standards.
  • Participate in on-call rotations to assist troubleshooting product operations, security operations, and urgent engineering issues.
  • Define the overarching architecture and specification documents for the engine, delegate component specifications within them, and drive their implementation.
  • Build and maintain the harness, agent instructions, and agentic skills that keep agent-written code trustworthy.
  • Stay current with research in program analysis and security, run AI-assisted research and spikes, and turn the findings into prototypes, proposals, and upstream contributions.
  • Take part in on-call or operational support where your team’s ownership model requires it.

What You Bring

  • Experience building your own LLM tooling, such as a harness, an agent pipeline, or evaluations.
  • Extensive professional experience writing, testing, and reviewing production code in Rust, Go, or a comparable systems language.
  • Experience with performance optimization and with containerized workflows and CI/CD.
  • A deep program analysis and static analysis background.
  • Deep application security experience, such as vulnerability research or secure code review.
  • Demonstrated capacity to communicate clearly and concisely about complex technical, architectural, and organizational problems.
  • A track record of taking ownership of ambiguous, team-wide problems and shipping them from concept to production.
  • Experience defining a system's overarching architecture and delegating component specifications.
  • A track record of mentoring engineers and raising a team's technical bar.

Helpful Experience

  • Familiarity with popular web or mobile application frameworks.
  • Experience designing guardrails for agent-written code.
  • A record of engaging with the research community.

About The Team

The Security Factory: Code Scanning team develops GitLab's SAST capabilities for customer software repositories. We work closely with the Code Security team on scanning rules & flows, with Composition Analysis on the broader software supply chain, and with other groups across the Sec Section.

Remote-Global

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.

Staff Software Engineer, Security Factory: Static Analysis employer: GitLab Inc.

GitLab is an exceptional employer that champions a fully remote work culture, offering flexibility and autonomy to its employees. With a strong focus on professional development, you will have ample opportunities to grow your legal expertise while collaborating with diverse teams across the globe. The supportive environment fosters innovation and inclusivity, making it a rewarding place for those seeking meaningful employment in the legal field.

GitLab Inc.

Contact Details:

GitLab Inc. Recruitment Team

StudySmarter Expert Advice🤫

We think this is how you could land Staff Software Engineer, Security Factory: Static Analysis

✨Join Local Tech Meetups

Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at GitLab Inc. or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!

✨Contribute to Open Source Projects

Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to GitLab Inc..

✨Tap into Online Developer Communities

Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like GitLab Inc..

✨Explore Job Boards Specifically for Tech Roles

Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like GitLab Inc. that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!

We think you need these skills to ace Staff Software Engineer, Security Factory: Static Analysis

Static Application Security Testing (SAST)
Rust
Go
Ruby
Performance Optimisation
Containerised Workflows
CI/CD

Some tips for your application 🫡

Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.

Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at GitLab Inc..

Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at GitLab Inc. and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!

Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!

How to prepare for a job interview at GitLab Inc.

✨Brush Up on Your Coding Skills

For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.

✨Know Your Tools and Frameworks

Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If GitLab Inc. uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.

✨Showcase Your Projects

Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.

✨Prepare for Behavioural Questions

While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.