Real, anonymous reports from people who interviewed for Software Engineer at N26, newest first and distilled into what to expect across the loop.
I started with an HR-style recruiter call that went smoothly, and shortly after I was asked to complete a Codility assessment. The exercises felt like typical LeetCode/HackerRank-style algorithm problems—pretty standard and, for me, not especially hard. I spent roughly an hour and a half working through it and submitted.
I went through what felt like a pretty structured sequence for a Senior Software Engineer role: a recruiter chat, then a LeetCode-style task submission, followed by a live coding round. After that came a technical discussion that blended into a system design round, and then a cultural fit stage.
The interview process typically starts with an HR call, followed by a Codility coding challenge, live coding rounds, a system design interview, and a behavioral interview. The overall timeline can stretch from a few weeks to over a month, with varying levels of communication and feedback throughout.
Candidates can expect a Codility assessment featuring LeetCode-style algorithm problems, which may vary in difficulty from medium to hard. Some candidates reported issues with problem clarity and the evaluation process, feeling that it relied heavily on specific approaches rather than overall coding skill.
The live coding rounds often involve solving algorithmic problems while discussing thought processes and trade-offs with interviewers. Candidates noted that these sessions can be challenging, especially when technical environments are not well-prepared or when communication issues arise.
The system design interviews require candidates to think critically about architecture and scalability, often involving real-world scenarios like account creation or handling slow response times. Candidates should prepare to discuss non-functional requirements and trade-offs in their design choices.
Behavioral interviews focus on past experiences and how candidates handle collaboration, conflict resolution, and pressure. The format typically follows a 'tell me about a time' structure, and candidates should be prepared for a fast-paced, high-pressure environment during these discussions.
Candidates reported mixed experiences regarding communication and feedback throughout the process, with some feeling that responses were generic or lacked transparency. It's important to be prepared for potential delays and to seek clarification if feedback is unclear.