Responsibilities
- Lead and manage a high-performing team of senior PMM ICs
- Define and evolve product positioning and messaging—from platform-wide value props to individual product narratives
- Drive end-to-end product launches: positioning, content, enablement, and GTM coordination
- Personally contribute to strategic product marketing projects, such as flagship launches, integrations, and competitive explainers
- Set the bar for developer-first marketing quality across blogs, decks, videos, landing pages, and more
- Partner closely with Product and Engineering to ensure technical depth and messaging accuracy
- Work cross-functionally with Developer Relations, Community, Content, and Distribution to scale and activate product stories
- Build repeatable processes and messaging frameworks that help the team scale with quality and consistency
About You
- You’ve led PMM teams made up of senior ICs, especially in developer-first companies (infra, data, OSS, DevTools)
- You’re comfortable working closely with engineers and product managers—and can translate specs and architecture into value-driven messaging
- You’ve personally led successful product launches and know how to create marketing moments that resonate with developers
- You’re a strong storyteller with an eye for clarity, credibility, and technical depth
- You know how to coach and guide ICs, helping them raise the bar while staying aligned to business goals
- You collaborate fluidly across functions: PM, Eng, DevRel, Marketing Ops, and Sales
You Could Be a Great Fit If You
- Have a background in infrastructure, databases, or developer tools
- Know what great developer marketing looks like—and what developers instantly ignore
- Are just as comfortable editing a blog as you are pitching positioning to technical execs
- Have a portfolio of content, launches, or messaging frameworks you’re proud of
- Thrive in fast-moving, high-growth environments where you need to lead and execute
You Might Not Be a Fit If You
- You are not located in or able to travel regularly to the Bay Area or NYC
- You prefer managing managers or a highly structured, top-down org
- You aren’t comfortable working with technical products and developer audiences
- You need rigid role definitions instead of collaborating fluidly across teams