Developer who loves teaching

Content Team

  • Location

    Remote (US | EU, London, UK, EMEA)

  • Timezone(s)

    GMT +2:00 to GMT -8:00

About PostHog

We're shipping every product that companies need to run their business from their first day, to the day they IPO, and beyond. The operating system for folks who build software.

We started with open-source product analytics, launched out of Y Combinator's W20 cohort. We've since shipped more than a dozen products, including:

  • A built-in data warehouse, so users can query product and customer data together using custom SQL insights.

  • A customer data platform, so they can send their data wherever they need with ease.

  • Max AI, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.

Next on the roadmap are CRM, messaging, revenue analytics, and support products. When we say every product that companies need to run their business, we really mean it!

We are:

  1. Product-led. More than 100,000 companies have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.

  2. Default alive. Revenue is growing 10% MoM on average, 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 $100m 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.

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

  • Time for deep work: 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, and we prioritize heads down work 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 with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.

Who we’re looking for

This role is about helping PostHog users through content, particularly by writing great docs and guide content.

It could suit a developer turned technical writer, a dev advocate who loves writing, or a software developer who's looking to change track.

Specifically, we're looking for people who:

  • Have real development chops. We don't expect you to be a 10x dev or anything, but experience in software development, either in full-time roles or through side projects, is essential. Our audience are devs, so you need to be too.

  • Figure out problems independently. There's rarely a blueprint to follow, or a list of jobs to be done here. 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.

  • Enjoy the craft of writing. You'll be doing a lot of writing, so you should enjoy it. You don't have to be obsessed with en dash usage, but you should geek out about making your writing effortless to read and understand.

  • 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.

  • Bias to action. 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.

What you’ll be doing

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 will be:

  • Maintaining our docs and writing tutorials that solve user pain points

  • Gathering context on pain points from engineers and customer-facing teams

  • Shipping improvements based on user feedback and analytics

  • Writing code and creating reference examples (e.g. code samples, demo apps, etc)

  • Building components and dev tools that improve our documentation stack

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

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

  • Improving the information architecture of our docs to ensure content is discoverable and scalable

What you won’t be doing

❌ Running webinars. Eugh, just no.

❌ Writing newsletters and brand content

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

Requirements

  • Experience writing docs and educational content for developers

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

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


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! Alignment with our values is just as important as experience! 🙏


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!

Meet the Content Team

Teaching and entertaining our audience through great docs, tutorials, newsletters, and video.

Team members

Does pineapple belong on pizza?

63% say YES!

We have a set system for compensation as part of being transparent. Salary varies based on location and level of experience.

Learn more about compensation

Location

(based on market rates)

Level

Step

Salary calculator

  1. Benchmark (United States - San Francisco, California) $190,910
  2. Level modifier 1
  3. Step modifier 0.95 - 1.04
Salary $181,365 - $198,546plus equity

  • Generous, transparent compensation & equityGenerous, transparent compensation & equity
  • Unlimited vacation (with a minimum!)Unlimited vacation (with a minimum!)
  • Two meeting-free days per weekTwo meeting-free days per week
  • Home officeHome office
  • Coworking creditCoworking credit
  • Private health, dental, and vision insurance.Private health, dental, and vision insurance.
  • Training budgetTraining budget
  • Access to our Hedge HouseAccess to our Hedge House
  • Carbon offsettingCarbon offsetting
  • Pension & 401k contributionsPension & 401k contributions
  • We hire and pay locallyWe hire and pay locally
  • Company offsitesCompany offsites

Get more details about all our benefits on the Careers page.

Make PostHog a hub for product engineers to learn and collaborate

Editorial

Awesome content and docs for data warehouse

Owner: Ian Vanagas (support from Vincent Ge and Edwin Lim)

Motivation: Data warehouse is a high-leverage product for our customer infrastructure strategy, but it lacks both high-quality docs and strong content marketing content to drive adoption.

What we'll ship:

  • Updated and fully fleshed out docs, working along similar lines to reference docs Edwin and Vincent are creating for error tracking.
  • Alternatives, comparison and top-of-funnel content promoting our data warehouse.
  • Opinionated blog and newsletter content (e.g. how we use data warehouse)

We'll know we're successful when

  • Top-of-funnel content is getting traction and creating interest
  • Interest in the product converts to real usage from new and existing users
  • Growth in pageviews to data warehouse docs and tutorials
  • Increased visibility of PostHog as a data warehouse option from LLMs
