My process for a senior Software Engineer role started with an initial screen, and then I had four virtual onsite interviews. The sequence moved through an AI coding round, then system design, followed by behavioral, and finally values. The recruiting loop felt organized, and I got a fairly quick debrief once the interviews were done.
The AI coding portion went well for me—I felt like I was communicating my thinking clearly. System design was the part that felt shakier; I could tell I didn’t land it as confidently as I wanted. The next morning, I was rejected after the debrief, and I was offered a feedback call.
3 months ago
Easy Positive Paris
After a recruiter screen, I took an online coding assessment and then moved into a small sequence of live interviews. The overall vibe was pretty practical: the coding portion leaned more toward implementation and design thinking than pure LeetCode trick problems. I remember having a few exercises, and the questions were framed in a way that pushed me to explain my approach as I went.
The process felt smooth, and the team I interacted with were genuinely nice. I also had a longer recruiter call where we covered the role and my background, then I went into a final technical interview that again followed a LeetCode-style medium-hard structure. I didn’t end up getting an offer, but it felt like I understood what was being evaluated and that the feedback loop, even if not positive, was respectful.
4 months ago
Difficult Neutral Lisbon, Lisbon District
My process started in the usual way: an initial recruiter video call where we talked through my background and fit, including compensation expectation…
4 months ago
Average Positive Portugal
I went through a process that started with recruiter communication that felt structured, with clear documentation and scheduled feedback prep meetings…
4 months ago
Difficult Positive Paris
Recruiting guided me through a very structured, FAANG-like sequence. After an initial HR screen, I went through two coding rounds, then a system desig…
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 & Timeline
The interview process typically begins with a recruiter screen, followed by a series of technical interviews including coding, system design, and behavioral assessments. Candidates noted that the overall structure was clear and organized, with timely feedback and communication throughout.
Recruiter screenTechnical interviewsFeedback
Coding Assessments
Candidates experienced a mix of coding assessments, often leaning towards practical implementation rather than purely algorithmic problems. The coding rounds emphasized communication of thought processes and problem-solving approaches, with some candidates noting a focus on real-world scenarios.
Coding assessmentImplementationCommunication
System Design Interviews
System design interviews were a common component, focusing on practical engineering trade-offs and real-world applications. Candidates were expected to propose architectures for vaguely defined problems, which required a solid understanding of systems and trade-offs.
System designEngineering trade-offsArchitecture
Behavioral & Values Interviews
Behavioral interviews often included discussions about past projects and values alignment, with a focus on how candidates approach teamwork and problem-solving. This part of the process aimed to assess cultural fit and alignment with the company's values.
BehavioralValues alignmentCultural fit
Candidate Experience & Communication
While many candidates appreciated the structured nature of the process, some reported inconsistencies in scheduling and communication, leading to frustration. Overall, candidates valued respectful interactions and clarity about expectations throughout the process.
Candidate experienceCommunicationScheduling
Pressure & Performance
Candidates noted that the pace and volume of the interviews could be demanding, particularly during coding rounds where multiple questions were asked in quick succession. Managing pressure and maintaining clarity under time constraints were crucial for success.