About the Role
As a Member of Technical Staff on the Product Security Team, you will sit at the intersection of technical vulnerability analysis, cross-functional remediation, and customer-facing transparency. Your primary mission is to translate complex technical security findings into clear, accurate advisories while driving the operational follow-through needed to get products patched. We are looking for an analytical, detail-oriented engineer who thinks critically about how systems fail-evaluating real-world exploitability and blast radius-and uses that insight to coordinate fixes across engineering teams and communicate risk clearly to our customers.
About the Team
PSIRT is a growing center of excellence dedicated to the security of our products and the trust of our customers. We focus on “doing the right thing” by our users, investing in proactive defense, data-driven decisions, and clear communication. Our team values collaborative engineering and operational integrity. As we scale, we are looking for driven practitioners who are passionate about understanding software vulnerabilities, streamlining remediation workflows, and maintaining the highest standards of customer trust.
Responsibilities
Security Advisories & Disclosure Lifecycle: Draft, review, and manage the end-to-end lifecycle of Security Advisories, Knowledge Base (KB) articles, and CVE registrations (supporting our CNA process). Ensure every publication distills complex root-cause analysis into clear, actionable guidance for customers
Vulnerability Triage & Impact Analysis: Partner with Security Engineers to validate reported bugs and third-party library risks. Apply an adversarial mindset to assess real-world exploitability, potential attack paths, and the exact “blast radius” across product versions to ensure accurate CVSS scoring.
Cross-Functional Remediation Tracking (TPM): Drive vulnerability remediation across Engineering, Product Management, and Support. Track milestones, manage third-party dependency upgrade timelines, and proactively unblock bottlenecks to keep fixes aligned with release schedules.
Cross-Team Alignment: Collaborate with Legal, Support, and PR during active security incidents to ensure external messaging is technically accurate, timely, and aligned with company standards.
Playbooks & Operational Visibility: Help standardize incident briefing templates, disclosure workflows, and reporting dashboards (leveraging SBOM and asset data) to improve visibility into security debt and remediation progress.
Qualifications
What you’ll bring to the team:
Relevance Experience: 2-5 years of experience in Product Security, PSIRT Operations, Application Security, Security Consulting, or Technical Program Management within a software engineering environment,
Analytical & Clear Communicator: A proven ability to take deep-tier technical data, bug reports, or architectural details and translate them into crisp, authoritative documentation for both developers and external customers.
The “Adversarial Eye”: A solid technical foundation is how software vulnerabilities work (e.g. OWASP Top 10, authentication bypasses, logic flaws) and how minor issues can be chained together, enabling you to accurately evaluate risk and CVSS severity.
Programmatic & Organized Mindset: Strong project management skills with the ability to juggle multiple active advisories, track dependencies, and hold cross-functional teams accountable to deadlines
SDLC Familiarity: A working understanding of the software development lifecycle and the operational realities of patching and upgrading third-party libraries in enterprise software.
Bonus points if you have:
Experience supporting CNA (CVE Numbering Authority) process or working with MITRE/FIRST disclosure standards.
Familiarity with modern vulnerability and supply chain formats such as VEX, CSAF, or SBOMs, as well as SCA (Software Composition Analysis) tools.
Basic scripting skill (e.g., Python) to help automate vulnerability tracking, data parsing, or reporting.
Hands-on experience reproducing bugs, reading code snippets, or validating proofs-of concepts (PoCs)