PostHog

Software Engineer

• Running GTM for our Agents and AI Gateway products. These are brand new teams, building our newest and bravest products.
• Owning launches from zero to done. You'll shape the story for these teams. That means crafting GTM plans, writing announcements, managing positioning, and supporting adoption long after launch day.
• Being the voice of PostHog for engineers. You'll work closely with product engineers to make sure our products land well. The more comfortable you are decoding jargon and communicating with developers, the better.
• Shipping. A lot. This is not a job where you write a strategy deck and wait. You’ll be shipping work every week — and learning fast from it.

Developer Marketer – Agents

DevOps Engineer

• You won’t be in a typical “keep the lights on” SRE role. The work is about turning a fast-growing, stateful system into a predictable, well-automated platform. (provisioning, scaling, rebalancing, recovery) That means reducing operational stress, designing safe automation for traffic-heavy workloads, and building the tooling and patterns that let the system scale without scaling human effort.
• You'll work on the kind of problems that only show up at large scale (petabytes of data, thousands of cores, constant ingestion) across a multi-region, multi-account AWS platform running many services on Kubernetes.
• Operating EKS clusters across several environments with Karpenter autoscaling, Cilium networking, and ArgoCD-driven GitOps deployments
• Managing and evolving a multi AWS account organization, provisioning, networking, access control, and cross-account connectivity
• Maintaining the Terraform/Terragrunt IaC platform - modules, automated plan-on-PR / apply-on-merge pipelines, and safe patterns for shared infrastructure
• Improving operational tooling around deploys, schema changes, backups, restores, and incident response
• Reducing operational load by identifying repeat pain points and eliminating them through code and self-healing automation
• Optimizing cloud spend as you go
• Participating in on-call and incident response, with a strong focus on making incidents rarer over time.
• You'll have room to design and automate, not just respond to alerts. You should join this team if you like deep ownership of production systems and enjoy building the platform layer that everything else runs on.

Site Reliability Engineer, US - Central/Eastern Timezone

• Managing large fleets of EC2-based VMs, disks, and networking for data-intensive workloads
• Improving operational tooling around deploys, schema changes, backups, restores, and incident response
• Working closely with ClickHouse engineers to turn database-level needs into infra-level solutions
• Reducing operational load by identifying repeat pain points and eliminating them through code and self-healing automation
• Participating in on-call and incident response, with a strong focus on making incidents rarer over time
• You’ll have room to design and automate, not just respond to alerts.

Site Reliability Engineer – ClickHouse

Business Development Rep

• Own the outbound pipeline engine. Iterate on the targeting strategy, account selection criteria, and signal-based prioritization that tells your team who to reach and why now. Start with what doesn't scale, then systematize it.
• Manage and develop a team of cracked BDRs, some of whom are here already (Andreas, Lorena, Melad). Coach daily on messaging, objection handling, qualification discipline, and outreach quality. Run weekly 1:1s focused on skill development, not just activity review. Build a ramp plan that treats the trajectory of learning as the primary leading indicator in the first 60 days.
• Build the tooling and automation layer. Help design and maintain Clay.com workflows, Salesforce enrichment processes, and AI-assisted sequence generation without being a slop-cannon. You should be able to build a Clay table from scratch, not just use one someone else built.
• Own the metrics and reporting. Build pipeline generation dashboards, track leading indicators (response rates, meeting quality scores, AE acceptance rates), and produce a weekly pipeline generation report. Instrument everything in PostHog, Lemlist, and Salesforce to make it so.
• Coach qualification discipline. Implement and coach a qualification framework that ensures meetings passed to AEs are qualified. Disqualification is a feature, not a failure – build the taxonomy and track the reasons.
• Iterate on messaging and channels. A/B test outreach sequences across email, LinkedIn, video, X, Discord, TikTok and creative channels. Maintain a living playbook that captures what works, what doesn't, and why.
• Collaborate with the TAE team on target refinement. Use feedback loops from AE deal outcomes to continuously sharpen targeting.
• You report to Ben (Revenue Leader). You'll work closely with Abhishek (GTM Engineer) on tooling and data infrastructure.

BDR Team Lead

Engineer

