Technical Content Writer
Editorial Team
Location
Remote
Timezone(s)
GMT + 2:00 to GMT -8:00
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 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 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
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. Use 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:
What you won’t be doing
❌ Churning out generic SEO content to hit a publishing quota.
❌ Spending most of your time writing social posts, newsletters, 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.
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. 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!
Generous, transparent compensation & equity
Unlimited vacation (with a minimum!)
Two meeting-free days per week
Home office
Coworking credit
Private health, dental, and vision insurance.
Training budget
Access to our Hedge House
Carbon offsetting
Pension & 401k contributions
We hire and pay locally
Company offsites
Get more details about all our benefits on the Careers page.
Publish so much, so good. We ship a lot as a company, we should also publish a lot as a team. This means getting more people up to speed and involved, including those not on our team. It means reusing the work we've already done to go further (like socials). Add content automations, tighter processes, more repeatable formats, and new channels so we can be in more places, all the time.
Tie it better to PostHog. First, we're often the first way someone hears about PostHog. We should be sharing what's important to the company. If PostHog focuses more on AI and data stack, so should we. Second, we should tie to other efforts related teams are working on (sales, paid ads, talent). Third, we should tie to data in PostHog to help us figure out the success of what we've done and what to work on next.
Business as usual
- A high-quality newsletter every two weeks -
Ian VanagasIan Vanagas - Social posts every day and amplifying employee accounts -
Liam GrahamLiam Graham
Social handbook
Owner: Liam GrahamLiam Graham
Motivation: Honeymoon period is almost over. I've gotta calcify a few ideas and best practices, and make sure they're understood across the entire org.
What we'll ship: A handbook section about how we do social at PostHog. Answers how social posting fits into our broader goals, and what type of posts do well. Is prescriptive for the brand itself.
We'll know we're successful when: Everyone across PostHog understands our disposition as it regards social media, I can say “no” to a social idea by replying with :rtf-handbook:. Product marketers can write the first draft of social posts themselves.
Test Instagram carousels
Owner: Liam GrahamLiam Graham
Motivation: We want to expand the type of content we post to unlock Instagram as a channel for social posts. Carousels are the way to do this.
What we'll ship:
- A graphics-approved template for Instagram carousels.
- The actual implementation of carousels to promote newsletters and blogs.
We'll know we're successful when: We're posting an average of one carousel a week to Instagram.
Expand AEO footprint (v2, the remix)
Owner: 
Natalia AmorimNatalia Amorim
Motivation: We've built a solid foundation - now it's time to go deeper and experiment with new content formats. The goal is to show up consistently when developers and founders are asking LLMs about the spaces PostHog competes in.
What we'll ship:
- Continued optimization plus net-new AEO/SEO content to grow upper-funnel traffic (both internal and from freelancers)
- SEO positioning that backs the "Self-driving" push – updating website pages and making sure AEO/SEO content carries the message consistently
- Track self-driving (and related) prompts in Gauge
We'll know we're successful when: LLM traffic not only stays up and to the right, but picks up momentum
Mini newsletters & blogs to explain trending dev topics
Owner: 
Jina YoonJina Yoon
Motivation: Ian's loops article did really well on Twitter and we're getting feedback that it's valuable to have simple explainers for overly-hyped and over-complicated topics.
What we'll ship: A mini-newsletter or blog every two weeks explaining a trending topic, buzzword, or concept in simple terms. Aim for 2-minute reads with newsletter-level quality, written with the X and YC audience in mind. Example topics: agents, skills, orchestration.
We'll know we're successful when: They perform well on Twitter and people are referencing them as a great explainer on that topic. SEO/AEO will likely benefit but that's not a primary goal.
A theory of self-driving
Owner: Ian VanagasIan Vanagas
Motivation: Self-driving product is the most important concept for the next era of PostHog, but few people know about it and it's still unclear what the implications of self-driving products is.
What we'll ship:
- 4 newsletters on an aspect of self driving product
- For example: setting good goals, doing better code reviews, getting the right context (using warehouse)
We'll know we're successful when: We are known for "self-driving product," are more confident about what it means, and are having the term repeated back to us.
A minimum viable brand study
Owner: Natalia AmorimNatalia Amorim
Motivation: We have wanted to do a brand study for a long time, but it's always seemed like too much work. We think it's important because we have lots of interesting first-party data, this is really valuable in AEO, and it gives us a potential new format to use.
What we'll ship: A data-heavy newsletter leveraging our first-party data that acts as a sort of minimum viable brand study. It should include some pretty graphs.
We'll know we're successful when: We ship the newsletter, share the graphs on social, and have a good idea what it takes to produce one of these.
James social
Owner: 
Andy VandervellAndy Vandervell
Motivation: Make PostHog famous for self-driving through James
What we'll ship: Two posts a week from James sharing how we think about self-driving, our strategy and ideas generally.
We'll know we're successful when: Posts consistently perform well and we see cut-through — i.e. people talking about PostHog off the back of them.