Product Marketing Manager

About Plane Plane's mission is to build the infrastructure the world's work runs on. Every organization runs on three things: the projects it's driving, the knowledge it keeps, and the requests it fields. Plane brings all three into one open, adaptable platform: simple enough for any team to adopt, dependable enough for organizations to build on. And we are building it for a future where humans and AI agents do that work together. Plane began in public on GitHub at the end of 2022. Since then it has grown into a work management platform used by teams around the world: 55,000+ stars, 5,000+ forks, and a contributor community that reads our code and files our issues. Organizations run Plane as a managed Cloud service, on their own infrastructure, or inside fully isolated environments. Building in the open keeps us close to users and raises the standard for everything we ship. Plane is the #1 work infrastructure in aerospace, defense, financial services, and other regulated industries: organizations whose requirements for control, auditability, and data residency rule most software out. When the strictest buyers pick a system of record, that choice means something. Adoption is growing fastest on Plane Cloud and in sovereign clouds, deployments that keep everything inside a country's own borders and rules. Plane is backed by top investors and built across San Francisco, London, and Hyderabad. We work in tightly knit teams, stay close to users, and care about the visible product as much as the unglamorous details that make software dependable. People own problems end to end, and we add process only when it helps the work. Humans and agents We believe the next decade of work will be done by humans and AI agents together. Not agents replacing people, and not a chat window bolted onto software built for humans clicking around, but both working in one system of action, where an agent's work is as visible and as accountable as a person's. Most software treats AI as a feature. We treat agents as a kind of worker, and that changes what the system underneath has to be. Agents are only as good as the context they can see and the state they are allowed to change, so shared context, explicit state, durable history, and accountable action are not items on our roadmap. They are the product. Plane is built so that when an agent acts, the humans responsible can see what happened, why, and on whose authority, and the record survives. This is what the infrastructure is for: making the future where humans and agents work together useful, legible, and fully within the organization's control. Every role at Plane is some part of building that. About the role Plane ships one product to three very different buyers: a team that signs up on Cloud in a minute, an organization that runs it on its own infrastructure, and one that runs it on machines with no internet connection. The same release has to be explained to all three, and the differences between what each one gets are real. You own the messaging system underneath that: what we claim for Projects, Wiki, Intake, and Plane AI, the proof behind each claim, and how a launch reaches the site, the docs, Sales, and the community as one story rather than three. You will work with product managers on what shipped, with Sales on the objections that decide enterprise deals, and with the community, who file an issue when a marketing page overstates the product. Key responsibilities Own positioning for Projects, Wiki, Intake, and Plane AI, and the source of truth for every claim and the proof behind it. When someone asks whether we can say something, you decide. Own how capability maps to edition and tier. Cloud, self-hosted commercial, and air-gapped customers get different things, and the page has to say which. Lead launches end to end: narrative, plan, page, announcement, email, in-product copy, and enablement, closed out with a review that names what moved and changes the next launch. Own the product, solution, industry, and comparison pages. These get read mid-evaluation against Jira, Asana, Monday.com, and ClickUp by people who use the competitor daily. Run the research the positioning rests on: customer and prospect interviews, lost-deal reasons, community threads, and competitive moves, turned into language we can publish. Work weekly with product managers, design, Sales, and the community team, and take contested claims to the engineer who built the feature before they ship. Maintain the library that goes stale on its own: battlecards, edition explainers, demo scripts, and FAQs. Check claims against the docs one page at a time before every launch, because an overstated claim returns as a support ticket or a lost deal. What you'll bring You have owned positioning that changed results. You can name the product, the claim you changed, and what moved after: adoption, conversion, or win rate. You ship the copy, not only the brief. Web-ready pages and launch assets that went live under your