Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      N26

      Engaged employer

      About
      Reviews
      Pay and benefits
      Jobs
      Interviews
      Interviews
      Related searches: N26 reviews | N26 jobs | N26 salaries | N26 benefits
      N26 interviewsN26 Senior Android Engineer interviewsN26 interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Centre
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy and Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent posts

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" and logo are proprietary trademarks of Glassdoor LLC.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalised job recommendations and updates by starting your searches.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.

      Senior Android Engineer Interview

      15 Nov 2016
      Anonymous interview candidate
      Berlin

      Other Senior Android Engineer interview reviews for N26

      Senior Android Engineer Interview

      8 Apr 2025
      Anonymous interview candidate
      No offer
      Negative experience
      Easy interview

      Application

      No offer
      Negative experience
      Easy interview

      Application

      I applied through a recruiter. The process took 3 weeks. I interviewed at N26 (Berlin) in Sept 2016

      Interview

      Was contacted by a recruiter directly. Passed a screening, had to wait a week for an on-site interview date to be scheduled. Came to Berlin - confusing office setup, had to wait 10 minutes for someone to meet me. The guy interviewing me seemed disinterested in customers or the product, very opinionated (obsessive) about the emerging technologies. We talked for an hour and it became apparent to me that the guy doesn't care about anything else than just reading and implementing "hot new stuff", whether the project needs it or not. The lack of craftsmanship is actually showing in their app. We discussed all his hot new things on Android and his wish to move towards it, regardless of any rational reasoning or resource constraints. He did not listen to any counter arguments for his statements and seemed like someone I would not hire myself. After saying goodbye I learned that this guy was supposed to be my lead and that his team was supposed to be 3 people, him included. He sent me a take home test which took me 3 days to implement, did not reply to my questions and comments, did not communicate with me afterwards. I have sent the test to them and never got any feedback, besides "the position is already taken". After two more weeks I learned that the "lead" guy actually left his position at N26 and that they still have a couple of "Senior Android Engineer" positions open. Summing up, I would say that in my experience N26 has shown to be unprofessional, dishonest and disrespectful.

      Interview questions [1]

      Question 1

      How would you test a singleton?
      2 Answers

      I applied online. The process took 2 weeks. I interviewed at N26 in Mar 2025

      Interview

      Not the worst interview process I was involved in, but definitely with some weird aspects. The process consisted of several parts: - 30 min recruiter call - 45 min high-level discussion of my experience with 2 engineers, nothing too deep - 1.5 h live-coding, new feature implementation in an Android app with small architectural discussions. They messed up with giving me access to the code project template in advance, so instead of 1 hour I had at most 20 minutes to prepare everything for the inteview - 45 min discussion about my experience and work approaches with two EMs and a team lead (?) I passed all the stages before the last one spectacularly (or so I was told :D), but the last one was weird. I was a bit uncomfortable—I believe 3 interviewers is a bit too much. Besides the hiring manager (who might become my EM), there was another manager, plus some kind of tech/team lead. It was unclear who was leading the interview; it felt more like a cross-examination by two managers, and I had trouble communicating with the manager from another team. It seemed like they did not listen to me. Just one example of communication: "Do you have experience mentoring less experienced engineers?" "Well, in my current company, we don't hire junior devs, but in my previous role I mentored a couple of junior developers." "So, are you saying you don't really have experience in mentoring others?" I don't know if that's a language barrier (most of the interviewers throughout the process had quite heavy accents), prejudice, or something else—but I was rejected after this last stage. The rejection itself is some kind of a joke. The recruiter scheduled a call with me a couple of days after the last interview just to say that the feedback was negative, but they were going to discuss my candidacy once again. And then, after a couple more days, they scheduled another call just to say that, unfortunately, it's still a "no." I am quite sure at least one of the calls could've just been an email. And I don't understand the need to give hope that their decision may change. Just don't say anything—say you need two more days to evaluate me and give the final feedback. But maybe it's just me.

      Interview questions [1]

      Question 1

      Write a unit test for the UseCase you've just implemented
      Answer question
      1

      Senior Android Engineer Interview

      15 Mar 2024
      Anonymous interview candidate
      No offer
      Negative experience
      Easy interview

      Application

      I applied online. The process took 3 weeks. I interviewed at N26 in Jan 2024

      Interview

      First recruiter interview and it went well. After that they sent me coding challenge and it also went well. After that I had interview with 2 junior developers who even don't know about basic android platform . It was like a oral test. They had questions paper and asked one by one . It was very unprofessional . How junior developers can interview person for a senior position ? Then after the oral test they sent me a feedback it makes me laugh . I'm so glad that I don't wanna work for a company like that. They don't have any management to hire someone .

      Interview questions [1]

      Question 1

      Android related questions . But they even don't know new techniques and they rejected me by looking at their paper.
      Answer question
      3

      Senior Android Engineer Interview

      24 Nov 2020
      Anonymous interview candidate
      Vienna
      No offer
      Negative experience
      Easy interview

      Application

      I applied online. I interviewed at N26 (Vienna) in Nov 2020

      Interview

      Initial call with the recruiter about my previous and current experience. Take home android app task was given with 3 days deadline, small app scope. Requirements were outline clearly. I was rejected for: - Unused dependencies - Unused imports - A crash - Usage of separate live datas for error, loading and result - "Unused object" that was used to use @BindingMethod - Single module (yet multi module was considered as extra or good to have) I concurred on the crash. - Unused dependencies and import, it is absolutely ridiculous to raise the bar on it. Regarding "unused object" with @BindingMethod, I wish the developer reviewing the code brush up his/her skills on Databinding. - I used vanilla Dagger 2 for DI, multibinding with custom key for mapping (not just for ViewModels mapping, but for the use cases), @Qualifiers, @Scopes, @Component with Subcomponents, I also demonstrated interface dependencies binding using @Binds, also made up case where I can use @BindsInstance, worth mentioning is injecting parameterized interfaces, yet it was evaluated as BASIC. Basically, I used dagger thoroughly. - Demonstrated usage of SOLID principles with emphasis of interface segregation and single responsibility, usage of factories, composition and polymorphism. - Usage of separate live data for result (success), loading and error state, how is this bad thing? I suggest they low the bar on stupid things like "unused imports" or "unused dependencies", also ask the developer to study the android documentation on Databinding. Especially, the retention policy and target of the annotations, he/she apparently skipped that lesson and has no idea what he/she is talking about whatsoever.

      Interview questions [1]

      Question 1

      Android app assignment with requirements given upfront.
      2 Answers