Skip to content
Plane

Senior Content Marketer

India
Senior · FullTime · Go-To-Market (GTM)
POSTED 23 MAR
Apply Ask
Role
239 days opentrue age
Posted 23 Mar
Pay
₹12.2L–₹29.5Lno pay posted
Market p25–p75
₹12.2L–₹29.5L
India · n=9 · 365d to 12 Nov
CompanyPlane →
34open roles
Opened · 30d
+0
Closed · 30d
−0
3d of snapshots · 30d window
Market
28,944open · Senior Other
Opened · 7d
+3,15611% of open
All other
621,591open
All tracked boards · live 17 Nov · n=28,944
Visa
✓licensed sponsor
UK licensed sponsor
✓Worker (A rating)
Checked 15 Nov
Docker

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 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.

What you'll do

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.

Source · PlaneFirst seen 2 NovOriginal ↗