Very easy, specific to Java questions. No design rounds, or problem solving. Feels like anyone can clear given they just learn a few things about Java.The thing I felt the worst about the interview was the narrow-minded approach of the interview. The process hardly checks the candidate's whole potential and felt more like a rapid-fire of 10 questions.

The background I come from (which they simply ignored) we work on systems serving millions of customers, at least 20-30 times more than N26, and we have huge ownership giving us lots of exposure and experience on building scalable systems, and our interviews (and similar other companies) judge the candidates based on all different levels of skills like: logical problem solving, design/architecture, coding quality and cultural fit. N26 just lacked that.

I feel if this is the quality of interviews, the people there would also be similar. And they take the same interview for SDE, and senior SDE. They gave me SDE, just based on one rapid-fire round, and not by checking the full potential. It's still a hard choice to make if I should go there or no, since it doesn't feel right going by this process.I mentioned the same to them numerous times, but I don't think they understand that, because they are not exposed to our level of doing things.

I know of another friend, who gave the same coding round as mine, and I got accepted, and he got rejected (I reviewed his code later when he mentioned, and it was fine), the feedback my friend got was factually wrong from their side, something like (the time complexity is O(n) whereas a constant list has a time complexity of O(1)). This is their feedback from internal engineers, which says that they lack basic understandings, and also don't take proper feedback or communicate regarding this.

Advice: Don't do this. Understand where we come from. Respect the candidate's advice and listen to them if you really want to afford good candidates.

What all GCs are there in Java?