10 N26 Software Engineer (New Grad, Berlin) Interview Questions (2026)
N26's new-grad SWE loop in Berlin in 2026 is a recruiter screen, a take-home or HackerRank assessment, a technical phone interview, and a three to four round virtual onsite. As a digital bank, N26 emphasizes JVM stack fundamentals, distributed-systems thinking, and EU regulatory awareness. Berlin HQ values strong written communication and async collaboration across timezones.
By Alex Chen, Founder, InterviewChamp.AI · Last verified
Loop overview
Berlin new-grad timelines run 5-8 weeks in 2026. Flow: recruiter screen → take-home or OA (90 min) → 45-min technical phone screen → three to four virtual onsite rounds. Onsite is two coding rounds, one design conversation, and one behavioral. Visa sponsorship for non-EU candidates is supported via Germany's Blue Card (relatively fast, 4-8 weeks).
Behavioral (3)
Tell me about a time you wrote a detailed technical document.
Frequently askedOutline
N26 has a strong RFC/design-doc culture. Pick a real doc: design proposal, post-mortem, system explainer. Walk through: audience, structure, feedback you received, how you revised. Show that you write for readers.
Why N26? What about challenger banking interests you?
Frequently askedOutline
N26 was one of the first mobile-only banks in Europe. Tie one element (mobile-first UX, pan-European regulation, JVM-microservice architecture) to a personal interest. Generic answers underperform; specific tech or product references win.
Tell me about a time you worked across a timezone or language boundary.
Frequently askedOutline
N26 spans Berlin, Barcelona, Vienna, with engineering in multiple cities. English is the working language but cross-language collaboration is common. Bring specific async practices: written decision logs, overlap windows, recorded video updates. Generic answers underperform.
Coding (LeetCode patterns) (4)
Given a list of EU IBANs, validate them and group by country.
Frequently askedOutline
IBAN has a fixed format (2-letter country, 2 check digits, BBAN). Validate length per country, run mod-97 check on rearranged digits. Group by the 2-letter prefix. Walk through edge cases: invalid country, malformed format, failed checksum. Banking-domain knowledge is a plus.
Implement a function that returns true if two strings are anagrams.
Frequently askedOutline
Sort and compare (O(n log n)), or count characters (O(n)). Walk through both. Edge cases: empty strings, different lengths, mixed case. Mention Unicode considerations if time permits.
Given a binary tree of accounts (root = customer, children = sub-accounts like savings/spending), return all leaves with balance > $100.
Occasionally askedOutline
DFS or BFS, filter at leaf check. Walk through the leaf-detection (no children) and the filter condition. O(n) time, O(h) space. Edge cases: empty tree, all leaves balance < 100.
Implement a function that returns the longest sequence of consecutive transaction days for a user.
Occasionally askedOutline
Sort transaction dates, single pass tracking current run vs longest run. O(n log n) time. Or use a set + check if (day - 1) is in set for O(n) avg.
Technical (2)
Implement a function that processes a stream of card transactions and detects when a user spends more than 80% of their daily limit.
Frequently askedOutline
Per-user running total + reset on day boundary. On each transaction: add amount, check against limit. Discuss: timezone-aware day boundaries, race conditions on concurrent transactions, persistence between process restarts. Walk through one near-limit scenario.
How would you investigate a customer complaint that a transaction was double-charged?
Occasionally askedOutline
Pull all transactions for the customer in the time window. Compare authorization IDs and settlement IDs. Check for retry logic that may have fired twice. Verify with the card network. Communicate clearly with the customer about the resolution. Show structured investigation.
System / object-oriented design (1)
Design a system that handles 1 million card transactions per day across 8 EU countries.
Frequently askedOutline
Discuss: ingestion from card networks, per-country routing (for regulatory reasons), shared accounting layer, async fraud detection, push notification. Walk through one transaction's lifecycle. Mention GDPR data-residency at a high level.
N26 interview tips
- Java and Kotlin dominate backend. Familiarity with JVM concurrency primitives helps.
- EU-banking regulatory awareness signals fit (PSD2, GDPR, country-specific data residency).
- English is the working language. German is not required but learning a few words helps socially.
- Berlin office is hybrid. Visa sponsorship via Germany's Blue Card adds 4-8 weeks.
- Written communication matters. Practice writing clear design rationales — RFCs are part of daily work.
Frequently asked questions
How long is N26's SWE new-grad interview process in Berlin in 2026?
Most reports show 5-8 weeks from OA to offer.
Does N26 Berlin sponsor work visas?
Yes for non-EU candidates via Germany's Blue Card. Processing adds 4-8 weeks. Confirm with your recruiter.
Does N26 ask system design for new-grad SWE?
Yes, one round is a system design conversation. New-grads show framing and tradeoff awareness.
What languages does N26 use?
Java and Kotlin dominate backend. Some Python in data services. TypeScript for web. Swift/Kotlin for mobile. The interview accepts any language.
Is N26 Berlin remote-friendly?
Hybrid is the norm. Some fully-remote roles within the EU. Confirm with your recruiter.
Practice these live with InterviewChamp.AI
Real-time AI interview assistant that listens to your loop and helps you structure answers under pressure.
Practice these live with InterviewChamp.AI →