Maturing the newsletter growth engine

Owner: Lior Neu-ner

Motivation: We want to reduce reliance on Substack recommendations, improve quality of paid signups, and create a scalable growth engine that's (largely) set and forget.

What we'll ship:

  • Newsletter ads for LinkedIn, Meta, and Reddit.
  • Newsletter ads and placements using new methods of tracking to validate.

We'll know we're successful when

  • Open rates above 40%
  • We know what works and this becomes easy to maintain
Long-term vision for newsletters

Owner: Ian Vanagas, Lior Neu-ner, and Andy Vandervell

Motivation: We want to maintain our existing newsletter schedule and quality standards while developing a stronger opinion on the future of newsletters at PostHog, audiences we want to reach, and what we're going to do to reach them in the short, medium and long-term.

What we'll ship:

  • An awesome newsletter every two weeks
  • Newsletter offsite to workshop new ideas and long-term plans
  • Updated handbook pages on newsletter process + plans
  • Hiring plan for what's needed to execute our newsletter vision

We'll know we're successful when

  • We're excited about our long-term plans for the newsletter
  • We ship a great newsletter every two weeks
  • We continue to see good engagement and feedback on newsletters
  • No decline in important metrics (shares, organic subs, open rate etc.)
  • We successfully onboard a new newsletter writer in Q3 with clear goals to work on
Shipping product engineer handbook

Owner: Andy Vandervell

Motivation: We want to completely own the concept of the Product Engineer by creating its central text. We're 80% of the way there. Need to ship final 20%.

What we'll ship

  • The introductory chapters of the handbook using a similar structure to the company handbook. This will give us the platform to then develop more sections on specific topics, or potentially integrate getting started content into the handbook.

We'll know we're successful when

  • We've shipped the first version of the guide
  • Positive initial reaction from our users and readers
  • Ranking for product engineer keywords in search
  • Incoming users convert to reading other parts of guide
  • Converting handbook readers to subscribers of the newsletter

Docs

Reference product docs for error tracking

Owner: Vincent Ge and Edwin Lim (support from Ian Vanagas)

Motivation: We want to show what 10x docs should look like by setting an example with a single product. These conventions will become examples and templates for 10x-ing other docs and a model for future technical writers to follow.

What we'll ship:

  • End-to-end product docs which include overview, concept explainers, references, use-case guides, tutorials, best practices, troubleshooting, code examples.
  • Stretch goal: Example app for error tracking

We'll know we're successful when:

  • Other small teams want their docs to look like the error tracking docs :)
  • Praise from users how awesome error tracking docs are
Generated SDK reference docs for popular SDKs

Owner: Vincent Ge

Motivation: No one should guess or look at source code to know how SDK methods work. We need to auto-generate references from source code that are accurate and always up to date.

What we'll ship

  • Reference generation code for:
    • posthog-js
    • posthog-react-native
    • posthog-node
    • posthog (python)
    • We can ship more or less depending on schedule/ask
    • We want push for highly accurate coverage and accuracy for these
  • posthog.com page that reads references and displays reference docs for:
    • Exposed methods
    • Parameter input and return type output
    • Type definitions

We'll know we're successful when

  • We gravitate toward checking SDK references as a source of truth for SDK signatures.
  • No more huge, hand-written SDK docs pages
  • 0 undocumented methods and type definitions for listed SDKs
10x-ing docs contributors

Owner: Edwin Lim

Motivation: At PostHog, everybody writes documentation. So let's equip everyone with the templates, tools, and criteria to 10x their output alongside ours.

What we'll ship

  • An updated docs handbook with templates, tools, and style guide criteria for writing PostHog documentation
  • A set of LLM prompts to help quickly generate templates

We'll know we're successful when

  • Teams actively use the templates and tools to write new docs
  • Positive feedback from teams that resources make it easier for them to ship docs

Video

Ship big and awesome video projects

Owner: Alex van Leeuwen

Motivation: We have a series of ongoing video projects that are high-value and big lifts

What we'll ship

  • DeskHog launch video
  • Customer infrastructure vision / explainer ;)
  • Hackathon documentary with accompanying blog post

We'll know we're successful when

  • They are shipped on time (within reason)
  • Positive feedback from PostHog fans
HogTok

Owner: Edwin Lim (with support from video)

