Pros: - People are very nice and eager to help you - Agile environment. Project lasts at most 3-4 weeks so it doesn’t get boring - Lots of responsibilities. Doctolib doesn’t have project managers. It’s the software engineer’s role. Every project has a “tech holder” whose job it is to talk to product and create functional requirements and JIRA tickets. - The remote policy was great while I was there, but I have been told by my past coworkers that they stopped hiring remotely.

Cons: - Very complex product. Doctolib is a huge product dealing with doctors, agendas, calendar availabilities, reasons for consulting a doctor, … Depending on which team you find yourself in, you might have to deal with a LOT of product knowledge. - Confusing roadmap. Unfortunately, the roadmap decisions are very decided top down. We would be handed projects just because other teams didn’t have the bandwidth. We would also be told by the CTO to reduce bug injection rate, but with no concrete plans. - Big code base and no plans to address technical debt. In a bid to become profitable, Doctolib is far more focusing on releasing new features rather than address some of the very real and very blocking technical debt present in the codebase. There is also no initiative to improve the developer experience so merging and shipping can also be a pain. -The promotion process is broken. You need to build a “case” for promotions, but some of their criteria require to touch things that you might not have access to (like security). Even if you have the level, you would probably need to wait a few years and get yourself “known” with some big project before you get it.

Pros: The topics include colleagues, product, impact, offices, and perks.

Cons: Middle management planning dependencies in the codebase involves a top-down culture.

Pros: Fast growing, Intelligent and full of creative minds

Cons: They don't pay very well.