Staff Engineer

Welcome to the good side of tech You might have heard

about us
, but with a different name: Doctoralia. It all started 12 years ago when we asked ourselves: is anyone in healthcare thinking about patients? We jumped in and we empowered patients by giving them access to leave and read reviews about their visit. We then provided doctors with the technology to manage bookings easily and save time, so they could devote themselves to what they always wanted: treating patients. And today is the day in which we ask you: wanna join us in the next step of making the healthcare experience more human? Docplanner at scale We are leaders in 13 countries so far, and more than 90 million patients trust us every month. 300k+ specialists believe in us and our product, and so do leading venture capital funds such as Point Nine Capital, Goldman Sachs Asset Management and One Peak Partners. And yet, employing over 2.500 people all over the globe, we managed to keep the startup-mindset we started with over 10 years ago. At Docplanner we are a diverse group of over 300 people working in Engineering, Data, and Product teams. We are responsible for building the product for all locations. Many of us have been here for over 5 years, yet we still welcome each new person with great joy and excitement. We could tell you

about us
, but we will let our reviews on Glassdoor speak for themselves. In case you’d like to see how it feels to be 100% yourself at work, here's a video of us. And why should you join us? Because it feels good to tell your family and your friends how you made the world a little bit better. You go to bed knowing that what you do matters, and that your talents align with your beliefs. We want to make the healthcare experience more human, and that starts with you being you. We believe that taking the diversity of human experience into account makes a better healthcare experience for all. We’re not just different: we embrace diversity. We’ll encourage you to come to work your whole self, and that includes not coming to the office at all if you prefer not to, as we're 100% remote friendly. The Role Docplanner is reinventing how we build products, and above all how we write code with AI. We are looking for a Staff Engineer who will set the technical direction for our Marketplace: the patient-facing platform where millions of people search for a doctor, compare profiles and book a visit. The Marketplace is in the middle of a large architectural shift. We are moving it, domain by domain, from a long-lived PHP monolith into our company monorepo, built from vertical slices (API + React web) and shipped with a strangler pattern. The booking flow, doctors' profiles, listings and Q&A are already on that path, and our new search experience is being built natively on it. Your job is to make sure this move ends in a better platform, not just a relocated one. Marketplace capabilities should become clean, well-owned building blocks that the rest of the Docplanner portfolio can plug into. When a patient books a visit, other systems, from patient engagement to our AI assistants, should know about it through a clear contract, not a one-off integration. You use AI coding agents such as Claude Code to do the building, and you own the design, the review and the quality bar. You prototype the hard parts yourself this way and show teams how far the approach can go. Your influence comes from the quality of your decisions and from how much you make the teams around you better. What Success Looks Like in 6 Months
* There is a written, agreed technical direction for the Marketplace on the monorepo: which domains move next, in what order, and what \"done\" means for each. It includes a realistic plan for making the monorepo the source of truth for bookings. Teams use it to plan, not just to read.
* At least one core Marketplace capability, such as bookings, is exposed through a clear, versioned contract that another Docplanner product consumes in production. For example, patient-facing products know which visits a patient has had without calling into the monolith.
* The monolith is shrinking in a measurable way: fewer ad-hoc endpoints and proxy layers, and more domains where the monorepo is the source of truth. Shared domains such as insurances, services, calendar and addresses have a clear owner and a target home.
* You are personally shipping, with AI agents writing the code and you owning the design, review and quality. You set the bar for what AI-native engineering looks like in a large, real codebase.
* AI-assisted workflows for migration and integration work, such as generating contracts, tests and adapters, are proven in one team and being adopted by others. The real indicator of success: teams across the portfolio come to you when they need Marketplace data or capabilities, and they leave with a contract they can build on, not a workaround.

What You'll Do
Own the Technical Direction of the Marketplace
* Be accountable for the target architec