Deutsche Bank Software Engineer candidates report an online or Codility coding screen, Java and Spring Boot technical rounds, a project or hiring-manager conversation, and HR. Timelines range from about two months to five.
$120K
Avg. Base Comp
$140K
Avg. Total Comp
3-4 rounds
Typical Rounds
2-5 months
Process Length
Candidates describe a Deutsche Bank Software Engineer interview built around Java and Spring Boot depth, not pure algorithm puzzles. Several people report a Codility or online coding stage first. Two walk-in candidates in Bangalore say some of those questions were Spring Boot-specific, and one had a caching problem.
Technical rounds then tend to cover core Java, OOP, collections, multithreading and thread safety, and SQL joins or indexing. Others were asked about microservices, Kafka (idempotency, offsets, replay, consumer lag), HTTP error handling and circuit breakers. DSA appears at an easy-to-medium level, such as finding a missing array element or writing a custom StringBuilder, so it is one part of the process and rarely the whole of it.
Project discussion carries real weight. Reports mention walking through your resume, why an application moved to microservices, production bugs, and how you would test APIs. One senior candidate also met a longer panel that touched on system design topics such as API gateways and load balancing. Practise explaining your own decisions out loud.
The process ends with a fitment or hiring-manager conversation and HR, sometimes including salary or start-date discussion. Outcomes are mixed: some candidates received offers, while others were rejected after strong-feeling interviews. Reported timelines run from about two months to nearly five, with long gaps for feedback and paperwork, so plan for a slow process. Formats also differ by location and level.
Synthesized from 35 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.
I interviewed at Deutsche Bank for a Software Engineer role, and the process felt surprisingly informal despite covering a lot of ground. My first round was technical, focused on DSA fundamentals, HashMaps, and Java OOPs concepts, along with some DBMS and SQL joins questions. There was no live coding — instead, my interviewer walked through my resume and asked me to explain my experience, then pivoted into technical questions based on what came up in conversation. The two interviewers were genuinely friendly and didn't push for trick answers; they seemed satisfied with partial explanations if I was on the right track.
The second round went deeper into system design and backend knowledge. We discussed my Spring Boot projects in detail, covered DBMS concepts and OS-level locking mechanisms, and explored how I'd architect Java-based systems. Behavioral questions were woven in naturally — things like how I manage time when juggling multiple priorities or how I ensure deliverables are met under pressure. One interviewer didn't even have his camera on, which honestly made it feel more relaxed than formal. They asked about HTTP methods, error handling, and circuit breaker patterns, all grounded in practical scenarios rather than theory.
One thing to know: the process is lengthy. After each round, expect a 3–4 week wait for feedback. The final offer letter took even longer for me — about three months — so the whole thing stretched to nearly five months from start to finish. That's something to prepare yourself for mentally if you're considering other opportunities in parallel. Overall, the interviews felt very skill-focused and relevant to the actual job, with no unnecessary gotchas.
Prep tip from this candidate
Focus on Spring Boot architecture, DBMS concepts, OS-level concurrency (locks), and practical HTTP knowledge including error handling and circuit breaker patterns. DSA and HashMaps came up, but Java OOPs and system design were emphasized more heavily than pure algorithm problems. Be ready to discuss your projects in depth and explain how you handle competing priorities — keep examples concrete and recent.
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 | |
| Maximum Profit | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Total Spent on Products | |
| Google Maps Improvement | |
| P-value to a Layman | |
| Cumulative Distribution | |
| Rectangle Overlap | |
| Top 3 Users |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an online assessment before any live interview. One mixed aptitude, two coding problems and DSA and database multiple-choice questions. Walk-in candidates in Bangalore describe a Codility test in which some questions were Spring Boot-specific, or focused on caching. Expect the format to vary by hiring channel and location.
Some candidates describe a first screen of roughly 30 to 45 minutes. Reported topics include core Java, Spring Boot and microservices basics, multithreading and a blocking queue implementation. One US-based AVP candidate also reports three Codility questions at this stage. It typically checks fundamentals before deeper rounds.
Candidates report one or two technical rounds lasting up to an hour or more. Reported questions include DSA at an easy-to-medium level, Java 8 streams, OOP, collections, concurrency and deadlocks, SQL joins and indexing, and Spring Boot beans, AOP and dependency injection. Later rounds may add Kafka and microservices scenarios. Some interviewers reportedly gave hints when candidates got stuck.
Several candidates report a round centered on their projects. Topics include why a system was split into microservices, production bugs, TDD and Agile experience, how to test APIs, and high-level design such as API gateways and load balancing. One candidate describes a 90-minute hiring-manager conversation. Prepare concrete examples of your own decisions.
Candidates typically report an HR conversation covering background, motivation, career plans, salary expectations and start date. Some were asked to submit documents afterward. Reported waits are long: one candidate cites 3-4 weeks for feedback after each round and nearly five months overall, another about three months, another almost two months. Some outcomes arrived without feedback.
