Staff Engineer (100% Remote within Spain)
docplanner · Spain · remote
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 https://www.glassdoor.es/Overview/Working-at-DocPlanner-EI_IE1071394.11,21.htm?countryRedirect=true 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 https://bit.ly/3xwnSAk.
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 will 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 architecture of the Marketplace across search, listings, doctors' profiles and the booking flow. Make sure search, doctors' profiles, listings and the booking flow fit together end to end on the new stack.
- Shape the monolith-to-monorepo migration: decide which domains move next, how to move them safely (strangler routing, anti-corruption layers, shadow traffic, staged source-of-truth flips) and when a domain truly counts as migrated. Q&A, already fully migrated, is the reference; the hard cases come next, such as doctor and integration booking flows with many callers and data strategies.
- Move domains from "thin proxy over the monolith" to "owned natively in the monorepo": data, business logic and persistence, not only the frontend. Profiles and listings, which already run on the new frontend, are the first candidates.
- Make the Marketplace easy to integrate with. Turn Marketplace capabilities into reusable building blocks for the whole Docplanner portfolio. Bookings, profiles and search should all be consumable through clear contracts.
LEAD THROUGH AI-NATIVE ENGINEERING
- Ship production changes in the Marketplace codebases by directing AI coding agents: prototype the riskiest parts of a migration or integration yourself, then hand teams a proven path.
- Drive AI-assisted development past where we are today, especially for migration work: understanding legacy code, generating contracts, adapters and tests, and keeping parity between old and new.
- Help make Marketplace capabilities usable by AI agents as well as people.
MULTIPLY THE TEAMS AROUND YOU
- Partner with Engineering Managers and Product Managers on planning and on unblocking cross-team work.
- Mentor senior engineers on architecture, system design and pragmatic decision-making.
- Contribute to Docplanner's Staff+ community of practice, sharing what works and keeping technical standards consistent across areas.
WHAT WE'RE LOOKING FOR
In a sentence: someone who can see the whole system, change it safely while it is running and make dozens of engineers faster along the way.
- You have led the technical direction across several teams, not just one, and teams followed because your decisions held up in production.
- You have taken a large legacy system apart while it kept serving real traffic. You know the strangler pattern, anti-corruption layers, data migration and dual-write pitfalls from experience, not from blog posts.
- You are strong in distributed systems and backend architecture, and comfortable in a polyglot environment.
- You bring solid hands-on experience using AI to accelerate software development, and good judgment on when to rely on it and when not to.
- You have moved from writing code by hand to directing AI agents that write it, and you can show how you keep design, correctness and security