PostHog

Security Engineer

• Triage and Tune: You’ll own our Wiz alerts. You’ll be responsible for turning "noise" into "actionable findings" and ensuring we aren't just staring at a dashboard of issues that don't actually matter. We already get relatively few alerts, and we’d like to even further reduce that to just the ones that matter.
• Incident detection, response: You’ll lead the charge on security incidents. Whether it’s a compromised NPM package or a suspicious IAM pattern, you’ll help coordinate the response and lead the post-mortem. You’ll also help build our IR runbooks.
• Build Observability: You’ll build detection pipelines, and close our network-based observability gaps. We want to be able to trace network requests and suspicious activity all the way back to specific code paths.
• Threat Hunting: You’ll proactively hunt for threats in our AWS environment. You won't just wait for an alert; you'll define what "good" looks like and build the telemetry to prove it.
• The VDP: You’ll support our Vulnerability Disclosure Program, triaging reports from researchers and eventually transitioning us toward a formal bug bounty program.
• Enable the Team: You’ll support our product squads with threat modeling and secure design reviews. We don't do "Security says no", we do "Security says 'here is how to do this safely.'"
• Help build our security culture: Our engineers trust the security team and view security as an enabler. You’ll be a crucial part of helping to continue this excellent (and uncommon) working relationship.

Full-stack Engineer

• You will be joining PostHog as a Product Manager
• Run growth reviews for products that have product-market-fit
• Dive into data research projects
• Organize user interviews
• Provide just-in-time product feedback for new and existing features
• Coach product engineers

Product Manager, Ex-Founder/Ex-Product Engineer

Operations

• Automate, manage, and maintain ClickHouse.
• Build systems for provisioning and scaling ClickHouse clusters.
• Optimize performance at instance and node level.
• Build a query optimizer for ClickHouse.

ClickHouse Operations Engineer

• Most companies treat FinOps like a janitorial service: engineers make a mess, and the FinOps person follows them around with a broom and a spreadsheet of "unattached EBS volumes."
• At our scale, we aren't interested in "saving money" in the abstract. We’re interested in efficiency as a product feature. Every dollar we shave off our unit economics is a dollar we can pass directly back to our customers, making our product more competitive and our margins healthier.
• We’re shifting FinOps left!
• We believe the most expensive line of code is the one written without considering how it scales. We want to move cost conversations from the billing cycle to the design doc. In this role, you aren’t a gatekeeper; you’re an enabler. You’ll be successful when:
• cost is a first-class citizen: Engineers treat "cost per query" or "cost per ingest" with the same rigor they treat latency or availability. You’ll be the person engineers go to when asking, "Will this architecture be expensive?" and have the credibility to provide the right answer.
• the "hot potato" dies: No more reactive scrambles when the AWS bill hits. You’ll build the systems that give teams the autonomy to own their own margins.
• cultural compounding: You shouldn't be a hero who personally finds $2M in a closet. You’ll be the architect who builds a culture where 100 engineers make 1% better decisions every day.
• Own the strategy and enable cost-aware engineering: You build the systems and attribution structures (tagging, showbacks) that give teams ownership of their impact.
• Partner with Finance: Explain variances, maintain clean cost allocation, and help the business understand margins by product line.

FinOps Engineer

Sales

• Increasing sales velocity and hustle - getting the sales teams to spend more time in person with customers, going deeper with accounts, and role modeling this yourself.
• Building the sales machine that scales us beyond $100m ARR. You will already have seen or have strong intuitions about the things we should do to grow, and conversely the things to avoid.
• Building an outbound function (warm and cold) - we are figuring this out as we go, but need someone who has at least seen this work happen. Nobody on the team has experience doing this.
• Predictable forecasts, repeatable pipeline creation, scalable rep productivity are all things that we have a loose grasp of at the moment. You will build this into a system.
• Improving things like our market segmentation, coverage model, deal ownership rules/handoffs.
• Reporting to Tim (co-founder & co-CEO) and building and coaching a smaller team of second-line leaders.

Sales Lead

Backend Engineer

• Scaling our billing system to $100M+ revenue (the hundy) by the end of 2026, and well beyond (the billy?).
• Building billing primitives flexible enough that launching a new pricing model doesn't require rearchitecting everything.
• Making our usage reporting and limiting near-realtime.
• Turning usage and messy raw invoice data into actionable internal reports, accurate forecasts, and compliant financials.

Security Engineer

Product Manager, Ex-Founder/Ex-Product Engineer

ClickHouse Operations Engineer

FinOps Engineer

Sales Lead

Backend Engineer – Billing