The technical interview was conducted in React using CoderPad. Candidates are given a small sandbox project to work on — a simplified Doctolib-like application with a list of doctors, the ability to make bookings, and to retrieve them later. The goal is to identify existing bugs in the application, prioritize them, and then resolve them in real time while navigating through the codebase. The code itself was very clear and well written, making it relatively easy to understand the structure and logic. Overall, the experience felt pleasant, realistic, and very close to actual day-to-day work. The only downside is that it can feel a bit fast-paced due to the time constraints. After the interview, I received detailed and personalized feedback, which was very much appreciated and reflects a thoughtful and respectful hiring process.

Having a backend background, I was contacted by an engineer from Alan to initiate an interview, saying that they liked my profile. I was hesitant, but since I saw that the company recruits "based on people, not profiles," I accepted the interview. I had a call with another engineer. Thanks to Glassdoor, I asked them about their product obsession. Subsequently, I received a rejection email stating that they are looking for a full-stack engineer, not just a backend engineer, and that because I asked questions about the product-innovation ratio, they believe I'm not sufficiently obsessed with the product side.