Technical Staff Writer (Blogs & Newsletters)

Job description

## About PostHog Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools. PostHog makes products [self-driving](https://posthog.com/self-driving). It's the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously. We started with open-source product analytics, [launched out of Y Combinator's W20 cohort](https://posthog.com/handbook/story). We've since shipped [more than a dozen products](https://posthog.com/products), including: - [PostHog Desktop](https://posthog.com/desktop), the only AI devtool that understands your product, not just your codebase. - [A built-in data warehouse](https://posthog.com/docs/data-warehouse), so users can query product and customer data together using custom SQL insights. - [PostHog AI](https://posthog.com/ai), an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries. We are: 1. **Product-led**. More than 450,000 organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit. 2. [**Default alive**](https://paulgraham.com/aord.html). Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on. 3. **Well-funded.** We've raised more than $180m from some of the world's top investors. We're set up for a long, ambitious journey. We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and [being as weird as possible](https://posthog.com/deskhog). ## Things we care about - **Transparency:** Everyone can read about our roadmap, how we pay (or even let go of) people, our strategy, and how we work, in our [public company handbook](https://posthog.com/handbook). Internally, we share revenue, notes and slides from board meetings, and fundraising plans, so everyone has the context they need to make good decisions. - **Autonomy:** We don’t tell anyone what to do. Everyone chooses what to work on next based on what's going to have the biggest impact on our customers, and what they find interesting and motivating to work on. [Engineers lead product teams](https://posthog.com/handbook/wide-company) and [make product decisions](https://posthog.com/handbook/which-products). Teams are flexible and easy to change when needed. - **Shipping fast:** [Why not now?](https://posthog.com/handbook/values#why-not-now) We want to build a lot of products; we can't do that shipping at a normal pace. We've built the company around small teams – autonomous, highly-efficient groups of [cracked engineers](https://posthog.com/founders/cracked-manifesto) who can outship much larger companies because they own their products end-to-end. - **Time for building:** Nothing gets shipped in a meeting. We're a natively remote company. We default to async communication – PRs > Issues > Slack. Tuesdays and Thursdays are [meeting-free days](https://posthog.com/handbook/company/culture#were-on-the-makers-schedule), and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had. - **Ambition:** We want to solve big problems. We strongly believe that aiming for the best possible upside, and sometimes missing, is better than never trying. We're optimistic about what's possible and our ability to get there. - **Being weird:** Weird means redesigning an already world-class website for the 5th time. It means shipping *literally* every product that relates to customer data. It means building an [objectively unnecessary developer toy](https://posthog.com/deskhog) with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun. ## **Who we’re looking for and why now?** A great writer who gets technical stuff – and loves figuring out how to explain it to other people. We have a strong writing culture, and writing as marketing has worked ridiculously well for us. We have a [newsletter](https://posthog.com/newsletter) with over 100k subscribers, active social accounts, and real SEO and AEO authority. Hundreds of thousands of people visit our website every day. If you join, you won't spend a year building an audience before anyone reads you. [We can and like to be opinionated](https://newsletter.posthog.com/p/collaboration-sucks) about what we think best practice is and thousands of developers look to us to provide them opinion. The problem is we're at capacity, and there's a long list of content we're neglecting because of it. We used to do more tutorials. Use case guides people keep asking us for. Overall, we have a lot to write about. PostHog has grown from product analytics into a broad platform for engineers, and we're building everything from AI agents and error tracking to data infrastructure at huge scale. We're also open by default, so we're unusually happy to share what we've learned along the way. We want someone who can turn all of that into genuinely useful technical content. Simply put, **you're a writer**. You care about the craft, have opinions about what makes technical content actually great, and have a portfolio that proves it. ## **What you’ll be doing** Disclaimer: we keep getting applications from excellent technical documentation writers who have no technical blog posts portfolio. This isn't that job though. The work here is **blog posts**. You'll research and explain use cases, technical concepts, and how things actually work. One day that might mean digging into how our engineers rebuilt part of our data warehouse. Another could be explaining the difference between logs and traces, writing a tutorial for a PostHog use case, or figuring out the best way to explain what a context warehouse is. You'll need to be comfortable getting into technical details, but you don't need to be an engineer. The important bit is that you're curious enough to understand technical concepts properly and a good enough writer to explain them simply. Day to day, it looks like: - **Writing content that helps people and agents use PostHog better.** Blog posts in the form of uUse case guides, tutorials, technical explainers, engineering posts. The stuff we know is valuable and haven't had the capacity to do as much as we want to. - **Researching and explaining hard things.** Technical details, engineering processes, and concepts that most people gloss over. Going deep enough that a builder actually learns something. - **Figuring out what to write.** Looking at what we are shipping as a company, what our priorities are, and what's interesting to decide yourself. There isn't going to be someone telling you what to write all the time. - **Choosing the right format for the idea.** Sometimes that's an engineering blog. Sometimes it's an SEO explainer. Sometimes it's a thread on X. - **Working with engineers and other marketers.** Getting the story of what they built, why it matters, and what's interesting about it for normal builders. You might edit their blog posts too. Some examples of the sort of things you might work on: - [10,000 PRs a month is easy: How devex is evolving at PostHog](https://posthog.com/blog/10k-prs-a-month) - [What is a context warehouse?](https://posthog.com/blog/what-is-a-context-warehouse) - [Why we rebuilt our data warehouse on DuckDB over ClickHouse](https://posthog.com/blog/why-we-rebuilt-our-data-warehouse) - [What is a Scout? A technical deep dive](https://posthog.com/blog/what-is-a-scout) - [What is distributed tracing? (A guide for engineers)](https://posthog.com/product-engineers/what-is-distributed-tracing) - [Validating what you ship: Did anyone use it? Did it work?](https://posthog.com/tutorials/validating-what-you-ship) - [How to set up embedded analytics](https://posthog.com/tutorials/embedded-analytics) **Go and read at least two or three of those before you apply.** If that's not the kind of thing you want to spend your week writing, this isn't the job, and we'd both rather find that out now. ## **What you won’t be doing** ❌ Writing [docs.](https://posthog.com/docs) This is not a traditional Technical Writer, or Documentation Engineer, or UX Writer role. [Wizard & Docs](https://posthog.com/teams/wizard-and-docs) team owns that, and they’re excellent at it. ❌ Churning out generic SEO content to hit a publishing quota. ❌ Spending most of your time writing social posts, ads, video scripts, or marketing copy. ❌ Waiting for someone to tell you exactly what to write every week. ❌ Publishing AI slop nobody on the team would actually want to read. ❌ Running the newsletter as your main job. The newsletter goes out to 100k+ people and you'll write for it, but it's downstream of the posts. If your dream job is editing a newsletter, this isn't it. ## **You’ll fit right in if:** - **You're a strong writer.** This is the most important requirement. You can take something complicated and make it clear, useful, and enjoyable to read. You’re dedicated to the craft of writing. Every post here gets reviewed and we only publish things we're proud of. You need to share the same sentiment. - **You've written technical content before.** Your portfolio includes technical explainers, engineering posts, tutorials, or similar work for a developer audience – similar to the ones we want to write (check the samples above!). Ideally, you've written these across styles, concepts, and mediums (SEO blogs, X threads). - **You're technically curious and capable.** You don't need to be an engineer, but concepts like logs and traces, data warehouses, APIs, LLMs, and agents shouldn't scare you. You should be able to learn how something works and explain it accurately. - **You have good taste.** You know the difference between content that genuinely teaches someone something and content that exists because somebody wanted to rank for a keyword. - **You’re AI-pilled.** You use AI in your own work to build cool things, improve your workflows, and help you write great content. - **You work independently.** There's rarely a queue of perfectly scoped assignments at PostHog. You'll need to decide what's worth writing, develop a point of view, and get it shipped. ## **Nice to haves** - **You've done this at a similar company.** Developer tools, B2B SaaS, or anywhere with a technical audience. If you've written high-quality technical explainers for a company like ours before, you're exactly who we're looking for. - **You ship things.** Side projects, small tools, anything that means you've been on the other side of the docs you're writing. - **You already use PostHog.** Not necessary, but useful. We use it for everything. *If you have a disability, please let us know if there's any way we can make the interview process better for you – we're happy to accommodate!* *#LI-DNI*