About PostHog
Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.
PostHog is 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. We've since shipped more than a dozen products, including:
-
PostHog Code, the only AI devtool that understands your product, not just your codebase.
-
A built-in data warehouse, so users can query product and customer data together using custom SQL insights.
-
PostHog AI, an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.
We are:
-
Product-led. More than 450,000 organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.
-
Default alive. 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.
-
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.
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. Engineers lead product teams and make product decisions. Teams are flexible and easy to change when needed.
-
Shipping fast: 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 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, 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 with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.
Job Summary
We're looking for someone who will help activate PostHog's online watering holes. The Developer who connects with other developers tends to people, not pipelines. The job is to make PostHog users (and their products) successful outside our product, get them having real conversations with each other on the internet, and carry PostHog's values into every online surface — the forum, the Discord, the subreddit, livestreams, AMAs, the DMs you'd never see. What starts with broad engagement is meant to lead to identifying and empowering superfans.
You'll have two bets and go deep to start. With plenty more challenges ahead:
What you’ll be doing
Bet 1: Grow online conversations between users. PostHog has a forum, a Discord, a subreddit, a newsletter, and a lot of content — but conversations between users are sparser than they should be. Forum traffic has declined year-over-year. Reddit engagement is low. You'll own growing the volume and quality of conversations across all three surfaces:
-
Forum — slow, indexed depth. Concrete opening project: clean up out-of-date questions, clarify what the forum is for, start actively triaging and seeding. The decline isn't because users don't want to talk; it's because no one is doing the maintenance and hosting work.
-
Discord — raw, real-time, not indexed. Currently in test mode; you take it over fully and aim for the 20% DAU default-alive benchmark. We haven't proven Discord will compound for us long-term, but the size of comparable companies' servers says it should. If it doesn't, you're the person who calls it.
-
Reddit — public, discoverable. Narrow scope: recruit passionate community members to help run the subreddit, and personally lead high-leverage moments like AMAs. Not daily triage.
You'll also seed conversations on hub topics like growth engineering, design for product engineers, and fundraising for founders, and figure out the strategic question hiding underneath: when does each surface get used, for what?
Bet 2: Spotlight users and build a superfans operating system. We have founders who are fans, OSS contributors, event organizers, forum power users, builder group leaders, and customers doing interesting work. Right now nobody keeps a list, the relationships are personality-dependent, and we mention great customers once in a case study and then never again. You'll build the system — identify, spotlight, enable, reward.
One specific track within this: a consistent flow of people engaging in the forum, open source contributions, users sharing what they're building in chat and livestreams. Make it easy to start in all these online spaces, recognize existing contributors meaningfully, and develop a reward system that goes beyond a merged PR. You'll also deal with potential negative incidents or breaking of guidelines that may invariably happen.
You'll also work closely with the IRL events team on the bridge between offline and online (builder groups becoming online regulars, online conversations seeding meetups), organizing online "events," and pick up sidequests such as a new community surface all together (would building our own social network be the best way to achieve these goals?)
What you won't be doing
❌ Turning these channels into customer support — what we're expressly trying to avoid ❌ Managing Twitter/LinkedIn/Youtube social — our social poster owns these ❌ Running "community" as a top-of-funnel signup engine — if signups happen, fine, but they're not the goal ❌ Being the loudest voice in every channel — the key here is identifying voices, not raising your own ❌ Day-to-day Reddit triage or moderation — you enable community members to do that
Requirements
-
Track record of building or stewarding an online community where high-quality conversations happened — forum, Discord, Slack, subreddit, doesn't matter which, results matter
-
Already an active PostHog user. Not "willing to learn it" — you're using PostHog in your own work today, you know the product surface area well enough to have a credible technical conversation with any user
-
Has been an active participant in developer communities (not just managed them from the outside)
-
Strong public writing/speaking — you'll be modeling the conversational standard you want users to meet
-
Embody PostHog's values in your day-to-day experiences
Nice to have:
-
OSS maintainer experience
-
Has run a developer-focused program before (champions, ambassadors, fellows, hackathons)
-
Has built an audience of their own (newsletter, podcast, YouTube, Twitter/X — any of it)
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
