After a recruiter touchpoint, the process felt pretty standard until the technical part. I was given a challenge to work on, and then the silence started. I fully completed what I was asked to do, so I expected some kind of follow-up or at least feedback.
Instead, there was no response at all. About a month later I received an email letting me know they’d moved forward with someone else, with no real debrief. The lack of closure was the most frustrating part.
> 1 year
Average Positive Paris
My process stretched across a couple of months. It started with an HR interview, then moved into a take-home assessment where I had enough time to complete it. After that, I had a technical interview that mixed theory with LeetCode-style questions, and the overall vibe there was smooth.
What stood out to me was the rhythm: HR first, then the longer written work, then the live technical check. The questions weren’t hostile or overly tricky in the way some interviews can feel; it was more like a straightforward way of validating both my fundamentals and how I think through problems under conversation.
> 1 year
Difficult Negative London, England
I went through a fairly heavy multi-round loop. It began with a recruiter chat, then I spoke with a manager, and there was also a background check plu…
> 1 year
Difficult Positive France
The process started with an HR conversation, then I had a technical interview with a software engineer. After that came a technical test that was far …
> 1 year
Difficult Negative London, England
After a recruiter call, I had a technical conversation with an engineer and then received a take-home coding test. The process felt very focused on th…
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
Recruiter & Initial Conversations
The interview process typically begins with a recruiter call followed by a conversation with a manager, focusing on the candidate's background and motivation. Candidates generally found these early interactions to be polite and organized, setting a positive tone for the process.
RecruiterHRMotivation
Take-Home Technical Assignment
Candidates are required to complete a demanding take-home assignment, often described as taking between 8 to 15 hours, with expectations for production-ready quality. Many candidates reported feeling the workload was disproportionate to the recruitment stage, and the criteria for evaluation were often unclear or inconsistent.
Take-homeTechnical assessmentProduction-ready
Technical Interviews
Following the take-home assignment, candidates typically participate in technical interviews that assess their coding skills and problem-solving abilities, often including algorithmic questions. The interviews are described as structured, with a mix of technical and behavioral questions, but some candidates felt the evaluation criteria were not always aligned with the initial expectations.
Technical interviewCodingAlgorithms
Communication & Feedback
Feedback and communication throughout the process varied significantly, with some candidates experiencing delays and a lack of closure after submitting their assignments. Many expressed frustration over being ghosted or receiving vague rejection reasons, which left them feeling their time and effort were not respected.
CommunicationFeedbackClosure
Overall Process Length & Structure
The overall timeline for the interview process can be lengthy, often stretching over several weeks or even months, with multiple stages involved. While some candidates appreciated the structured approach, others felt the extended duration contributed to a sense of uncertainty and burnout.
TimelineStructureLength
Cultural Fit & Values Assessment
Interviews often included discussions around cultural fit and alignment with the company's values, with some candidates feeling pressured to express enthusiasm for the company. This aspect was seen as critical in the final evaluation, alongside technical skills.