Developer who loves teaching

We help developers build successful products by giving them a suite of products to analyze, test, observe, and deploy new features. We currently offer product and web analytics, session replay, feature flags, A/B testing, a CDP, SQL access, and a data warehouse… and there’s plenty more to come.

PostHog was created as an open-source project during Y Combinator's W20 cohort. We had the most successful B2B software launch on HackerNews since 2012 with a product that was just 4 weeks old. Since then, more than 70,000 companies have installed the platform. We've had huge success with our paid upgrades, raised lots of money from some of the world's top investors, and have shown strong product-led growth – 97% driven by word of mouth. 

We're growing quickly, but sustainably. We're also default alive, averaging 10% monthly revenue growth and with more than $10m ARR. We're staying focused on building an awesome product for end users, hiring a handful of exceptional team members, and seeing fantastic growth as a result.

What we value

• We are open source - building a huge community around a free-for-life product is key to PostHog's strategy.

• We aim to become the most transparent company, ever. In order to enable teams to make great decisions, we share as much information as we can. In our public handbook everyone can read about our roadmap, how we pay (or even let go of) people, what our strategy is, and who we have raised money from.

• Working autonomously and maximizing impact - we don’t tell anyone what to do. Everyone chooses what to work on next based on what is going to have the biggest impact on our customers.

• Solve big problems - we haven't built our defining feature yet. We are all about shipping fast, talking to users, and iterating.

While this role involves working on our docs, it isn't a narrowly-defined technical writer role. We're looking for someone who can:

• Bridge the gap between the power of PostHog and the knowledge users need to harness that power to it fullest. This means being as comfortable writing about conceptual frameworks, and best practices, as you are explaining how to configure posthog-js correctly.

• Speak to our audience of product engineers and technical founders. This means experience in software development, either in full-time roles or in side projects, is essential.

• Figure out problems independently. There is no blueprint to follow, or list of jobs to be done. We work together to find the best answers and solutions, but we expect everyone to bring a point of view and ideas they can execute. You need taste and love for the craft of writing, too.

• Anticipate where less technical users need additional support. While developers and technical founders are our ICP, PostHog is still a powerful tool for non-technical users, like product managers and marketers. It's important our content supports their use cases and helps them achieve their goals.

As a product-led company, our content, docs, and marketing often lags the product. You need to be comfortable being a little reactive. Having a plan is great, but biasing to action and iterating quickly is even better.

We're building a broad product, so there's a huge surface area of problems we help solve, and content needed to support our users in doing so.

This includes keeping our technical documentation up-to-date, but also higher-level guides covering common concepts and problems, like feature flag best practices and what analytics events you should track.

This means you'll be:

• Figuring out our users’ pain points by talking to them directly

• Gathering context from product and customer success teams

• Writing code (e.g. code samples, test apps) and sharing development best practices

• Producing written content that educates users and help them succeed

• Seeking out the most critical paths where great content have an outsized impact

• Improving our existing documentation, so our users have a great experience

• Ensuring AI agents have the context they need to provide accurate answers

What you won’t be doing

❌ Webinars. We’re interested in supporting video content, but webinars aren’t our vibe

❌ Writing newsletters and brand content. Never say never, but this isn’t a primary focus for this role

❌ Attending and speaking at events. This is primarily a content role

❌ Waiting to be told what to do. No one will present you with a list of docs to update

• Experience writing docs and learning content for developers, preferably at a dev tool company

• Software development experience, though not necessarily in a formal role

• An opinionated take on what makes great docs and educational content

Nice to haves

• Experience working with customer success teams to understand customer problems

• Comfortable producing your own video tutorials and support material

We believe people from diverse backgrounds, with different identities and experiences, make our product and our company better. That’s why we dedicated a page in our handbook to diversity and inclusion. No matter your background, we'd love to hear from you!

Also, 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.