Sefism is free for learners. We are here to help you grow, one step at a time.Join for free
Sefism.
Health techFunded startup

Doctolib

Builds online appointment booking for patients and practice management software for doctors in France, Germany and Italy.

Not known6 stage process documentedFounded 2013
Headquarters

France

Headcount

1,000 to 5,000

1,000 to 4,999 people
Work model

Not known

Hiring

Not known

Not enough signal to say. Check the careers page directly.
Where to apply
Careers pageWebsite

Ask for a referral to Doctolib

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

Open internships

How they hire

The process usually takes about 4 weeks and the final interview is on site, with travel costs covered. Mobile engineers do a mobile app design interview instead of system design and skip the online test, and engineering managers replace coding with a role-play leadership case study.

  1. 1

    Recruiter interview

    Official
    Recruiter screen

    A first meeting about your background and motivation, with a few technical questions.

  2. 2

    CodinGame test (junior profiles)

    Official
    Online test

    Junior candidates take an online coding test before the live rounds.

  3. 3

    Coding interview

    Official
    Live coding

    A live coding exercise.

  4. 4

    System design interview

    Official
    System design

    Assesses your design and architecture skills.

  5. 5

    Behavioural interview

    Official
    Culture fit

    A discussion of real situations you have handled, to understand how you would act on the job.

  6. 6

    Reference check and offer

    Official
    Offer

    References are checked before the offer is made.

What comes up

Recurring themes from candidate accounts, not a question bank. Nobody is served by leaked question lists, least of all you in the interview.

  • Thinking out loud

    Official

    For technical and analytical questions, Doctolib wants you to talk through your approach, assumptions and trade-offs; not having every answer is fine.

  • Motivation and the mission

    Official

    Come ready to explain why the role excites you, what you are passionate about, and with a few thoughtful questions about the company.

  • Realistic coding in CoderPad

    Reported

    A CoderPad case study says Doctolib replaced a long take-home and three technical interviews with a timed coding screen and one collaborative live coding interview.

Worth reading before you apply

From the Sefism resource library, matched to the rounds above.

Platform
Design Gurus Problem Set

A browsable practice library of coding problems that can be filtered by pattern, data structure, difficulty and company, so you can drill exactly the weakness you found this week. Patterns include two pointers, sliding window, hash maps, stacks, backtracking and greedy algorithms, with company filters for Google, Meta, Microsoft, Amazon, Oracle and LinkedIn. Free to browse, with an in-browser editor and solutions.

  • Job search
  • DSA
Design Gurus · Interview Prep · Ongoing
FreeDetails
Course
Grokking 75: Top Coding Interview Questions

A course built around 75 coding interview questions chosen for coverage across 18 topic areas, from arrays and sliding window to graphs, backtracking, dynamic programming and tries. Each question has a step-by-step algorithm, a walkthrough and complexity analysis, with solutions in six languages. It suits candidates with a few weeks before an interview who need a balanced, finite problem set rather than an endless list.

  • Job search
  • DSA
Design Gurus · Interview Prep · 3 to 4 weeks · Intermediate
SubscriptionDetails
Roadmap
System Design Interview Playbook

A learning path that bundles five courses into one sequence for system design preparation: System Design Fundamentals, Grokking the System Design Interview, Advanced System Design Interview Volume II, Grokking Microservices Design Patterns and Grokking Design Patterns for Engineers and Managers. Together they add up to 76 chapters and 666 lessons. It suits engineers who want a complete, ordered curriculum instead of assembling one from scattered posts.

  • System design
  • Job search
  • Career
Design Gurus · System Design · 2 to 4 months
SubscriptionDetails
Guide
Design Gurus Newsletter

A free newsletter of short, focused posts on system design and problem solving, from the team behind the Grokking courses. Recent posts cover company interview processes (such as OpenAI and Anthropic roles), the most asked mobile system design questions and preparation plans, each linking to a fuller article on the blog. It suits engineers who want a steady, low-effort way to keep system design and interview topics fresh between deeper study sessions.

  • System design
  • DSA
Design Gurus · System Design
FreeDetails
Guide
GeeksforGeeks

A very large site of articles on data structures, algorithms and core CS subjects such as operating systems, DBMS, computer networks and OOP, usually with code in several languages, plus practice problems and paid courses. It is handy for revising a university topic or finding a worked example of a specific algorithm. Quality varies because much is community written, so cross-check anything surprising against a textbook or official documentation.

  • DSA
  • CS fundamentals
  • Databases
GeeksforGeeks · Other · Ongoing reference
FreeDetails
Roadmap
Sefism CS Core Subjects Roadmap

An eight-stage roadmap through the core CS subjects: how a computer runs a program, OOP and design, operating systems, computer networks, database theory and internals, software engineering and theory, finished with a systems project such as a shell, an HTTP server or a tiny database. It suits CS students and self-taught developers filling the same gaps, and favours understanding shown in working code over memorised answers.

  • DSA
  • CS fundamentals
  • Databases
Sefism · Other · About 216 hours, 22 to 46 weeks · Beginner
FreeDetails
Browse the whole library

What it pays

Nothing collected for this company yet, and nothing worth guessing at. A made-up range is worse than no range because people negotiate against it.

Add to the Doctolib page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.

Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Universities they recruit from

No sourced university links yet. A campus drive, a career fair appearance or an internship partnership is what puts a university here.

Add to the Doctolib page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.

Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

How to actually get seen

Explain your reasoning as you go in the coding and design rounds. Doctolib suggests waiting a year before reapplying after an unsuccessful application.

Sources

Whole profile last checked 2026-09-22.

Interviewed at Doctolib? Fill in what changed.

Processes change, rounds get added, tests get replaced. If what you went through was different from what is on this page, tell me and I will update it.

Want me to refer you here?

Send me the role, your CV and a few honest paragraphs on why you fit it. Where I know someone inside and your profile matches, I will make the introduction. Where I cannot, I will tell you why and point you at the route that does work. You get an answer either way.

Ask for a referral to Doctolib

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

Add to the Doctolib page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.

Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Work with me

Stuck on something specific?

Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.

Book a free sessionSee all services

Follow along

New writing, resources and project ideas land here first.