The process started when an HR representative contacted me via LinkedIn. Here’s how it went:

1. Initial HR Screening (Video Call) This was an introductory chat to discuss the company, my expectations, and alignment with the role.

2. Technical Test I received a test with three questions:

• An easy bug-finding task.
• Two medium-level problems requiring knowledge of data models and LeetCode-style problem-solving.

I passed this stage but faced a surprise: though all visible tests passed, the first question showed only 50% success after submission due to hidden tests. I had ended the session 40 mins early, missing the chance to debug. Despite this, I cleared the round.

1. Code Pairing Interview This involved solving a LeetCode problem with two engineers via screen sharing. The problem was easy, focusing on clear communication, alternative approaches, complexity analysis, and unit testing. They also asked collaboration-related questions. The session was smooth, and the interviewers were polite and supportive.

2. System Design Interview This round included detailed pipeline-related questions and a design task (e.g., login or account creation). Key points:

• Use a micro-services approach.
• Include non-functional requirements.
• Explain design choices clearly.

Though time was short, the interviewers extended it to allow me to finish. They were helpful, and the discussion was engaging.

1. Behavioural Interview The final stage was a behavioral interview with two HR managers. It involved a series of “Tell me about a time when…” questions covering:

• Communication and collaboration.
• Prioritisation shifts.
• Conflict resolution.
• Expectations of senior-level roles.

The questions were fairly standard, with no surprises. I felt the session went well.

After a 10-day silence, I received feedback stating that while my technical performance was strong, I didn’t pass the behavioural interview due to issues with my communication style. This was surprising since communication style is subjective and can vary based on personal preferences (e.g., tone or body language).

I reflected on this feedback and shared it with colleagues and peers, who assured me that they hadn’t faced issues with my style. While I couldn’t get further clarification from N26, I recognise that communication preferences differ across individuals and teams.

Positives

• Clear guidance and excellent documentation from HR.
• Polite and professional technical interviewers.

Negatives Vague and subjective feedback on communication style in the final round.

I hope N26 finds candidates whose communication style aligns with their expectations! 🙄🤷🏻‍♀️

LeetCode Easy and Medium Questions: The technical test involved solving easy and medium-level coding problems, similar to LeetCode. System Design: Focused on designing a specific part of a system, such as login functionality or account creation. Pipeline Questions: Included detailed and comprehensive pipeline-related questions. Behavioural Questions: “Tell me about a time when...” style questions exploring communication, collaboration, and problem-solving in various scenarios.