Role description
PostHogAbout PostHog
PostHog is your product’s context layer. It ingests and stores your analytics, errors, replays, and business data so you and your agents can query and act on it.
We launched out of Y Combinator's W20 cohort. We've since shipped more than a dozen products, including:
A suite of analytics and observability tools, including product analytics, replay vision, AI observability, and error tracking
PostHog MCP for users and their agents to query and act on their product and business data
Data warehouse so users can query product and customer data together using custom SQL insights.
We are:
Product-led. More than 500K 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.
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
Help us understand how PostHog grows, what that growth costs, and what we should plan for next. Working directly with our Finance team, you’ll own the day-to-day consolidated financial model, expense planning, and board reporting, with their guidance. You’ll explain differences between actual results and plans, partner with team leads on hiring and spending decisions, and ask thoughtful questions that challenge our assumptions.
What you’ll be doing
Corporate planning and consolidation
Maintain the integrated three-statement forecast: income statement, balance sheet, and cash flow. Keep actuals, assumptions, and scenarios consistent and easy to follow.
Own the quarterly board pack and investor reporting. Report costs versus plan each month and explain what changed. Support fundraising analysis when needed.
Operating expenses and business partnering
Work with team leads to track hiring and vendor spending. Update the forecast each month and explain changes.
Set up monthly planning reviews so team leads can see their spending outlook and discuss changes.
Revenue and commercial analysis
Support Mine's revenue modeling, check inputs and calculations, document assumptions, and explain performance versus plan.
Run the weekly revenue update when Mine is out.
Example public issues/projects:
The models and board materials are internal. These links provide public context for example projects.Build a consolidated forecast and monthly reporting pack. Public context: Finance team
Build a headcount and vendor-spend forecast that shows what changed each month and which decisions need review. Public context: Spending money
Build an infrastructure cost forecast and show how cost per product changes as usage grows. Public context: Pricing and usage-based products
What you won't be doing
❌ Sales Ops execution (deal desk, contracts, credits/refunds, commission calculations, policy implementation)
❌ Accounting close, revenue recognition, collections, and the GL
❌ Billing-system engineering or ownership of the data platform. The analyst uses and checks these teams' outputs for planning.
Requirements
Build and debug an integrated three-statement model in Excel or Google Sheets. Make assumptions explicit, add checks, and test scenarios.
Turn an unclear business question into a model. Separate facts from assumptions and explain which inputs drive the answer.
Reconcile model outputs to source data and investigate discrepancies. Keep forecasts and reporting accurate and up to date.
Explain why results differ from plan, get useful inputs from team leads, and follow up on missing information.
Ask questions, challenge assumptions constructively, and want to learn how a software business works.
AI is part of how you work. You use tools to build and check models, write SQL, and automate reporting, and you can show us examples of this.
Work in a small team where processes are still being built.
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