Deutsche Bank Software Engineer Interview Guide

Candidates describe the Deutsche Bank Software Engineer interview as a stack-heavy process more than a pure algorithm contest. Two candidates who attended walk-in drives report an online coding assessment on Codility as the first step. One says two of three questions were Spring Boot-specific rather than generic DSA, and the other's test centered on caching.

The technical rounds most often lean on core Java, Spring and project depth. Candidates mention threading and thread safety, collections, OOP, microservices, Kafka (configuration, idempotency, offsets, replay and consumer lag), Spring annotations, AOP and IoC, Oracle stored procedures, and SQL. Several say interviewers go through the resume closely, so be ready to explain what you owned, why design decisions were made, and what broke in production. One senior candidate found that even basic Java concepts were probed almost word for word, so precise definitions matter.

Coding difficulty is usually described as easy to medium. Reports of the process itself are mixed. One candidate describes a walk-in drive with a long wait before the test and same-day cuts after lunch. Another cleared every round, received a congratulatory email and a document request, waited almost two months, and was then told there would be no offer. One candidate who received an offer noted that even the so-called behavioral round turned practical, with questions such as how to test APIs. Most of these reports ended without an offer, so treat thorough Java fundamentals and well-rehearsed project stories as the safest preparation.