The usual drill. An initial screening call with an HR person (who was very friendly). Then an assignment that you'd have to deliver within two days. Clear specs and you're given the freedom to use whatever tools you want (except for Bootstrap). The next step was an onsite interview. This was a problem solving on a whiteboard but packaged as a conversation. It was great though. It was very casual but very insightful.
The next step was a meeting with the CTO which was far from being friendly. First off, he was like 10 minutes late to the interview and didn't even apologize. He didn't seem to be interested in answering my questions, with a bored tone even. He even mentioned how they fire people who don't share their "values" (never, ever ever be proud of that or even mention it in an interview). Then I was given a "challenge" to solve. I have no idea how this could indicate whether or not you're a good front end developer. This wasn't a data structure/algorithm coding challenge by the way. Without mentioning the "tricks" he was doing throughout the interview to test your focus, etc etc (I would love to know if he had a psychology degree actually).
Everyone I had an interview with in Number26 mentioned how their employees work long hours and it was even considered as an indicator of determination and willingness to get things done (nope! you're burning your employees). I decided not to move forward with the interview process right after that.
Presenting use cases about architecture design and how I would solve them.
My opinion on some JS frameworks, what am I looking for in a company etc.
The following metrics were computed from 2 interview experiences for the N26 Frontend Engineer role in Berlin, Germany.
N26's interview process for their Frontend Engineer roles in Berlin, Germany is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for N26's Frontend Engineer interview process in Berlin, Germany.