Deutsche Bank Data Engineer interviews, as candidates describe them, combine SQL and coding questions with stakeholder and motivation conversations. Reports differ on round count and pace, so prepare for both technical and behavioral rounds.
$121K
Avg. Base Comp
$165K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Candidates describe a Deutsche Bank Data Engineer interview that mixes hands-on technical questions with behavioral conversations, and their experiences vary by team. Reports of the process are limited, so treat the details below as examples rather than a fixed format.
SQL window functions come up more than once. One candidate says the hiring manager round was heavily SQL-focused and drilled window functions. A candidate for an adjacent senior big data role was also asked about SQL analytical functions. Another reports a right-join question, so be ready to explain joins clearly as well as write advanced queries.
Coding questions appear to be basic and sometimes loosely related to pipeline work. Candidates mention finding duplicates in an array, reading a nested JSON structure, and HackerRank or LeetCode-style problems. One interview also included HTTP questions such as the difference between PUT and PATCH. Practice writing short, clean code aloud on a shared screen.
The behavioral side is just as important. Candidates mention stakeholder management, difficult stakeholders, why Deutsche Bank, and how they would succeed in the role. One candidate also faced conceptual machine learning questions about PCA and R-squared in VP rounds. Prepare concrete stakeholder stories and a specific answer for why this bank.
Expect uneven logistics. Candidates report slow scheduling, long gaps between stages, little feedback, and in some cases no reply after the final round. Staying organized and following up politely will help.
Synthesized from 5 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 process kicked off with an HR screening call where they walked through the role and asked standard questions about my background and fit. After that came the technical rounds—a live coding session focused on Python and SQL, where I worked through a problem on the spot. They were pretty rigorous about algorithmic thinking and database optimization, so I had to be sharp with my syntax and explain my approach clearly as I went.
Then I had conversations with team members and senior managers. These weren't just code-on-a-whiteboard; they were behavioral mixed with technical depth. They dug into my previous work experience, how I'd handled stakeholder communication, and how I'd approach tight deadlines when things got messy. One question that stuck with me was about validating fair value in a rates derivative scenario with limited market data—it was testing whether I could think through a real-world problem under uncertainty, not just regurgitate an algorithm.
The final round was with the hiring manager, which felt more conversational. They wanted to understand my product thinking and how I'd actually operate in their environment. The whole thing took a few weeks from start to finish, partly because of the approval cycle after negotiations wrapped up. Overall it was well-structured and professional—they had a clear sense of what they were looking for, and the interviews reflected that.
Prep tip from this candidate
Be ready for domain-specific problem-solving around financial instruments and derivatives—they don't just ask you to sort an array, they ask you to think through valuation challenges with incomplete data. Pair that with solid Python and SQL fundamentals, especially around optimization.
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 | |
| Data Cleaning Experiences | |
| LRU Cache 1 | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Comments Histogram | |
| Closest SAT Scores | |
| Top Three Salaries | |
| Cumulative Distribution | |
| Experiment Validity | |
| Find the Missing Number | |
| Maximum Profit | |
| String Shift | |
| Prime to N | |
| Like Tracker | |
| Last Transaction | |
| Attribution Rules | |
| Find the First Non-Repeating Character in a String | |
| Alphabet Sum | |
| Size of Joins | |
| Total Spent on Products | |
| Monthly Customer Report | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe an initial HR contact, though it differs by person. One was emailed for availability and then waited over a week. Another says the HR screen was followed by almost two months before the first interview. A third says no formal recruiter conversation was needed. Confirm scheduling proactively.
One candidate describes a conversational first technical call with a team member covering high-level skills and experience. Another describes a panel of interviewers, with one leaving early, who asked for a duplicate-finding function, SQL joins, and HTTP method differences. Expect basic fundamentals and be ready to explain your approach clearly.
A candidate reports that the hiring manager interview was intensely technical and SQL-heavy, with a focus on window functions. A candidate for an adjacent senior big data role also reports analytical function questions and nested JSON handling on a shared screen. Practice window functions and reading nested data structures in code.
One candidate describes three successive VP interviews that leaned behavioral and conceptual, including difficult stakeholders, PCA and R-squared. Another candidate reports questions on why Deutsche Bank, their experience, how to succeed in the role, and stakeholder management. Prepare specific examples and a clear motivation answer.
One candidate reports a face-to-face final interview at the office, after which they heard nothing despite two follow-up emails. Another reports little communication on progress across weeks. Candidates in these reports did not receive offers, so plan to follow up and keep other options moving while you wait.
