Responsibilities

• Translate product into positioning
• - Take what the product and engineering teams build and turn it into messaging that resonates with buyers — not feature lists, but narratives about what the product enables and why it matters
• - Own the product messaging framework: value propositions by persona (business owner, operations manager, sales leader), by vertical (solar, insurance, recruitment, healthcare), and by use case (inbound, outbound, responder)
• - Write and maintain the core positioning documents that sales, marketing, and the website draw from — ensuring consistency across every touchpoint
• Launch features so customers actually notice
• - Own the go-to-market process for new features and product updates: coordinating across product, engineering, design, and marketing to ensure launches have the right messaging, the right assets, and the right timing
• - Write release communications — customer emails, in-app announcements, changelog entries, blog posts — in language that explains the value without requiring the reader to understand the technology
• - Build the internal enablement materials that help the sales and customer success teams explain new features confidently: one-pagers, demo scripts, FAQ documents, and objection-handling guides
• Create the content that drives demand
• - Produce product marketing content: case studies, comparison pages, landing pages, product tour scripts, explainer videos (scripting, not production), and webinar content
• - Work with the marketing team to build campaigns around product capabilities — turning "we can do X" into "here's why X matters for your business, and here's the proof"
• - Write for the website and blog — not thought leadership for its own sake, but content tied to search intent, buying signals, and the questions prospects actually ask before they buy
• Understand the market and the customer
• - Build and maintain competitive intelligence — what other AI voice/messaging platforms are saying, charging, and shipping — and ensure the sales team has up-to-date battlecards
• - Talk to customers and prospects to understand how they describe their problems, what language they use, and what they compare the platform against — then feed this back into messaging and positioning
• - Work with the product team to understand what's coming on the roadmap and start shaping the narrative before the feature ships, not after
• Connect product and marketing as a function
• - Attend sprint reviews and product demos so you know what's shipping and can plan communications in advance
• - Be the person marketing turns to when they need to understand a feature, and the person product turns to when they need to know how something should be positioned
• - Maintain the product wiki, help centre content, and customer-facing documentation — ensuring it's accurate, current, and written for the audience, not for the engineering team

Requirements

• - 2–3 years in product marketing, content marketing, or a marketing role where you worked closely with a product or engineering team — not just ran campaigns, but understood what was being sold and why
• - Exceptional writing skills — you can take a complex, technical product and explain it in a way that a non-technical buyer finds compelling. Your writing is clear, concise, and doesn't hide behind jargon
• - Experience turning features into benefits — you instinctively translate "we added multi-currency billing support" into "your international teams can now see costs in their local currency" without being told to
• - Comfortable in a fast-moving environment where you'll need to produce work quickly, iterate based on feedback, and occasionally write the first version of something that's never existed before
• - Familiar with B2B SaaS buying processes — you understand that the person who uses the product isn't always the person who buys it, and you can write for both audiences
• - Organised enough to manage multiple launches, content pieces, and stakeholder requests in parallel without things going silent

Preferred

• - Experience in AI, voice technology, communications platforms, or a technically complex product — you've already solved the "how do I explain this to a non-technical audience" problem before
• - You've written a case study, competitive battlecard, or product one-pager that a sales team actually used (not just filed)
• - You have a portfolio of writing — blog posts, landing pages, email campaigns, product announcements — that demonstrates range and clarity
• - You've worked in a company where product marketing was one person or a very small team, and you built the function rather than inheriting it