There are 5 stages in total. The first stage is a screening call with a recruiter with regular questions about previous experiences and expectations about the role.
Second stage is a Codility challenge that includes 3 problems involving DSA, I found this one to be harder than I thought with the problems involving DP but they only aim for 67% correctness.
Third stage was a pair coding session with two engineers where I had to solve a small technical problem. The problem was of medium difficulty with follow-up questions on how to handle edge cases.
Fourth stage was a system design interview with two engineers. The problem presented wasn't super hard and was mainly focused on async communication between microservices and scalability.
Fifth stage was behavioural interview with two engineering managers that involved a lot of "Tell me about a time when" questions. It was mainly focused on handling shifts in priorities and feedback culture.
In the end they decided to move with another candidate because I didn't want to relocate to Berlin, even though I made it very clear from the first interview that this was not an option for me and they said it was ok not to relocate. Complete waste of time and totally unprofessional.
Tell me about a project you worked that you're most proud of.
The following metrics were computed from 8 interview experiences for the N26 Backend Engineer role in Germany.
N26's interview process for their Backend Engineer roles in Germany is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for N26's Backend Engineer interview process in Germany.