Developer who connects with other developers

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)…