Deutsche Bank Software Engineer interview typically runs 3-5 rounds: HR, coding, technical, techno-managerial, and fitment. Timeline ranges from same day to about two months, and the process is often batch-style and highly variable.
$82K
Avg. Base Comp
$112K
Avg. Total Comp
3-5
Typical Rounds
2-8 weeks
Process Length
We’ve seen Deutsche Bank consistently favor candidates who can move comfortably between everyday engineering work and core technical fundamentals. Across experiences, the questions rarely stay in one lane: easy-to-medium coding shows up, but so do Java, Spring, SQL, OS, networking, and database basics, often with follow-ups that get very literal about how things work. Multiple candidates noted that the interviewers cared less about flashy algorithms and more about whether they could explain the mechanics behind their answers, especially in Java and backend contexts.
A recurring theme is that the company wants proof you’ve actually built and supported systems, not just listed tools on a resume. Candidates were asked to walk through projects in detail, defend design choices, and handle practical prompts like how to test APIs, how caching works, or how to reason about microservices, Kafka, Oracle stored procedures, and even React performance. We’ve also seen a few experiences where the discussion broadened into cloud and reliability topics such as Kubernetes, Terraform, load balancers, and thread safety, which tells us they value engineers who understand the surrounding system, not just the code snippet in front of them.
The non-obvious make-or-break factor here is precision. Several candidates described interviews that felt fair but rigid, with interviewers expecting exact definitions or very specific reasoning. That means success at Deutsche Bank often comes down to whether your explanations are crisp, technically grounded, and tied to real work. Our candidates report that the strongest signal is not just solving the problem, but showing you can justify it in a production-minded way.
Synthetized from 5 candidates 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 hardest part for me was realizing that the “behavioral” round was not really behavioral at all. My process was on Power Day, and the first two technical rounds felt pretty straightforward. Each round had two interviewers, and the coding questions stayed around easy to medium DSA level. I also got a few riddle-style questions, plus some core CS topics like OS, CN, DBMS, and SQL. They spent time going through my resume and the projects I had built, so it helped to be ready to explain what I actually did rather than just list technologies.
After those rounds, I moved into what was described as the final behavioral interview, but it was still with the same technical interviewers. That round was much more practical and project-focused than I expected. They asked questions based on real work, including how I would test APIs, and I had not prepared for that style of discussion. I ended up answering more from instinct than from a structured framework, which made that round feel weaker than the coding rounds. Another process I heard about was a more traditional sequence with a Spring Boot-related Codility round, core Java, system design, project fitment, and HR, so the exact structure can vary. In my case, the overall difficulty was still on the easier side, and I did receive an offer, but the main takeaway was to prepare for both coding and practical engineering questions tied to your resume and projects.
Prep tip from this candidate
Be ready for easy-to-medium DSA, but also drill OS, CN, DBMS, SQL, and Java/Core Java basics. Just as importantly, practice explaining your projects clearly and answering practical questions like how you would test APIs, since that came up in the final round.
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
Design a highly available, scalable Azure infrastructure using Terraform and Kubernetes.
| Question | |
|---|---|
| Client Solution Pushback | |
| LRU Cache 1 | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Maximum Profit | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Cumulative Distribution | |
| Hurdles In Data Projects | |
| Rectangle Overlap | |
| Monthly Customer Report | |
| Google Maps Improvement | |
| Slacking Employees Salaries | |
| Over-Budget Projects | |
| Top 3 Users | |
| Sum to N | |
| Over 100 Dollars |
Synthesized from candidate reports. Individual experiences may vary.
The process often begins with a brief HR step to confirm basic background and logistics. In some cases, this is followed by scheduling a longer technical interview, while in walk-in drives candidates may move directly into the assessment.
Candidates are commonly given a Codility test or online coding round before or alongside technical interviews. The questions are usually easy to medium level and often focus on practical stack knowledge such as Spring Boot, caching, or core coding fundamentals rather than only generic DSA.
This round is typically conducted by two interviewers and covers coding, core CS fundamentals, and resume/project deep-dives. Expect questions on Java, OOPs, OS, CN, DBMS, SQL, multithreading, microservices, Kafka, and sometimes a small coding exercise or riddle-style problem.
Some candidates move into a follow-up round that blends technical discussion with role fitment and practical engineering judgment. This stage can include project-based questions, system design or architecture basics, API testing, and discussion of how you would approach real work scenarios.
In some processes, there is a separate online fitment discussion with the hiring manager. This round tends to be conversational and positive, focusing on role alignment, experience, and whether your background matches the team’s needs.
After clearing the interviews, HR may ask for documents and other onboarding-related information. Candidates reported receiving congratulatory communication at this stage, but final offer release could still take time.