About Plain
Plain is customer support infrastructure for B2B companies. Teams like Cursor, Modal, and Mintlify run support on Plain, and more and more of our customers build on it, running their own agents on our API and MCP server. We’re a Series A company doubling down on Plain as the platform that people and agents build support on.
The role
You’ll own how Plain shows up for technical buyers: in AI search, traditional search, developer communities, social, and anywhere engineers and their agents look for tools. You’ll set the content calendar, write the technical version of our story, and make sure what we ship actually gets found.
There’s no shortage of material. Vercel built its own support agent on our API. n8n resolves 70% of support questions on Plain’s agentic infrastructure. Framer uses our API to power its QA pipeline. We just shipped MCP Apps inside Claude and ChatGPT. Our engineers ship every week, and you’ll turn it into content engineers read, share, and cite.
You’ll report to Cole D’Ambra, Head of Demand Generation, and work closely with our community lead, product marketing, customer success, design, and engineering.
What you'll do
•Decide what we say. Own the content calendar, based on sales and customer calls, communities, industry movement, and what engineering is shipping.
•Write for engineers. Deep dives on how customers like Vercel, n8n and Framer build on Plain, tutorials, and technical versions of our team’s guides and stories.
•Own how we’re found. Track how AI search, LLMs and traditional search describe Plain, find where we’re missing or out of date, and fix it.
•Get us listed where people and agents look. Own Plain's presence on review sites, Product Hunt, Reddit, MCP registries and plugin directories, and keep it accurate.
•Run our social presence. Company X and LinkedIn, plus the conversations that matter on Hacker News and Reddit.
•Make every piece go further. Adapt and distribute what we make for technical and non-technical buyers.
•Make launches land with engineers. Work with product marketing so every launch reaches the developers who’ll build on it.
You’re measured on the demos and pipeline from the channels you own, not on how much you publish.
This is a great fit if ...
•You've written for a developer tool, API or infrastructure company, and understand how organic discovery works.
•When you hear a customer built their own agent on our API, your first thought is “I need to write that up.”
•You start from research and first principles, and spot where things are heading before others do
•You like being early to things that don’t have a playbook yet, like getting found by agents.
Nice to have
•You’ve worked as an engineer, even early in your career, or in developer relations
•Video, podcasts or an audience of your own
•You use AI agents to research, write and publish faster, and you still own the thinking and the quality
This is not a great fit if ...
•You want to hire an agency before you’ve written anything.
•You need a brief, a messaging doc and three rounds of approval before you start.
•Your best work only happens in 3,000-word originals.
•You’d rather maintain docs than get things found.
•“It got a lot of views” is where your story ends.