Freelance SEO/AEO Technical Writer

there is only one of me, and that is becoming a problem 🫠

quick context: I run SEO + AEO at PostHog, which means I spend my days convincing google and several LLMs that we're worth their attention. it's working – it's our fastest-growing channel (yay!!), but our content production is currently bottlenecked by lack of bandwidth (booo).

the bottleneck is me. I am the bottleneck.

since cloning myself isn't an option yet, I'm hiring a couple of 𝗳𝗿𝗲𝗲𝗹𝗮𝗻𝗰𝗲 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝘄𝗿𝗶𝘁𝗲𝗿𝘀 to help me scale our content in the meantime.

who i'm looking for:
- you know dev tools;
- you've either shipped code, or you've written about it convincingly enough;
- you care for technical accuracy (if you make stuff up our readers will clock you);
- you are a human who writes like a human

All the details, including how to apply, can be found here

if this sounds like you (or someone you know), drop me a line :)

Also this goes without saying but I’m currently looking for flesh-based, real humans to work directly with; if you run an AI-content-creation-solution-workflow-thing or run an agency please do not DM me at this time, I will not reply ♥️

---

Freelance Technical Writer

Contract • Remote • Variable volume (~2–4 articles/month)

About PostHog

We're shipping every product that companies need to run their business – product analytics, session replay, feature flags, experiments, error tracking, logs, a data warehouse, LLM analytics, and a bunch more. We started open source out of Y Combinator's W20 cohort, more than 100,000 companies have installed PostHog, and we're default alive, growing mostly through word of mouth.

Our blog is one of the main ways people find us. The editorial team writes most of it, but we want a small bench of freelancers to help us go deeper on technical topics and cover more ground.

What this role is

We're hiring a freelance technical writer to contribute SEO and AEO-focused content to the PostHog blog. Think: comparison articles, alternatives listicles, product tutorials, "how to do X with [PostHog product]" guides, deep-dives on product-related topics, and more.

Volume varies – assume 2–4 articles per month on average, sometimes more, sometimes less. You'll work directly with PostHog editors. Briefs include the angle, the target keyword, structural guidance, and links to internal docs and source material. You write, we edit, we publish.

To be clear: this is a freelance contract, not employment nor a retainer. 

There's no guaranteed volume or minimum commitment from us – we send briefs when we have them, and you take the ones that work for you. Some months will be busier than others.

Who we're looking for

You're our dream candidate if you:

• Have an engineering or coding background. You've shipped code, debugged something in production at 2am, set up observability tooling, or built a side project that involved more than a Webflow site. You can read our docs, install PostHog, and actually use it before writing about it.
• OR you can speak with authority on technical topics without being an engineer. Maybe you've spent years writing about developer tools (Stripe, Vercel, Supabase, Resend, Linear – if you've contributed to blogs in that orbit, we want to see it). Either way, you don't need hand-holding on the basics and you can write something a CTO will actually finish reading.
• Care about accuracy. Our readers are technical. They will notice if you describe feature flags wrong, mix up server-side and client-side SDKs, or hallucinate an integration that doesn't exist. We expect you to fact check rigorously and cite primary sources (docs, GitHub, official announcements, etc).
• Write like a human. We do not want slop.
• Can hit a deadline. Variable volume means we need people who say yes when they can deliver and no when they can't. Ghosting after accepting a brief is the fastest way to not work with us again.

Nice to have

• SEO knowledge. You know what search intent is, you understand how to structure an article for both Google and LLMs (AEO), and you have a general understanding of SEO best practices.
• Familiarity with PostHog or competing tools (Amplitude, Mixpanel, Sentry, Datadog, LaunchDarkly, Heap, Hotjar, etc.). Bonus points if you've written about any of them.
• Comfortable with markdown, Git, and pull requests. A lot of dev-tool companies (us included) treat the blog like a codebase. If submitting a PR to a content repo doesn't faze you, that's a plus.

How to apply

Send us:

1. A short (!)  intro. A couple of sentences on who you are and why you want to write for us.
2. Your portfolio. Links to at least 3–5 published technical pieces you're proud of. Bylined work is best, but we'll consider ghostwritten samples if you can confirm you wrote them.
3. Your rate and payment terms.
4. A short writing sample. Pick ONE of the prompts below and answer in 1–2 short paragraphs. Don't go long – we're looking at how clearly and concisely you can explain a technical idea, not how much you can pad.

a. What's the difference between logs, APM, and error tracking? When would an engineering team reach for each, and where do they overlap? 

B. What separates a good LLM Observability  tool from a bad one? If you were evaluating Langfuse, Langsmith, Braintrust, and PostHog side by side, what features would you actually weigh and why?

c. What can an MCP server unlock for a product like PostHog that a traditional API or dashboard can't? Give a concrete example of a workflow that gets meaningfully better when you can talk to the product through an AI agent instead of clicking through a UI.

Helpful starting points: posthog.com/docs. Feel free to install PostHog and poke around – that's encouraged.

One important note: we will know if your answers are AI-generated, so tread carefully.