Product Manager: Core Platform

Product Manager: Core Platform

About XBOW

Build the future of offensive security with XBOW. Attackers are already using AI to move faster than defenders can react—we’re creating the platform that puts security ahead in the arms race. Our AI-powered system autonomously discovers, validates, and even exploits vulnerabilities, giving organizations proof-backed results in hours instead of weeks.

Founded by Oege de Moor, creator of GitHub Copilot, and backed by Sequoia, Altimeter, and other leading investors, XBOW is applying cutting-edge AI to one of the world’s most urgent problems. In just over a year, our AI, built by a world-class AI team and legendary security researchers — has uncovered thousands of real-world zero-days across the software billions rely on, and achieved the #1 ranking on HackerOne’s global leaderboard.

We’re a team of builders, hackers, and researchers who thrive on solving problems others think are impossible. If you want to push the boundaries of AI, reshape how security is done, and join the group defining this new era of defense — we’d love to talk.

Your Role: Product Manager for Core Platform

XBOW's product has grown fast. Some foundational things now need to be rethought, not just patched. We're looking for a PM to own that work -- the core platform layer that every user touches but nobody explicitly asked for. Configuration flows, scope enforcement, data navigation, input validation. The stuff that separates "technically works" from "actually good."

A lot of this work is ambiguous. A customer hits a confusing behavior, a support ticket gets filed, and the easy fix is a tooltip or a validation message. But the actual problem might be that the underlying abstraction is wrong -- that the product's model doesn't match how customers think about the domain. You need to be the person who sees that, and who has the taste to know what "right" looks like even when nobody's written a spec for it.

These problems span UX and architecture at the same time. Fixing them means bridging between designers, frontend engineers, backend engineers, and infrastructure -- understanding what each side cares about and translating across those boundaries. Not just technically, but interpersonally. Foundational changes are hard to land because they affect everyone.

This is not a general PM role. If you only think in wireframes or only think in system diagrams, this isn't the right fit. We want someone with a real point of view on how products should work, the engineering fluency to back it up, and the growth trajectory to keep getting better at both.

What you will do

• Own foundational platform improvements — Spec and ship changes to core workflows that other features build on: how users configure what gets tested, how the platform enforces boundaries, how results get surfaced

• Fix the defaults — Identify places where the product lets users silently misconfigure things, and build the validation and guardrails that prevent it

• Rethink core abstractions — Some of our primitives were designed for an earlier version of the product. You'll lead the work to evolve them -- which means understanding the downstream impact on multiple system layers

• Make data accessible — Users shouldn't have to drill through multiple screens to answer basic questions about their results. Fix that

• Navigate cross-team changes — Foundational work touches many teams. You need to understand blast radius, negotiate tradeoffs, and bring people along without having authority over them

• Write specs engineers respect — Your PRDs should demonstrate you understand the technical constraints, not just the desired outcome

What You've Done:

• Shipped product changes that required coordinating across frontend, backend, and infrastructure -- not just UI features

• Worked on products where misconfiguration has real consequences: security tools, infrastructure platforms, developer tools, cloud services

• Made or heavily influenced architectural decisions as a PM -- you understand system boundaries, data flow, and why "just add a checkbox" is sometimes a multi-sprint project

• Designed configuration or setup flows that meaningfully reduced user confusion and support load

• Operated in a startup or high-growth environment where you owned problems end-to-end

What Sets You Apart:

• You fix the root problem, not the symptom. When a user complains about a confusing error message, you ask whether the error should exist at all

• You're comfortable when things are undefined. You don't stall waiting for requirements -- you go figure out what the right thing to build is

• You have UX instincts backed by engineering fluency. You can explain to an engineer why something matters and roughly how to fix it

• You bring people along. Foundational changes are hard to land -- you know how to build alignment across teams that don't report to you

• You're measurably better at your job than you were a year ago, and you expect the same next year

• You write well. Not marketing copy -- clear, technical writing that engineers actually read

Our Stack (for this role)

• GitHub (Issues, Projects, Actions)

• Networking and proxy concepts are relevant but you'll learn the specifics here

• Security domain knowledge helpful but not required

What we offer

• Compensation & Equity: Competitive salary and equity package, making you a true owner of the company.

• Career Growth: Shape your role, lead the function, and grow with the company as we redefine cybersecurity.

• Meaningful Work: You will tackle technically complex challenges and play a pivotal role in the growth of our business, working alongside an amazing team and some of the world’s experts to shape how AI transforms cybersecurity.

What else you should know

• Location: US-Eastern Remote, Europe Remote (all team members are remote but we meet regularly and you’re supported to travel to collaborate with colleagues in person)

• Contract: Full-time.

• Hiring Process:

• 45-min introductory chat with our Head of Talent, Zac Wallis.

• 45 minutes with our Head of Product, Aqeel Siddiqui.

• Take home assessment.

• Presentation of take home assessment to product team.

• 45 minute interview with Engineering Leader

We aren't focused on seniority titles at XBOW—so if you’re worried about “leveling,” don’t be. We care a lot more about mission fit, capability, and impact than what’s on your LinkedIn headline.

We believe in people who are driven by curiosity and a willingness to learn. Even if you don't check every box, we encourage you to apply if you're excited about the role and our mission.