N26 Vienna Office | Glassdoor

N26 Vienna (Austria)

N26 Vienna (Austria) Reviews

  • "A great place to be"

    StarStarStarStarStar
    • Work/Life Balance
    • Culture & Values
    • Diversity & Inclusion
    • Career Opportunities
    • Comp & Benefits
    • Senior Management
    Current Employee - Engineering Manager in Vienna (Austria)
    Current Employee - Engineering Manager in Vienna (Austria)
    Recommends
    Positive Outlook
    Approves of CEO

    I have been working at N26 full-time (Less than a year)

    Pros

    Great product, very helpful people, high quality engineers

    Cons

    Scattered information, can be hectic, in constant change

See All Reviews

N26 Vienna (Austria) Photos

N26 Vienna (Austria) employees haven't posted any photos yet.

Get this page going by posting a photo. It only takes a second, and your photos are anonymous.

Share a Photo

N26 Vienna (Austria) Jobs

N26 Vienna (Austria) Salaries

Salaries in € (EUR)
Average
Min
Max
1 employee salary or estimate
About €56k - €65k
€56k
€65k
About €56k - €65k
€56k
€65k
1 employee salary or estimate
About €47k - €55k
€47k
€55k
About €47k - €55k
€47k
€55k
1 employee salary or estimate
About €5k - €5k
€5k
€5k
About €5k - €5k
€5k
€5k

N26 Vienna (Austria) Interviews

Experience

Experience
50%
0%
50%

Getting an Interview

Getting an Interview
100%

Difficulty

2.5
Average

Difficulty

Hard
Average
Easy
  1.  

    Senior Android Engineer Interview

    Anonymous Interview Candidate in Vienna (Austria)
    No Offer
    Negative Experience
    Easy Interview

    Application

    I applied online. I interviewed at N26 (Vienna (Austria)) in November 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

    • Android app assignment with requirements given upfront.   1 Answer
See All Interviews