Deutsche Bank Software Engineer candidates report Java- and Spring-heavy interviews, practical project discussions, and coding that ranges from stack-specific assessments to easier DSA questions.
$128K
Avg. Base Comp
$157K
Avg. Total Comp
3-4 rounds
Typical Rounds
2-8 weeks
Process Length
Deutsche Bank Software Engineer interviews in the available reports lean toward practical backend engineering rather than only difficult algorithm drills. Candidates describe Codility assessments with Spring Boot or caching prompts, easy-to-medium DSA questions, and discussions of Core Java, OOP, threading, collections, SQL, and database queries. One candidate’s one-hour interview also went directly into Spring Boot concepts such as annotations, AOP, and IoC, plus Kafka configuration, idempotency, replay, offsets, auto-commit, and consumer lag.
Your project narrative is central preparation. Reported interviewers asked why an application moved to microservices, which domain the candidate owned, what challenges occurred, and how production bugs were handled. Other reports mention resume-based questions, API testing, practical OOP/database/API discussion, and basic distributed-systems topics. Prepare to explain concrete design choices and tradeoffs from your own work, then connect them to the Java and backend technologies on your resume.
The reports show different hiring formats. One Power Day account describes two technical rounds followed by a final practical, project-focused conversation; another walk-in account reports a Codility test, technical and techno-managerial interviews, then an online fitment discussion. One candidate who reported a full duration described a process of almost two months.
Synthesized from 6 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Deutsche Bank process.
The one-hour interview began with an introduction, followed by:
Questions included:
Prep tip from this candidate
Prepare a concise project walkthrough covering microservices decisions, ownership, challenges, and production bugs. Review Core Java, Spring Boot fundamentals, and Kafka configuration, idempotency, offsets, replay, auto-commit, and consumer lag.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Deutsche Bank
Implement Dijkstra's shortest path algorithm for a given graph with a known source node.
| Question | |
|---|---|
| Text Editor With OOP | |
| Azure Kubernetes Infrastructure | |
| Client Solution Pushback | |
| LRU Cache 1 | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| String Shift | |
| Bagging vs Boosting | |
| Comments Histogram | |
| Prime to N | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Maximum Profit | |
| Find the First Non-Repeating Character in a String | |
| Google Maps Improvement | |
| Cumulative Distribution | |
| P-value to a Layman | |
| Rectangle Overlap | |
| Top 3 Users | |
| Over-Budget Projects | |
| Slacking Employees Salaries |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a Codility assessment in some walk-in processes. Reported prompts included caching and Spring Boot-specific questions, while another candidate described easy-to-medium DSA and occasional riddle-style questions. The assessment emphasis may therefore depend on the hiring flow and team.
Technical conversations reportedly covered Core Java, threading, collections, OOP, Spring Boot annotations/AOP/IoC, SQL, and database queries. Candidates also encountered practical backend topics such as Kafka configuration, idempotency, offsets, replay, auto-commit, and consumer lag.
Candidates report detailed questions about projects and ownership: why a system became microservices, the domain they owned, production bugs, and delivery challenges. Practical questions may also cover API testing, OOP, automation, or basic distributed-systems ideas tied to prior experience.
One candidate described a final conversation that was labeled behavioral but remained technical and project-focused. Another reported a later online fitment discussion with a hiring manager after same-day technical stages. Treat this as a possible practical discussion rather than assuming a purely behavioral round.
