Deutsche Bank Data Scientist interview typically runs 2 rounds: technical conversation and final round. The process usually takes a few weeks and is heavily focused on applied experience.
$116K
Avg. Base Comp
$140K
Avg. Total Comp
2
Typical Rounds
2-3 weeks
Process Length
Our candidates report that Deutsche Bank is far less interested in abstract machine learning fluency than in whether you can defend the decisions behind your work. One interview felt like a deep dive into past projects, with no live coding at all; the conversation kept circling back to why a particular model was chosen, what baseline it beat, and how the tradeoffs were weighed. That tells us the bar here is not just “can you build it,” but can you explain why this approach was the right business choice in a way that holds up under scrutiny.
A recurring theme is the emphasis on applied judgment. The interviewer pushed for details on implementation decisions and the reasoning behind them, which suggests they’re listening for candidates who can connect technical choices to real-world constraints and outcomes. We’ve seen this pattern in finance-facing teams before: they want people who can translate model behavior into something a stakeholder can trust. The non-obvious make-or-break factor here is whether your examples sound like polished summaries or like you truly understand the alternatives you rejected. Candidates who can clearly articulate why a simpler baseline was not enough tend to come across as much stronger in this process.
Synthetized from 1 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 first round was much more of a technical conversation about my past work than I expected. I went in thinking it would be a coding screen, but there was no live coding at all. Instead, the interviewer spent most of the time digging into projects I had worked on and how they connected to the role. A lot of the discussion centered on models I had implemented, why I chose them, and what made them a better fit than a more conventional baseline. They wanted details on the reasoning behind the model choice, not just a high-level summary, so I had to explain the tradeoffs and the implementation decisions pretty carefully.
What stood out was how in-depth the questions were about the actual work rather than generic machine learning knowledge. It felt like they were trying to understand whether I could justify model selection in a real business setting and communicate that clearly. I was told the process would be two rounds total, but I didn’t make it to the second round. Overall, it was less algorithmic than I expected and more focused on applied experience, so I’d prepare to talk through your projects end to end, especially why you picked one model over another and what benefit it gave compared with a simpler approach.
Prep tip from this candidate
Be ready to defend your model choices in detail, including why you picked them over a simpler baseline and what practical benefit they gave. Also prepare to walk through your past projects end to end, since the first round was centered on applied experience rather than live coding.
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
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| Employee Salaries | |
| Closest SAT Scores | |
| Top Three Salaries | |
| Subscription Overlap | |
| Experiment Validity | |
| Find the Missing Number | |
| Cumulative Distribution | |
| Compute Deviation | |
| Maximum Profit | |
| Prime to N | |
| String Shift | |
| Bagging vs Boosting | |
| Last Transaction | |
| 500 Cards | |
| Session Difference | |
| Rain in N Days | |
| Random SQL Sample | |
| Alphabet Sum | |
| Paired Products | |
| Bank Fraud Model | |
| Rectangle Overlap | |
| Swipe Precision | |
| Hurdles In Data Projects | |
| Unique Work Days | |
| Slacking Employees Salaries |
Synthesized from candidate reports. Individual experiences may vary.
The candidate was told the process would have two rounds total, which suggests an initial recruiter or coordination call before the technical interview. This stage would typically confirm interest, background, and basic fit for the Data Scientist role, though no detailed questions from this step were described in the experience.
The first round was a deep technical conversation centered on the candidate’s prior work rather than live coding or algorithm drills. The interviewer asked for detailed explanations of projects, model choices, tradeoffs, and why a given approach was better than a more conventional baseline.
A major part of the discussion focused on walking through past work end to end, including the reasoning behind implementation decisions and the business context for each model. The interviewer wanted more than a high-level summary and pressed for specifics on how the candidate justified model selection in a real-world setting.
The interviewer probed why certain models were chosen, what alternatives were considered, and what made the selected approach a better fit than simpler baselines. The emphasis was on practical judgment, explaining tradeoffs clearly, and showing that the candidate could communicate technical decisions to a business audience.