Senior Platform Engineer

pbHealth can’t wait /b. /p pNot for symptoms to get worse. Not for a six‑month appointment. Not for a system to catch up. But that’s exactly how healthcare works today. You wait, until you can’t. /p pAlan exists to end the wait. /p pHealth is a universal right, and we believe this right can only become real when it’s coupled with prevention. We need to stop treating health as something we repair and start treating it as something we build, every day. It’s not solely a question of willpower. It’s the healthcare system itself that needs to work for everyone, in a sustainable way. /p pSo we are building the new standard in prevention insurance. Alan is the first company that integrates insurance, prevention, and care into a single, acclaimed user experience. /p pWe are on an incredible journey to build a global leading company, with a unique culture. We already partner with 40K+ companies of all sizes, serving more than 1M+ members, and have reached €800M+ in ARR. /p pPrevention as the new norm. That's what we're building with our team of 1000+ people. If it speaks to you: we're hiring across France, Spain, Belgium, and Canada. And beyond. /p h3What you’ll build and who you’ll work with /h3 pEvery Alan product, in every country, runs on the same backend: events, queues, cache, data shared between components, transactions. More than 200 engineers build on it every day. It carries more than 1 million members today. It must carry 10 million, in more countries, with more regulated health data. /p pYou would join Backend Platform, a new team in our engineering organisation. Our job is to rethink the backend of a fully grown company, while it keeps running. Today almost everything runs in one Python monolith on one database. We are moving it towards big services that scale on their own, one pilot at a time. We build the tools that make this possible, and we set the rules for how Alan builds backends. /p pThis is a rare kind of project. The codebase serves real members and customers every day, and we have the mandate to change how it is built. What we decide now will shape how hundreds of engineers work for years. You will learn a lot, and your work will have a real impact. /p pThe team is small and growing: 3 engineers today, 6 next year. Its mission: /p pOwn the backend building blocks every Alan product depends on, and make them simple enough that product teams use them without needing us. /p h3Your scope /h3 ullibThe events pipeline. /b How our components and services talk to each other asynchronously: a Postgres outbox, Redis Streams, an S3 archive. It is in production for about 20 components. You make it a product that teams use on their own. /lilibData replication between services. /b A service publishes read-only tables. Other services keep a local, fresh copy and join on it. This replaces slow joins across components. /lilibTowards big services. /b The tools to take capabilities out of the monolith: a service template, APIs between services, traces across services, dependency management. We start with a pilot and turn it into a playbook. /lilibThe shared runtime. /b Queues, cache, the transaction layer. Their limits, their SLOs, their headroom. /lilibThe backend direction. /b The rules for how we build backends at Alan, written with the other engineering teams. /li /ul h3The stack /h3 pPython, Flask, SQLAlchemy, PostgreSQL, Redis, RQ, Datadog, all in a monorepo. New services are async-first. We deploy daily and believe in distributed ownership: you build it, you own it. You don't need prior Python experience. /p h3Is it you we're looking for? /h3 h3Experience we value /h3 ulli5+ years of backend engineering, with code other teams depend on: libraries, frameworks, pipelines, internal platforms. You ran it in production and owned it. /liliDistributed systems as a daily tool: events and messaging (delivery guarantees, ordering, idempotence, retries), data replication, consistency, transactions. /liliPostgreSQL in depth: transactions, locks, replication, query plans. /liliYou have split a monolith or built services, step by step, while production kept running. /liliYou measure before you optimise, and you set SLOs and alerts for what you own. /liliEnglish working proficiency. French is not required. /li /ul h3Mindset we value /h3 ullibProduct mindset. /b Product teams are your customers. Adoption is how you measure success. /lilibEnabler. /b You build things others use on their own, instead of doing the work for them. /lilibYou write to think and align. /b Short framing docs and decision records are how this team works with the rest of engineering. /lilibInfluence without authority. /b You get other teams to change how they build, with no reporting line. /lilibIncremental. /b One pilot first, then the playbook. No big-bang rewrites. /li /ul h3Strong plus /h3 pyou worked in a platform team that served product teams /p ullievent-driven architecture at scale /liliCDC or logical replication /liliasync Python (asynci