Motivation: Video (HogTok) as a website delivery system for feature discovery, tutorials, and technical content, and our flagship big video projects.

What we'll ship

  • Two HogTok's per week consistently
  • Social media player that supports videos and images in the app and website
  • Social posts on brand and James' account using HogToks

We'll know we're successful when

  • Users watch the content
  • People mention how cool HogTok is
  • Support and sales teams find it useful enough to share with users
  • We can see conversion to usage / adoption of features

Meta

We hire all the awesome people

Owner: Andy Vandervell

Motivation: We need to grow our team to increase our capacity for core work and grow our owned audiences

What we'll ship:

  • Hire all Q3 roles in the marketing hiring place:
    • 1x post-production specialist
    • 1x content marketer
    • 1x developer who writes guides
    • 1x Developer who writes newsletters
  • Proposals for new roles as needed, including:
    • Developer who is terminally online (social media)

We'll know we're successful when

  • We've hired everyone want during Q3
  • New starters onboarded and making an instant positive impact
Better systems and insights for content marketing

Owner: Andy Vandervell

Motivation: We want a better grasp of data and growth patterns for our work, and we (mostly Andy, tbh) thinks more robust systems will help us coordinate content and marketing efforts better as we scale.

What we'll ship

  • Insight of the week during sprint meetings
  • Kick-ass new dashboards for how content and docs are performing
  • Monthly growth review for team content (inc. newsletter, content & docs)
  • Marketing / content calendar anyone can access and understand

We'll know we're successful when

  • We're regularly making better decisions about what to prioritize based on data
  • We have a strong grasp of the data points we care about (and which ones we don't)
  • Anyone can see what's happening and when at a glance

Other

Sidequests
  • Plan for dealing with stalke tutorials and content – Lior
  • Testing viral animated video shorts – Lior
  • Automating summaries of the docs feedback each week with LLMs to make it actionable – Vincent
  • Adding Greptile or similar to website repo to spot common errors and problems – Ian
Things we want to do with new hires
  • Much better docs + content marketing for CDP, surveys, and LLM observability
  • Doubling down on SEO content (i.e. alternatives, comparisons, etc. for all products)
  • Consistent video schedule for things like changelog, new features etc. outside of big projects
Anti-goals
  • Nailing YouTube. This is long-term ambition, but we're not ready to tackle this yet.
  • Weekly newsletter. We've been down this road several times. Requires more resources.
  • Redesigning docs website. We have thoughts here, but we can't ship this alone and there are more hair on fire problems for us to solve.
  • Great docs homepage experience. We think this could be critical to communicating the customer infrastructure experience, but we have more fundamental problems to solve right now, and it isn't something we can ship alone. This is something we'll revisit as a potential Q4 goal / project.
  • In-depth docs for Max AI. Some improvement here would be nice and useful, but the product is moving too fast for us to usefully contribute and we think users will gain more from playing with Max AI than reading docs. We do, however, want to use HogToks to encourage and inspire users to try using Max and explore things you can do using AI in PostHog.
  • Owning unanswered questions on Docs. We don't have the capacity to do this and it would distract us from core goals. Will discuss better logic on docs pages for stale questions, or potentially out of date questions, with website folks.

We do 2-3 short interviews, then pay you to do some real-life (or close to real-life) work.

  • 1
    Application (You are here)
    Our talent team will review your application

    We're looking to see how your skills and experience align with our needs.

  • 2
    Culture interview
    30-min video call

    Our goal is to explore your motivations to join our team, learn why you’d be a great fit, and answer questions about us.

  • 3
    Technical interview
    45 minutes, varies by role

    You'll meet the hiring team who will evaluate skills needed to be successful in your role. No live coding.

  • 4
    Founder interview
    30 minutes

    You have reached the final boss. It's time to chat with James or Tim.

  • 5
    PostHog SuperDay
    Paid day of work

    You’ll meet a few more members of the team and work on an independent project. It's challenging, but most people say it's fun, and we'll pay you $1,000 for your efforts!

  • 6
    Offer
    Pop the champagne (after you sign)

    If everyone is happy, we’ll make you an offer to join us - YAY!

(Now for the fun part...)

Just fill out this painless form and we'll get back to you within a few days. Thanks in advance!

Seriously, just write a couple of sentences about why you love us and you'll be doing better than 90% of applications.

Questions about this page? or post a community question.