Skip to content

GitLab

Threat Research Engineer, Security Factory: Threat Research

GitLab is hiring a Threat Research Engineer, Security Factory: Threat Research for a remote role open to applicants in Israel. It pays PLN 272k-PLN 408k a year and Level rates it ; you can apply on GitLab.

Level's read on this job

  • Level rates this role Uses AI ●●○○: an ordinary role that requires AI tools.
  • The posting lists this role as remote.
  • Tools and skills the posting cites include LangChain, LangGraph and AI agents.
  • Level lists 251 other open roles at GitLab.
  • The role was posted in the last few days.

AI in this role

LangChainLangGraph
ai-agents

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 a Threat Research Engineer, you’ll take ideas from the first question to a working proof of concept, deploy it, and analyze the results yourself. This is a full-stack role, with AI central to how we work. You’ll build agentic workflows for research, analysis, and detection, and use AI tools every day to move faster.

What you’ll do

  • Research new attack surfaces and threat vectors, including AI coding agents, agent plugins, and package ecosystems.
  • Find and responsibly disclose vulnerabilities in open source projects and developer tools.
  • Analyze software supply chain incidents and events.
  • Build AI-powered workflows and agents that automate research, analysis, and detection.
  • Build and maintain the cloud-based systems behind our detection and advisory work.
  • Improve the quality and coverage of our vulnerability and malware advisories.
  • Write up your findings as blog posts and present them at conferences.
  • Take part in on-call or operational support where your team's ownership model requires it.

What you’ll bring

  • Hands-on security experience in research, malware analysis, penetration testing, or security tooling, with both a developer mindset and an adversarial mindset: you can build systems and think about how to break them.
  • Demonstrated experience using AI in real work, such as building with large language model APIs or agent frameworks like LangChain, LangGraph, or agent SDKs.
  • Strong programming skills in Go or Python, with good software engineering practices including testing, code review, continuous integration and continuous delivery, and maintainable code.
  • Experience deploying and running production services on a public cloud.
  • Understanding of how package ecosystems work and how software supply chain attacks happen.
  • Ability to map possible attack vectors, name trade-offs, and make data-driven decisions, balancing quality and speed with customer outcomes in mind while keeping up with security and AI industry trends.
  • Clear writing that explains findings to both engineers and a general audience.
  • Helpful, but not required: published vulnerability findings; security research on AI agents, large language model applications, or Model Context Protocol (MCP) servers; Google Cloud Platform experience; or infrastructure as code experience with Terraform or OpenTofu.

You don’t need deep knowledge of compilers or static application security testing engines. A high-level understanding is enough.

About the team

The Threat Research group researches security threats as they emerge and turns what we learn into protection for GitLab customers. We maintain the GitLab Advisory Database, which powers GitLab’s dependency scanning. We also build detection capabilities, do original vulnerability research, and publish what we find. Recent work includes the Shai-Hulud npm worm and a critical remote code execution vulnerability in Serena, a popular MCP coding agent. You can read more on the Security Labs blog.

The base salary range for this role’s listed level is currently for residents of the EU, applicable in the specified country or countries only. Sales roles are also eligible for incentive pay targeted at up to 100% of the offered base salary. Grade level and salary ranges are determined through interviews and a review of education, experience, knowledge, skills, abilities of the applicant, equity with other team members, alignment with market data, and geographic location and having regard to any applicable collective agreements. The base salary range does not include bonuses, equity, or benefits.

Poland base salary range: 272,000 - 408,000 PLN

How GitLab Supports Full-Time Employees

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.

How we rate this

Threat Research Engineer, Security Factory: Threat Research at GitLab rates 48 out of 100 for how much of the daily work is AI. That makes it Uses AI (AI Level 2 of 4). The level is about AI in the job, not seniority.

Classification

Uses AI. An ordinary role that requires AI tools.

  1. ●●●● Builds AI80 to 100
  2. ●●●○ Works on AI60 to 79
  3. ●●○○ Uses AI40 to 59
  4. ●○○○ Little AI0 to 39

Levels come from how often the tools, models and workflows of the role are named in the posting itself. Read the description and count the AI tools, models and workflows it names.

Prepare for this job

Built from this posting and from similar jobs on Level.

Skills and AI tools this role asks for

AI agentsLangChainLangGraph

Questions you could be asked

  1. How do you decide when an AI agent can act on its own versus asking for approval first?
  2. Walk me through how you've used LangChain in your day-to-day work.
  3. What are the limits of LangGraph that you've run into, and how did you work around them?
  4. This role expects you to use AI tools as part of the job. Which ones have you used, and for what?
  5. Tell me about a time an AI tool got something wrong. How did you catch it?

Adapt your resume

  • List these exact terms on your resume: AI agents, LangChain, and LangGraph. An applicant tracking system matches the wording, not the idea.
  • Attach one line of real, concrete experience to at least one of them. A tool named with nothing behind it rarely survives a human read.
  • Put the AI tool in a bullet point about what you did, not just in a skills list. This role treats it as a required part of the job.

Get your CV reviewed before you apply

Send your CV and the role you want next. Your review arrives by email within 3 days.

Get new remote research jobs (Uses AI ●●○○ or higher) by email

One email a week, each job rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.

Free.

Similar roles

Research roles that use AI, at other companies.

What kind of AI work fits you?

Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.

Find my next step

More jobs at GitLab

Related searches

Same AI level