Deutsche Bank Business Analyst candidates describe a team panel, a hiring-manager talk, a loans data modeling round and an assessment-centre path, with questions on the role, CV, motivation and fit.
$75K
Avg. Base Comp
$90K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Deutsche Bank Business Analyst candidates describe processes that differ by team, so the best preparation is knowing the role well and being able to explain your own experience. One candidate expected a recruiter call but was put in front of a video panel of two team members, who asked for the difference between a Product Owner and a Business Analyst and what the candidate knew about the bank. Another spoke with a hiring manager who went through specific CV roles, current responsibilities, and why Deutsche Bank suited the candidate's values. That conversation included a case-style element with some technical content, but behavioral fit carried more weight. Neither of these two candidates received an offer.
Two other reports ended in offers. One candidate, who came through a recruitment agency, had a techno-functional round centred on loans data modeling, followed by a managerial round on team fit. Another described an online assessment, a division-specific video simulation with a written exercise, and an in-person day of three interviews that covered why that division, a conflict example and a skill not on the CV.
Prepare a concise Product Owner versus Business Analyst answer, walk through your CV role by role, and be ready to reason aloud about how entities relate in a lending system. Ask what format to expect, because one invitation gave almost no detail beyond the time and link.
Synthesized from 9 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 went through five rounds for the Business Analyst role, spread over several months. The process kicked off with resume screening and an HR round focused on my background and fit with the bank. What struck me most was how inconsistent the interview style felt across rounds—some interviewers were very structured and formal, while others felt more conversational and even threw curveballs at me.
The technical rounds were the toughest part. I had three coding interviews back-to-back, starting with basic object-oriented programming problems, then moving to a string manipulation question framed as a greedy algorithm problem. The third round surprised me because even though it was billed as a technical fit assessment, I was asked to solve a medium-difficulty problem involving log pattern processing—not exactly what I'd prepped for given the role title. Each round was about thirty minutes, and there was a gap of one to two months between them, which made it hard to stay in the zone.
Mixed into these technical rounds were behavioral and managerial interviews. One interviewer asked me what news article had interested me recently, which felt pretty random. Others dug into situational scenarios: how I'd handle a recurring error in a daily report, what I'd do if a senior manager asked for urgent data I wasn't confident about, and how I'd approach managing a new process with no documentation. There was also a case study on corporate banking products that tested my understanding of the business side.
The final round was another HR discussion wrapping things up. Overall, the process felt thorough in scope but lacked real depth or warmth—I didn't get much sense of the team culture or what growth would actually look like in the role. The rounds felt disconnected from each other, and the tone varied so much it was hard to gauge what they were really looking for.
Prep tip from this candidate
The coding rounds mix algorithmic problems with threading and concurrency concepts—drill greedy algorithms, string manipulation, and deadlock avoidance specifically. But don't neglect the behavioral side; the situational questions about handling errors, data accuracy concerns, and managing undocumented processes are just as critical, and they test judgment more than technical breadth.
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
How would you negotiate and resolve disagreements when a client rejects your proposed solution?
| Question | |
|---|---|
| Data Cleaning Experiences | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Cumulative Distribution | |
| Rolling Bank Transactions | |
| 500 Cards | |
| Find the Missing Number | |
| Employee Salaries | |
| Bagging vs Boosting | |
| Subscription Overlap | |
| Button AB Test | |
| Comments Histogram | |
| Prime to N | |
| Closest SAT Scores | |
| Top Three Salaries | |
| Size of Joins | |
| Total Spent on Products | |
| Monthly Customer Report | |
| Google Maps Improvement | |
| P-value to a Layman | |
| Paired Products | |
| Top 3 Users | |
| Third Purchase | |
| Slacking Employees Salaries | |
| Hurdles In Data Projects | |
| Experiment Validity | |
| Over 100 Dollars | |
| Minimum Change | |
| Recurring Character |
Synthesized from candidate reports. Individual experiences may vary.
One candidate expected a recruiter call but was invited to a video panel with two team members, with almost no advance detail. Another began with a hiring manager who explained the role and process. Questions covered the bank, CV responsibilities and motivation. Confirm the format before the call.
Reported questions included how a Product Owner differs from a Business Analyst, what the candidate knew about Deutsche Bank, what they did in specific CV roles and current responsibilities, and why the bank fit their experience and values. One candidate also described a case-style element with some technical content.
One offer recipient, who applied through a recruitment agency, described a techno-functional round on loans data modeling. The interviewers wanted to see how the candidate would structure and relate the parts of a lending system, and they cared about reasoning and domain understanding more than recited definitions.
The same agency candidate had a second, managerial round on team fit and collaboration. A different offer recipient described an online assessment, a division-specific video simulation with a written exercise, and an in-person day of three interviews, with questions on why the division, a conflict example and a skill not on the CV.
