GitLab - Senior Product Manager, Secret Detection and Vulnerability Research
Requirements
• Domain depth in application security, vulnerability management, or security research. You have worked on or adjacent to scanners, detection content, threat intelligence, or SDLC security tooling and you know how these products actually get evaluated in a bake-off. • Domain depth • Technical credibility sufficient to earn the respect of a security engineering team. You do not need to have written the scanner, but you should be able to reason about detection logic, data pipelines, CI integration, and the tradeoffs between coverage and noise. • Technical credibility • Commercial reasoning. You start from revenue mechanics, buyer motion, and competitive displacement, then work inward to product decisions. Candidates who reason only from feature lists outward are not a fit. • Commercial reasoning. • Evidence of using AI as a force multiplier in your own work: research, analysis, data pulls, prototyping, drafting. Consuming a chat assistant occasionally is not the same as restructuring how you work. • Evidence of using AI as a force multiplier • Judgment under ambiguity. You bring structured options and a recommendation instead of escalating an open question. • Judgment under ambiguity. • Bias for clarity. You can take a noisy, technical, politically contested problem and produce one page that everyone can align on. • Bias for clarity. • Bonus: hands-on background as a developer, security engineer, red teamer, or researcher; experience with credential and token ecosystems; experience commercializing a data or intelligence asset. • Bonus: • This role sits in GitLab's Security product management organization, which owns application security testing, vulnerability management, supply chain security, secrets management, and AI governance. The Security Section is central to GitLab's Ultimate tier and to the shift toward consumption-based product revenue, so the work is visible to senior leadership and directly tied to company results. You will work asynchronously with engineering, design, and research counterparts across multiple regions, and with the Field teams who take this to market. • How GitLab Supports Full-Time Employees • Benefits to support your health, finances, and well-being • Flexible Paid Time Off • Team Member Resource Groups • Equity Compensation & Employee Stock Purchase Plan • Growth and Development Fund • 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. • Country Hiring Guidelines:
Responsibilities
• Own the business outcomes for Secret Detection and Vulnerability Research, including adoption, expansion, competitive win rate, and revenue contribution. Bring a point of view on packaging and pricing, not just features. • Set the strategy for the full secret lifecycle: prevention, detection, validation, revocation, and reporting across GitLab.com, Dedicated, and Self-Managed. • Treat detection content as a product. Define how rules, advisories, and intelligence feeds are sourced, validated, versioned, and measured, and make quality visible to customers. • Treat • Hold the line on detection quality. False positives are a product defect and you will own the metrics that prove precision is improving. • Work at the level of the technology. Read the rule syntax, question the entropy heuristics, understand why a scanner missed something, and challenge engineering with informed alternatives. • Use AI to compress the distance between question and answer. Pull your own data, prototype your own flows, synthesize research and competitive input yourself, and bring conclusions rather than requests for someone else to investigate. • Build the case for where AI belongs in the product: triage, rule generation, remediation guidance, and reducing the human review burden per finding. • Build • Partner with engineering, security research, threat intelligence, Field, and GitLab's own Security team, who are one of your most demanding users. • Partner • Communicate in writing, asynchronously, with enough precision that a distributed team can act without a meeting. • Communicate
Apply in one click
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT