I applied online. The process took 4 weeks. I interviewed at Alan in Nov 2025
Average interview
Application
I interviewed at Alan in Jan 2026
Interview
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.
Interview questions [1]
Question 1
[Frontend / React] You are asked to find three bugs (one per page), explain how you would prioritize them if you were a Product Owner and why, and then fix them in order while navigating the code live.
Applied through the portal, where I was asked some open-ended questions. Was invited to a screening call and informed that the best way to prepare is by reading the blogs of the company. No one showed up at my screening call. Eventually, I had that rescheduled. The engineer interviewing me hadn't actually read my CV, because they didn't know I am currently unemployed. Kudos for the courtesy of sending a personalised rejection email.
Interview questions [1]
Question 1
What do you do in your current position? If you could change something about project X, what would it be?
I applied through other source. The process took 1 week. I interviewed at Alan (Paris)
Interview
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.
Interview questions [1]
Question 1
A list of questions that they prepared without any open questions about the candidate's profile
