About the role
The people worth reaching already know their problem: they have tried a RAG prototype, watched it return something unsafe, and realised the model was never the issue. Our job is to be findable and credible at that exact moment.
That makes this a technical marketing role. The content that works here is a worked example, an honest benchmark, or a field note explaining a failure mode, not adjectives. You would own positioning, the site's story, the top of the funnel and the measurement of what actually converts.
There is one hard rule: the site only claims what ships. Anything unbuilt is labelled planned. If that constraint sounds like an obstacle rather than an asset, this will be a frustrating job.
What you'd do
- Own positioning and the site's story: what the product does today, with anything unbuilt labelled as planned
- Run content that earns technical trust: field notes, worked examples, honest benchmarks
- Build the top of the funnel across search, developer communities and partnerships, and measure what actually converts
- Work with product on launches, pricing pages and the first-run experience
- Own the numbers: what a channel costs, what it returns, and when to stop doing it
What we need
- Four or more years in marketing or growth, with real ownership of a funnel
- You can write. Not brief a writer: write, about a technical product, accurately
- You have run acquisition experiments and can describe one that failed and what it taught you
- Comfortable in analytics tooling without needing someone to pull the numbers for you
- You are happy selling something honestly rather than maximally
Nice to have, not required
- You have marketed a developer tool, an API or infrastructure
- SEO experience on a technical site with real content depth
- You have run a launch that involved a community rather than a press release
How we work
- Small team, thin slices, shipped weekly. Nothing sits on a branch for a month.
- Reviews are real. Every feature ships with its tests, and a bug found in review is cheaper than one found by a customer.
- Safety-critical means the boring answer usually wins: fail closed, keep the receipt, don't guess.
- We only claim what ships. That applies to the product, the roadmap and the offer letter.
How hiring works
- 1A 30-minute call about something you've built and what was hard about it.
- 2A working session on a real problem from this codebase. You can drive, or we can pair.
- 3A conversation about how you make decisions when the evidence is thin.
- 4References, then an offer. We aim to answer within a week at every stage.