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.

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.

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 under control.
• You enjoy mentoring and raising the bar of the engineers around you.
• Fluent English

• Experience with two-sided marketplaces, search and discovery, or booking and scheduling systems.
• Experience with monorepos at scale: build tooling, code ownership and shared platform conventions.
• You have exposed product capabilities to AI agents.
• Healthcare or another regulated domain, where data privacy and security shape the architecture.

We care more about how you think and the impact you drive than about the size of your previous company.

Let’s talk money

• A salary adequate to your experience and skills.

True flexibility and work-life balance

• Remote or hybrid work model with or hub in Warsaw;
• Flexible working hours (fully flexible, as in most cases you only have to be on a couple of meetings weekly);
• 20/26 days of paid time off (depending on your contract);
• Additional paid day off on your birthday or work anniversary (you choose what you want to celebrate).

Health comes first

• Private healthcare plan with Signal Iduna for you and subsidized for your family.
• Multisport card co-financing for you to have access to sports facilities across Poland.
• Access to iFeel , a technological platform for mental wellness offering online psychological support and counseling.

Keep growing with us

• Free English and Spanish classes.

We promote and embrace equal opportunities in our hiring process, and also every day at work. When you apply for our roles you receive equal treatment regardless of age, disabilities, gender reassignment, marital or civil partner status, pregnancy or parental status, race, colour, nationality, ethnic or national origin, religion or belief, sex, sexual orientation or any other dimension of human difference. If you require additional support in your recruitment process, we kindly encourage you to let us know. Behind those words you’re reading, there’s a person (hi!) who already helped a candidate by adapting the interviews, and now we’re lucky to have this person with us. So, even if you’ve never asked for it before, may this serve as a sign that, now, you can do so. We can only truly be equal if we adapt to each other.

“We believe all humans, in all their beautiful diversity, should have equal rights, dignity and respect. Period.” Mariusz Gralewski, CEO