Senior Content Marketer

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.

Plane gets evaluated in public. Our docs, our issue tracker, and comparison pages written by competitors are all evidence a buyer collects before they talk to anyone here. You will own the content that meets them there, which means the roadmap of what we publish, the standard every page is held to, and most of the drafts. This is a writing job first. You will work with product managers on what shipped rather than what was announced, with Sales on the objections that stall enterprise evaluations, and with the community team, whose forum threads are a steady supply of real questions.

Own the content roadmap across discovery and evaluation: what gets written, refreshed, consolidated, or killed. You defend those calls with signups, product qualified leads, and assisted conversions rather than pageviews.

Own the comparison and migration surfaces for Jira, Asana, Monday.com, and ClickUp. These pages get read mid-evaluation with a competitor's sales team in the other tab, so they have to be accurate enough to survive that reader.

Write for two audiences without patronizing either. A self-hoster debugging a container upgrade and a VP of engineering justifying a migration budget both have to reach the end of the page.

Turn releases into content that says what changed and who it is for, built from the pull requests and the product manager rather than from the announcement blurb.

Build the proof that shortens an enterprise evaluation: deployment stories, customer evidence, and content on security, governance, and data residency. Much of this means asking regulated customers for permission we will sometimes not get, and writing without it when we do not.

Work daily with product managers, design, and community, and put every technical draft in front of the engineer who built the thing before it goes live.

Do the maintenance: auditing pages that rank for the wrong query, rewriting posts that aged badly after a release, fixing internal links across the site, and consolidating pages that compete with each other.

You ship final drafts You write long form that goes live with light editing, and you can point to three pieces you would still defend a year later.

You have grown organic traffic that converted Keyword strategy, internal linking, refreshes, and topical authority are things you have run end to end, with signups or pipeline at the other end of them.

You write about technical products without distorting them You have covered software you did not build, checked claims against the product, and been corrected by an engineer without it becoming a problem.

You have written competitive content Comparison, migration, or alternatives pages in a category where the other side had a bigger budget than you.

You have editorial judgment about other people's work You can brief a writer, cut a draft in half, and explain why, because part of this job is improving writing you did not do.

You have used Plane, run it self-hosted, or written for an open project whose community will correct you in public.

You have written security, compliance, and deployment content: SSO, audit logs, data residency, air-gapped installs.

You have built templates, docs-adjacent content, or product education that people still use.

You have opinions about what AI search is doing to content strategy, and you have tested them.

Every company says it is different. We will try evidence instead.

The scope is real. We are a passion team serving companies of every size, including some of the largest in the world. Something you ship this month will run inside a Fortune 500 company and a 50-person startup in the same week, and you will hear from both.

The constraints make you better. Plane runs in our cloud, in customers' clouds, and on machines that will never touch the internet. Much of the work happens in the open, where the issues, the fixes, and the roadmap conversations are public. Building software that survives all of that is harder than building an ordinary SaaS product, and it is a better education than most companies can offer.

The people-and-agents future is being built here, in production. We think humans and AI agents will share one system of action for work. We are building t Panchayat Bhavan oh my Godhat system now, for customers who already depend on it, and you will work on that problem directly whatever your role.

Your name is on the work. The teams are deeply connected enough that credit and responsibility both find you fast. That is some pressure. Mostly it is the fun part.

If that sounds like your kind of place, we would like to meet you.

Plane is an equal opportunity employer. We do not discriminate based on race, color, religion, gender identity or expression, sexual orientation, national origin, age, disability, veteran status, or any other protected characteristic under applicable law.