• Make technologies explainable and legible to both humans and agents
• Maintain and design knowledge bases
• Engineer and orchestrate context pipelines
• Build and ship agents powered by the above
• Working on our AI Wizard, an AI agent that onboards thousands of users to PostHog
• Building custom agents, harnesses, skills, context pipelines, and MCPs and shipping them to production
• Building systems to maintain our developer docs and knowledge bases using docs-as-code and AI engineering techniques
• Creating technical content across multiple mediums like docs, example apps, or video explainers
• Creating workflows for publishing streams like the changelog
• Working with other teams so they can build on top of our systems

Context Engineer

Revenue Operations

• Sales compensation: Design, model and maintain rep comp plans so incentives actually point at company revenue goals. Own quota setting and the modelling behind it. Run comp scenarios and pressure test them before they ship. Own comp planning each cycle, from first model to rolled out plan. Give reps and leads live visibility into attainment throughout the quarter and flag proactively when someone is tracking behind.
• Monthly sales growth review: own the cadence end to end: prep, analysis, and a clear read on what's driving and blocking growth. Surface gainers, losers, new vs expansion revenue, and where mature customer growth is slowing. Don't let signal wait for the monthly meetings: run lightweight weekly/biweekly updates pushed to sales leads and reps so the numbers reach people without being pulled. Treat the review as a decision making tool: leading indicators, levers and gaps, not just numbers.
• Triggers & proactive monitoring: build alerting on the things that actually move sales led revenue: deals slipping stages, forecast diverging from pacing mid quarter, reps falling behind attainment, churn or expansion signals, ICP score outliers. Catch problems early and route them to the right rep or lead with a recommended action, so the monthly review becomes synthesis rather than discovery.
• Pipeline & forecast discipline: own pipeline hygiene, deal stage definitions and forecast accuracy, working collaboratively with the Revenue Leader. Design the minimum viable process that gives reliable signal without burying reps in CRM admin. Be opinionated about the data, metrics and roadmap for Salesforce and Vitally.
• Decision support: run win/loss analysis, set discounting and pricing guardrails (with the analysis behind them), implement ongoing tests across the sales funnel and design small experiments on the sales motion with an honest read on whether they worked.
• A sales revenue source of truth: Build the trustworthy activation, expansion and attribution metrics layer for the sales led motion. Work out what actually correlates with revenue vs what we've assumed (e.g. whether our ICP score tracks real revenue outcomes). Dig into open metric questions, e.g. how NRR rolls up and the deltas in it. Be the person we trust for "what's really happening with sales led revenue"

Revenue Ops Manager – Sales Focused

• 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?
• 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?)

Developer

Account Executive

• Technical Account Executives own the initial relationship with customers who get in touch via the website and want to speak with a human before signing up to PostHog. It’s early days, so you’ll cover the full spectrum of customers from high-velocity startups looking to move quickly, to more complex strategic engagements with Mid-Market/Enterprise customers.
• Winning new business. You'll find your way to the right people at prospective customers — engineers, PMs, founders — and show them why PostHog beats whatever they're using now. You own the whole deal, first call to close and beyond, and you’re comfortable in your ability to meet and exceed a quarterly target.
• Owning customer feedback and making sure it gets to the wider PostHog team. You’ll work directly with product teams, we don’t believe in bureaucracy here.
• Being hyper responsive is a must. You need to feel like an extension of a customer’s existing team. We try to do as much customer comms in Slack as possible.
• You’ll need to be an expert on all PostHog products, so that you can help customers see the value and adopt them.
• Comfortable with outbound. You'll earn meetings through relevance and creativity – not through volume and pressure. We do weird outbound.
• Switching contexts comfortably. Prospect and triage leads in the morning, enterprise evaluation in the afternoon, async Loom response to a customer question in between. You adjust tone, depth, and approach for each without losing quality.
• Turning both inbound and outbound lead flow into a real pipeline that converts. Lots of people get in touch with us. Not all of them are deals. You should be able to tell the difference quickly, prioritize who PostHog will be a good fit for and close them efficiently.

Technical Account Executive

Technical Customer Success

• Building relationships with your users. You should know who the key people are at each company, and they should know you.
• Owning their feedback and making sure it gets to the wider PostHog team.
• Investigating technical issues. You're the first person to dig into customer issues, often solving them yourself rather than immediately passing to support.
• Being super responsive to their Slack messages, support tickets, and emails.
• Being their favorite ever Customer Success person to work with!