The process started with an initial 30 minutes screen interview with an N26 recruiter who asked about my professional experience and why I'd like to join the company.
All the interviews were handled professionally. I had to wait a little for the final decision since all the interviewers had to meet together, other than that it was a very respectful interview process.
How do you keep up to date with what's going on in the iOS world?
If you're starting a new project, how would you decide if you should use a third party dependency or not?
If you were starting a new project now, which architectural pattern would you choose?
Tell me about your experience in writing unit tests.
Have you ever maintained a legacy project in Obj-C? Did you have any problems?
Did you any change to work with continuous integration and continuous delivery?
Who do you mostly collaborate with? Are there other iOS engineers, Android engineers, designers, etc...
What's the hardest part about communicating with people from other disciplines (e.g. people who are not engineers)?
Why bundler?
Architectural patterns used in the project explanation
Project implementation related questions.
Give us an example of something you've implemented in your daily work after reading something interesting in the iOS communities online.
When making a group project, how do you make sure that everyone is on the right path?
How would you like to develop here as an engineer?
In terms of team structure, how is your daily work organised?
The following metrics were computed from 2 interview experiences for the N26 iOS Developer role in Berlin, Germany.
N26's interview process for their iOS Developer roles in Berlin, Germany is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for N26's iOS Developer interview process in Berlin, Germany.