PostHog
Backend Engineer
Remote Growth - Billing role with clear candidate location fit.
PostedJun 22, 2026
Eligible countries38 accepted countries
Seniority signalOpen level
Work settingRemote
Accepted candidate locations
Role overview
Backend Engineer
Requirements and responsibilities
Readable role content extracted into sections for faster review.
About PostHog
- 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.
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.
What you'll be doing
- 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.
- Making all of the above go brrr.
What you'll be doing
- Implementing a new, ledger-based revenue model and re-building all dashboards and investor reports on top of it.
- Making billing the source of truth for pricing, subscriptions and invoicing.
- Shipping 5+ pricing launches and changes this quarter, including two new pricing models.
You’ll fit right in if:
- Strong backend engineer. Python, SQL, and complex data modeling should feel like home.
- Edge cases make you excited, not anxious.
- Experience with data pipelines, task queues, and workflow orchestration - we still have a lot of Celery but are leaning more into Temporal and Dagster.
- If you've done something manually twice (or seen someone else do it) - you're already building an automation or an internal tool to make it easier.
- Happy paths are maybe 10% of billing. You treat error handling, rollbacks, and retries as the actual work - not TODOs you'll "get to later".
- You don't need someone to tell you what to build. You've started a company, led a major project from scratch, or shipped an impressive side project.
You’ll fit right in if:
- You've built and scaled usage-based billing systems before (and have the scars to prove it).
- You get weirdly excited about revenue modeling, forecasting and accounting ledgers.
- You have a decent guess which one of these we made up: Q2C / AR / B2R / GAAP / ASC 606 / NRR.
You’ll fit right in if:
- You only want to work with other engineers - billing touches every team at PostHog, from product to finance to GTM to marketing.
- You need clearly defined requirements before you start building.
- You think billing is a solved problem - we thought so too, once.
Similar roles
Keep a backup shortlist.
Python 8 accepted countries
Senior Backend Engineer (AdTech)Leap ToolsView role Python 8 accepted countries
Senior Backend EngineerLeap ToolsView role Python 8 accepted countries
Application Security Engineer (Tech Lead)Morgan StanleyView role Eas Build, Expo 8 accepted countries
Senior/Lead Mobile EngineerVox MediaView role Stack
Use these tags to compare similar remote roles.
Location eligibility
Candidates should apply only when their profile country is listed here.
Your profileCountry not setSign in to check your country against this role.
View all 38 accepted countries
Hiring flow
WithMira shows the role, then sends candidates to the company application.
1Check role fit, stack, and location eligibility in WithMira.
2Open the company application page from the tracked apply link.
3Save the role or subscribe for similar opportunities before leaving.