My process had a very specific kind of difficulty: a timed technical assessment that felt tightly controlled and punishingly strict. The test came with a total of 16 questions across 55 minutes, and only a handful of them required writing code. Copying was disabled, and it wasn’t allowed to use external IDEs—everything had to be done within their constraints.
The proctoring setup was also a major part of the stress. I had to use a webcam with full-screen mode, and they explicitly prohibited AI tools, online resources, and any external help. That combination made the whole thing feel less like a normal coding exercise and more like an exam environment.
4 months ago
Difficult Neutral Paris
After application screening, I started with a recruiter-style video interview to talk through my background and align on the next steps. Not long after, I had technical interviews that leaned into coding practice, with one of the early rounds structured around medium-style LeetCode problems where the discussion went deeper than just solving once—I had to explain my reasoning and then consider improvements.
The process also included a separate technical conversation focused on web technologies and concepts, which felt like a distinct evaluation of how I think about the web stack rather than just general programming.
5 months ago
Average Neutral Paris
My interview journey ended up being far messier than what I initially expected. I first went through screening and early technical steps, and the recr…
6 months ago
Average Positive United States
After the initial recruiter call, I moved into a structured sequence that felt pretty transparent from the start. I had a tech screen focused on codin…
12 months ago
Difficult Negative Paris
My interview process stretched into a seven-step marathon that dragged across roughly two months, with about a month of silence before a final “no tea…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Stages
The interview process typically follows a structured sequence starting with a recruiter call, followed by technical assessments that include coding and system design interviews, and concluding with behavioral evaluations. Candidates noted a mix of remote and onsite formats, with clear expectations set at each stage.
Candidates experienced a variety of coding challenges, often modeled after LeetCode problems, focusing on algorithms, optimization, and debugging. The technical interviews required candidates to explain their thought processes and consider improvements beyond just arriving at a solution.
LeetCodeAlgorithmsDebugging
System Design Interviews
The process included system design discussions that assessed candidates' architectural reasoning and ability to tackle complex design problems. These interviews often required candidates to articulate their design decisions and trade-offs clearly.
System designArchitectural reasoningTrade-offs
Behavioral & Cultural Fit Interviews
Behavioral interviews were conducted to evaluate candidates' past experiences and alignment with company values, often using structured formats like STAR. These rounds aimed to gauge how candidates would fit within the team and company culture.
BehavioralCultural fitSTAR
Logistics & Communication Issues
Several candidates reported logistical challenges, including delays in receiving materials, last-minute changes to interview formats, and inconsistent communication from the company. These issues contributed to a sense of frustration and uncertainty throughout the process.
LogisticsCommunicationDelays
Overall Difficulty & Candidate Experience
The difficulty level of the interviews varied, with some candidates finding the process challenging but fair, while others felt overwhelmed by shifting requirements and unclear expectations. The tone of the interviews also played a significant role in candidates' experiences, with supportive environments leading to better performance.