PostHog
Backend Engineer- Europe/UK Timezone
Remote Feature Flags role with clear candidate location fit.
PostedJun 24, 2026
Eligible countries59 accepted countries
Seniority signalOpen level
Work settingRemote
Accepted candidate locations
Role overview
Backend Engineer- Europe/UK Timezone
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
- Real-time cohorts, our most-requested feature. Membership is computed on a delay today, which makes it useless for targeting like "users who did X in the last five minutes." Evaluating it in real time at flag-check time collapses a whole category of custom targeting logic people build themselves.
- Moving from a read-heavy to a write-heavy architecture, including a dedicated store for flag evaluation so we're not coupled to the shared Persons DB.
- An AI-first flag management tool we're dogfooding internally, so agents can create, modify, and reason about flags without ever opening the UI.
- Reliability and performance work to lower our p50/p90/p99 latencies and isolate the evaluation path from upstream failures (load shedding, request hedging, decoupling from the Persons DB).
Requirements
- You've built and operated systems that handle high volumes of requests or data (millions+ per minute), and you care about tail latency, caching, and distributed systems failure modes
- You're productive in Rust and Python, or confident you'll get there fast. While the app is Django, the evaluation engine and much of our backend infrastructure is in Rust or moving to it.
- You work independently. You can pick a sensible architecture, ship it faster than people expect, and drive it to done without being managed
- You ship changes quickly without breaking a service customers depend on to launch
- You're based in a European time zone
Nice to haves
- Experience with feature flags, customer data platforms, or other real-time decision engines
- You've carried a pager and dealt with incidents
- You're comfortable provisioning and maintaining cloud infrastructure
- Experience with benchmarking and profiling tools
Similar roles
Keep a backup shortlist.
Java, Python 8 accepted countries
Application Security Engineer (Tech Lead)Morgan StanleyView role Python 8 accepted countries
Senior Backend Engineer (AdTech)Leap ToolsView role Python 8 accepted countries
Senior Backend EngineerLeap ToolsView 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 59 accepted countries
AlbaniaAlgeriaAustriaBahrainBelgiumBotswanaBulgariaCroatiaCyprusCzechiaDenmarkEgyptEstoniaEthiopiaFinlandFranceGermanyGhanaGreeceHungaryIcelandIrelandIsraelItalyJordanKenyaKuwaitLatviaLithuaniaLuxembourgMaltaMauritiusMoldovaMontenegroMoroccoNetherlandsNigeriaNorth MacedoniaNorwayOmanPolandPortugalQatarRomaniaSaudi ArabiaSerbiaSlovakiaSloveniaSouth AfricaSpainSwedenSwitzerlandTanzaniaTunisiaUgandaUkraineUnited Arab EmiratesUnited KingdomZambia
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.