Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      N26

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur N26 | Offres d’emploi chez N26 | Salaires chez N26 | Avantages sociaux chez N26
      Entretiens chez N26Entretiens d’embauche pour Backend Engineer chez N26Entretien chez N26


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Backend Engineer

      1 juin 2026
      Candidat à l'entretien anonyme
      Berlin
      Aucune offre
      Expérience positive
      Entretien facile

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez N26 (Berlin) en mars 2026

      Entretien

      There were 3 technical rounds. First was a codility coding test. You can take it anytime within 7 days. Second was a Pair Coding Interview which involved live coding in front of 2 interviewers. Both interviewers were backend engineers but not seniors. Third was a design interview, where you have to draw a design on an online platform called Figma. In this one, your interviewers will be seniors.

      Questions d'entretien [1]

      Question 1

      (1) Codity questions (3 coding problems described below) : (1) You are given implementation of a function . This function, given a non-empty array A of N integers (sorted in non-decreasing order) and integer K, checks whether A contains numbers 1,2, ..., K (every number from 1 to K atleast once) and no other numbers. The goal of the exercise is to find and fix bug(s) in the implementation. (2) In 1 step, any element of a given array can be either increased or decreased by 1. Write a function that, given an array A of N integers, returns the minimum number of steps required to make all elements equal. (3) There are N arrows. The K-th arrow is rotated clockwise by A[K] degrees from an upward direction. In 1 move you can rotate 1 arrow clockwise or counter-clockwise by an arbitrary angle. What is the minimum sum of rotation angles needed to make all arrows point in the same direction. Write a function that, given an array A made of N integers, describing the initial rotation of each arrow, returns the minimum sum of rotation angles needed to make all arrows point in the same direction. (2) Coding interview: (1) code Leetcode easy level question. (3 Sum). (2) If a client sends invalid or unexpected input to a REST API, what should the API ideally return? (3) What are sealed interfaces? When / why do we use it? (4) if a rest api needs to return null to the client, should it return a simple null or return an object of type Optional ? When to use Optional? What are the benefits of using Optional? If the type of input from the client is not as expected, would you prefer to return a null, or an error message or an empty collection? (5) If a variable is of type Optional, do we still need to perform a null check before calling methods on it? What happens if we don't? Error or warning? (3) Design interview (1) Design a new user registration system, including the email verification/confirmation flow.
      Répondre à cette question

      Autres retours d’entretien d’embauche pour un poste comme Backend Engineer chez N26

      Entretien pour Backend Engineer

      31 août 2025
      Candidat à l'entretien anonyme
      Barcelone
      Aucune offre
      Expérience positive
      Entretien facile

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez N26 (Barcelone) en août 2025

      Entretien

      First, I had a call with a recruiter where we discussed the position, available opportunities, and my experience at a high level. We also went over the next steps in the process: 1. Coding task (algorithmic, on Codility) to complete during the week – 2 hours. 2. Live coding session (algorithmic, on Codility) with two engineers – 1 hour. 3. System design interview. 4. Team fit interview.

      Questions d'entretien [1]

      Question 1

      I was asked to resolve easy LeetCode algorithmic task.
      1 réponse
      2

      Entretien pour Backend Engineer

      4 févr. 2025
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé via la recommandation d'un employé. Le processus a pris 6 semaines. J'ai passé un entretien chez N26 en janv. 2025

      Entretien

      5 stages in total. First stage is a screening call with a recruiter with regular questions about previous experiences and expectations about the role. Second stage is a codility challenge that includes 3 problems involving DSA, I found this one to be harder than I thought with the problems involving DP but they only aim for 67% correctness. Third stage was a pair coding session with two engineers where I had to solve a small technical problem. The problem was of medium difficulty with follow-up questions on how to handle edge cases. Fourth stage was a System Design interview with two engineers. The problem presented wasn't super hard and was mainly focused on async communication between microservices and scalability. Fifth stage was behavioural interview with two engineering managers that involved a lot of "Tell me about a time when" questions. It was mainly focused on handling shifts in priorities and feedback culture. In the end they decided to move with another candidate because I didn't want to relocate to Berlin, even though I made it very clear from the first interview that this was not an option for me and they said it was ok not to relocate. Complete waste of time and totally unprofessional.

      Questions d'entretien [1]

      Question 1

      Tell me about a project you worked that you're most proud of.
      Répondre à cette question
      3