After a recruiter chat, my process felt short and straightforward. About a week later I had an interview with the hiring manager’s area leader focused mostly on technical topics, and it lasted roughly half an hour.
Before that, I went through a quick HR conversation—around fifteen minutes—where the questions were more about me, my career context, and general personal background. That part was relaxed and didn’t feel like a heavy interrogation.
2 months ago
Difficult Negative Rome
My first round felt smooth, with the interviewer responsive and the conversation going well. Then the process shifted into something much more intense: I went into a second technical round where questions came very fast and it leaned on a problem-solving style format. One version of that round required me to create a function on the fly while answering nearly fifty questions.
That same technical-heavy phase also included case-style scenarios and live testing, and it felt like a full hour where I couldn’t really catch my breath. The overall difficulty was clearly higher than the first step.
2 months ago
Average Positive Kuala Lumpur
I started with an intro-style session, and then moved into two main parts: a technical interview and an HR interview, both handled online. The technic…
3 months ago
Difficult Negative Belgium
I had a scheduled interview that never happened, and it immediately changed how I felt about the process. I waited through the entire booked time slot…
5 months ago
Average Positive Paris
My path was described to me as fairly quick and smooth overall, lasting up to about three or four months at most. The process had four interviews tota…
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 includes an HR screening followed by one or more technical interviews, often culminating in a final discussion with a manager or team member. The overall timeline can vary, with some candidates experiencing a quick process of a few weeks, while others face delays of several months.
HR screeningTechnical interviewManager discussion
Technical Interview Focus
Technical interviews often emphasize problem-solving skills, coding on the fly, and understanding of software design principles, including architecture and best practices. Candidates should be prepared for both theoretical questions and practical coding exercises, with some interviews requiring live coding or whiteboard sessions.
Coding exercisesSoftware designProblem-solving
Behavioral & HR Conversations
The HR interviews generally focus on personal background, motivations, and cultural fit, often using the STAR method for behavioral questions. These conversations are typically more relaxed compared to technical rounds and serve to gauge alignment with company values and expectations.
STAR methodCultural fitMotivations
Communication & Feedback
Candidates frequently report issues with communication, particularly after technical interviews, where feedback may be sparse or delayed. Many expressed frustration over a lack of closure, with some not receiving any updates post-interview, leading to feelings of being forgotten.
FeedbackCommunicationClosure
Interview Difficulty & Expectations
The difficulty of interviews can vary significantly, with some candidates describing intense technical rounds that test depth of knowledge and problem-solving ability. It's important for candidates to manage their expectations, as the perceived difficulty may not always align with the outcome.
Interview difficultyExpectationsProblem-solving
Candidate Experience & Reflections
Candidates often reflect on the overall experience, noting how the tone and structure of interviews impacted their perception of the company. Positive experiences were linked to clear communication and supportive interviewers, while negative experiences were marked by disorganization or mismatched expectations.