I went through the earlier stages already, and by the time I was scheduling my next conversation I’d completed an OA and a machine-coding round. The recruiter had set expectations that the next step would be a conversation with an Engineering Manager, which was the stage I was trying to understand better.
From what I could infer at the time, the flow I was in was basically OA first, then machine coding, and then an EM discussion. I was mostly curious what iOS-specific topics they might go into at that manager stage, since the earlier rounds weren’t specifically labeled as iOS-focused from the way I’d heard about them. Overall it felt like I was progressing normally, just at the point where I’d need to align with what the EM was looking for, not just the coding outcomes.
4 months ago
Average Positive Amsterdam
I applied through the portal and the OA showed up the very next day. The assessment gave me 90 minutes, and I had to solve problems that involved REST API and SQL. I hadn’t expected those topics to be part of the coding OA, so I didn’t get to a polished result. I remember leaving feeling like my solutions were only partially correct. The rejection came back the next day, which made the whole thing feel very abrupt.
5 months ago
Average Positive Amsterdam
My application process felt straightforward and low-drama. I went through the technical part and, honestly, the technical interview itself was enjoyab…
5 months ago
Difficult Negative Amsterdam
A recruiter reached out to me and then the process ramped up quickly: I had two intro meetings, followed by three interviews covering system design, c…
5 months ago
I applied for the Software Engineer I role and received an online assessment link. The process for me was basically a single round focused on data str…
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
Application Process & Initial Assessment
Candidates typically start with an online assessment (OA) that includes coding challenges, often focused on data structures, algorithms, REST APIs, and SQL. The OA is usually followed by a technical interview or a screening call, which may vary in structure and content.
Online AssessmentData StructuresAlgorithms
Technical Interviews
Technical interviews often consist of live coding sessions and system design discussions, where candidates are assessed on their problem-solving skills and ability to optimize solutions. The focus is not just on correctness but also on the reasoning and efficiency of the solutions provided.
Live CodingSystem DesignOptimization
Behavioral & Cultural Fit Interviews
Behavioral interviews are conducted to evaluate candidates' cultural fit and collaboration skills, often using questions about past experiences and conflict resolution. These discussions typically follow technical assessments and are seen as an important part of the evaluation process.
BehavioralCultural FitSTAR Method
Interview Structure & Flow
The interview process is generally structured with a clear sequence, starting from the OA, moving to technical assessments, and concluding with behavioral interviews. However, candidates have reported variability in the clarity and communication regarding the next steps.
Interview StructureProcess FlowCommunication
Timeline & Follow-Up
Candidates have experienced varying timelines, with some reporting quick responses while others faced long waits without updates. The lack of communication post-interview can lead to frustration and uncertainty about the outcome.
TimelineFollow-UpCommunication Issues
Overall Difficulty & Candidate Experience
The overall difficulty of the interviews is often described as moderate, with candidates feeling that the interviews were respectful and fair, though some found the assessments challenging. Many candidates reflected on the importance of preparation for both technical and behavioral components.