Jobra
🐞Step 1 of Jobra:AI Debugging Rounds
DSA+AIPreparing you for both.
JOBRA · AI DEBUG ROUND (PREVIEW)sum.cpp
// buggy snippet
int total(vector<int>& a, int n) {
    int sum = 0;
    for (int i = 0; i <= n; i++) { // 🐞        sum += a[i];
    }
    return sum;
}
A real codebase. A real bug. You + AI.

Jobra drops you into a broken repo. Find it, fix it, ship it. AI helps you debug like on the job.

Prompt:Correct the loop condition
Tap 'Let Jobra fix it' below to simulate AI debugging...

Deutsche Bank Software Engineer Interview Guide

33 min read

How the Deutsche Bank software engineer interview works: HackerEarth test, two technical rounds, ProFit and HR, from real candidate experiences in India.

In this article
On this page

How to Crack Deutsche Bank: The Software Engineer Interview, From Real Experiences

Last updated November 20, 2026 · 27 min read · For TDI and summer interns, Graduate Analysts and campus SDE candidates in technology

Built by the Codinzhub team. This guide is built from Deutsche Bank software engineering interview experiences that candidates shared, including experiences and online assessment questions on Codinzhub. The process changes by campus, track and year, so treat this as a map, not a promise.

The 30-second version. Deutsche Bank hires entry-level technology graduates in India through campus drives. You take an online test on HackerEarth, usually 3 coding questions in 90 minutes, and a small shortlist goes to one interview day. Full-time candidates face two technical interviews of usually 30 to 60 minutes, then a professional fitment (ProFit) round of usually 20 to 40 minutes and an HR round of 15 to 30 minutes; interns have one technical interview. The technical rounds dig into your projects, then mix short DSA questions, sometimes on paper, with OOP, DBMS, OS and puzzles. The last two rounds are mostly stories and "why Deutsche Bank", and they cut candidates too. Results often came the same night. The habit that matters most: explain every project choice and every line of code out loud.

What this guide is, and what it is not

This guide is built from 22 candidate records of Deutsche Bank's entry-level software engineering hiring: 4 experiences shared on Codinzhub, 12 public write-ups, and 6 sets of online assessment questions shared on Codinzhub. It also draws on Deutsche Bank's official careers pages. Most experiences are from 2023 and 2024 Indian campus drives for Graduate Analyst, SDE and intern roles in technology; one experience and two OA question sets are from 2026.

It is:

  • A map of the process, stage by stage, as candidates described it
  • The question patterns that keep coming back, and the follow-ups to expect
  • A six-week plan and practice problems matched to those patterns

It is not:

  • A list of leaked questions or a promise of what you will be asked
  • An official description of Deutsche Bank's process
  • An offer rate. Outcomes in candidate posts are self-reported and are not a statistical sample.

Important things to know before you start

These Deutsche Bank facts change how you should prepare.

It is a campus process, decided in one day. Deutsche Bank says Indian applicants apply through their campus and interview on campus. In 6 reports every interview round ran on one day with the result that night, so you need energy for four rounds back to back.

Two of the four rounds are mostly non-coding, and they still cut people. The professional fitment (ProFit) round cut 16 candidates to 12 and 6 to 4 in two drives, and one 2024 candidate who reached HR was not selected. Prepare stories and a real answer to "why Deutsche Bank?" as seriously as DSA.

Expect paper and puzzles. Code was written on paper in at least two on-campus rounds, with no way to run it, and a puzzle came up in 9 of 16 experiences. Practise writing clean code by hand and reasoning aloud.

Round-by-round breakdown

Candidates described five stages: a campus application, an online coding test that sets the shortlist, an interview day with two technical rounds (one for interns), a professional fitment round and an HR round, and a result that usually came the same night.

Stage 1: Application, where candidates applied

Almost every record is an Indian campus drive: 15 of 16 candidate experiences. Deutsche Bank's careers site says Indian students apply through their campus, not the general portal, and that partner campuses are hired between July and December, with interviews on campus.

ChannelWhat candidates said
On-campus driveThe main route. Three reports say one visit hired interns and full-time graduates together. Eligibility varied: all branches with no GPA cut-off (a 2023 intern drive); CS, IT, AI and data science, and electronics (2023); B.E. or B.Tech of any branch plus MCA, for Pune or Bangalore (2023).
Off-campusOne 2023 candidate applied off campus and got an international offer after two 60-minute technical interviews.

What helped. Candidates credited deployed projects they could show live, full-stack projects they understood end to end, and a competitive programming profile.

Stage 2: Shortlisting, how candidates moved forward

There is no recruiter screen in the data. The online test decides who is interviewed, and a pre-placement talk comes before the interview day in 4 reports.

  1. The online test score. Shortlists were small: 44 students at one 2023 drive (two reports from the same campus), 42 at another, 55 of about 3,000 in one undated report, and 14 at a 2023 intern drive where, the candidate said, only those with every MCQ and coding question correct went through. One 2023 candidate guessed that CGPA also counted, because many of those shortlisted had 8.5 or above.
  2. Results and scheduling. The shortlist came 2 to 3 days after the test in one report, 4 days in two, and about a week in one. Interviews followed the test by 4 to 11 days in the three reports that give both dates.
  3. Pre-placement talk (PPT). Four reports describe a talk by the bank's team after the test, in college or online, covering work culture and compensation. One candidate warned that a later interview round was "purely based on" this talk; later rounds asked about the bank's values in 2 reports and what it does in 3.

What candidates advised. Attend the pre-placement talk carefully, note the bank's values, and prepare your own questions for each interviewer.

Stage 3: Online assessment

Campus candidates took an online coding test first (12 of 16 experiences describe it). There is no phone screen: the test score leads straight to the interview day.

Online coding assessment

How it works. The test ran on HackerEarth in 7 of 7 reports that name a platform, for 90 minutes in 9 of 10 reports giving a length, with 3 coding questions in 12 of 15 reports giving a count. Two reports say points rose by question: 20 for the first, 50 each for the second and third. Intern-season tests differed: one 2023 intern test had 2 coding questions plus 20 MCQs on operating systems, DBMS, networks and OOP, and another 2023 test had 2 coding questions plus 10 MCQs in 120 minutes. Partial scores still got three candidates through.

At a glance

  • Length: 90 minutes (9 of 10 reports); 120 minutes in one 2023 test with MCQs
  • Questions: 3 coding questions (12 of 15); 2 coding questions in three intern-season or mixed drives
  • What was asked: greedy, binary search, dynamic programming, math and string problems; Codinzhub pages add array, string, tree and graph problems
  • Most common: No single repeated question

Difficulty labels ranged from one easy and two medium (two reports) to medium-hard; in one 2023 drive, no one at the college fully solved the hard string question.

QuestionWhat it testsLevel
Validate an IP addressString parsing and validationGraduate Analyst
Collecting coins: each hero beats every monster of power at most its ownSorting, prefix sums, binary searchGraduate Analyst
Largest number up to 1e9 that divides at least K array elementsDivisor countingGraduate Analyst
Binary-search-on-answer problem like Koko Eating BananasBinary search on the answerGraduate Analyst
Grid path DP problem related to Rat in a MazeGrid dynamic programmingGraduate Analyst
Variation of the next greater element problemMonotonic stackIntern
Core CS MCQs on operating systems, DBMS, networks and OOPCS fundamentalsIntern

OA questions shared on Codinzhub.

QuestionDriveTopic
Minimum operations to convert an array into a permutationIIT (BHU) Varanasi, November 2026Arrays
Maximum subarray sum with equal first and last elementsIIT (BHU) Varanasi, November 2026Arrays
Minimum number of cars to turn backIIT Guwahati, October 2026Not reported
Count anagrams without adjacent equal charactersIIT Guwahati, October 2026Strings
Largest perfect binary subtreeIIT (BHU) VaranasiTrees
Vertices stop disappearingMNNIT AllahabadGraphs

Codinzhub has 16 Deutsche Bank OA question pages from six college sittings; see all of them in the question bank.

Stage 4: The interview loop

Deutsche Bank says interviews in India take place on campus, and 6 reports describe every round on a single day. Most rounds cut candidates. Full-time candidates (Graduate Analyst or SDE) had two technical interviews, a professional fitment round and an HR round in the 10 reports describing a full campus loop. Interns had one technical interview, then the fitment and HR rounds (3 intern reports and one unlabelled report); one intern noted that seniors at the same drive had one more technical round. Funnels show the cuts: 42 to 30 to 16 to 12 at one 2023 drive, and 44 to 27 to 22 to 18 at another.

What a 45-minute first technical interview looks like

TimeWhat usually happensWhat to do
0–5 minIntroduction; some interviewers ask your strongest areaEnd on the project and topic you know best; they steer from it.
5–15 minProject deep dive: design, database choice, "why this stack"Have a diagram and one trade-off ready for each project.
15–30 min1 to 3 DSA questions, sometimes on paperState the brute force, then improve it, and give the complexity.
30–42 minOOP, DBMS and SQL, OS or networks theory; sometimes a puzzleOne-line definition, then a real-life example.
42–45 min"Do you have any questions?"Ask something specific about the team or the bank's technology.

Seven reports describe these parts, in varying order.

Technical interview 1

At a glance

  • Length: 30 to 60 minutes (10 of 11 reports); about 2 hours in one 2023 report
  • Questions: 1 to 5 short DSA questions plus CS theory, after a project discussion
  • What was asked: projects, OOP, DBMS and SQL, linked lists and sorting, OS and networks; a puzzle in 7 of 16
  • Most common: Explain the four OOP pillars with real-life examples, and ACID properties (6 of 16 candidates each)

The project discussion came up in most first rounds (13 of 16), and it went deep: one 2026 candidate was asked to "sell" their project as if the interviewer were an investor, and others had to draw its design or ER diagram. Code was written on paper in at least two on-campus rounds, and run on the candidate's own machine in one online intern round.

QuestionFollow-upLevel
Walk through your project: design, stack choices and whyWhy this database and not another? Draw the designGraduate Analyst, SDE, Off-campus SWE
Explain the four OOP pillars with real-life examplesTypes of polymorphism with examplesGraduate Analyst, SDE, Intern
ACID properties in DBMSNot reportedGraduate Analyst, Intern
SQL vs NoSQL, and why you used NoSQL in your projectWhich is faster, SQL or MongoDB?Graduate Analyst
Polymorphism: overloading vs overridingNot reportedGraduate Analyst, SDE, Intern
Write a sorting algorithm (merge sort), then compare it with quick sortWhich is the best sorting method?Graduate Analyst, Intern
Dijkstra's algorithm: code it and say where it failsReal-life uses of shortest pathGraduate Analyst, SDE
Reverse a linked listNot reportedGraduate Analyst, Intern

Technical interview 2

At a glance

  • Length: 30 to 60 minutes (7 of 9 reports); 15 to 20 minutes for one candidate after a strong first round, 65 to 70 minutes for another
  • Questions: 1 to 3 coding questions (7 of 11 reports), plus theory and more projects
  • What was asked: dynamic programming, trees and graphs, SQL and database design, networks and OS
  • Most common: No single repeated coding question; why indexing is used came up in 3 reports

This round had the longer DP, tree and graph problems in 5 of 11 reports. Interviewers pushed for the optimal answer: one took a candidate from brute force to DFS and BFS to a linear solution with hints, and another wanted the most optimised longest palindromic subsequence. Interviewers had the first round's feedback in two reports.

QuestionFollow-upLevel
Bottom view of a binary treeNot reportedGraduate Analyst
Longest palindromic subsequence, optimisedNot reportedGraduate Analyst
House robber: maximise loot without robbing adjacent housesNot reportedGraduate Analyst
Jump Game III, then a linear solutionOptimise to a linear solutionGraduate Analyst
Group anagramsNot reportedOff-campus SWE
Search in a sorted and rotated arrayNot reportedNot reported
Design a database for a college library, then query itOdd rows without a student_id columnSDE
Why use indexing in a database?Not reportedGraduate Analyst

Professional fitment (ProFit) round

At a glance

  • Length: 20 to 40 minutes (5 of 8 reports); 10 to 15 minutes in one 2024 report, 50 and 60 minutes in two 2023 reports
  • Questions: a project walkthrough, then situational, team and background questions
  • Themes: projects, team conflict, deadlines and dependencies, family background, higher studies, motivation

Three candidates called it a technical-plus-HR round that checks communication and confidence. It cut 16 candidates to 12 and 6 to 4 in two funnels. It can turn technical: an OOP calculator on paper, heap sort, or branch questions for electronics students.

Reported questions.

  • Show and explain your projects, then say what you would improve (9 of 13 candidates), then which stack you would pick if you had funding
  • Tell me about your family background and your parents' work (5)
  • The hardest challenge or setback in a project, and how you handled it (5)
  • Hobbies and interests outside academics, and how you keep at them (4)
  • Your team cannot start until team B delivers, and team B misses the deadline
  • First day at work: the person you must submit to is on leave
  • Choose between a valuable client and project accuracy
  • Design a calculator using OOP on paper, then add percentage and mod

HR round

At a glance

  • Length: 15 to 30 minutes (7 of 8 reports); 5 to 10 minutes in one
  • Questions: introduction and background, motivation, then team or ethics scenarios
  • Most common: Why Deutsche Bank? (6 of 16 candidates, in this round or the fitment round)

Two candidates had it online; one HR interviewer had feedback from every earlier round.

Reported questions.

  • Why Deutsche Bank? (6)
  • Tell me about yourself, beyond what is on your resume (6), then how your people skills are good
  • What does Deutsche Bank do? (3)
  • How have you handled a conflict or disagreement in your team? (3)
  • You find a critical bug the evening before a deadline: what do you do?
  • Two friends at rival firms approach the same client
  • Taking the blame for someone else's mistake
  • Your view on AI and what it means for jobs in five years

See every fitment and HR prompt in the question bank.

Stage 5: Same-day result and offer

Decision. There is no hiring committee or team match in the data. In 6 reports every round ran on one day and the result came that evening, as late as 8:30 pm in one report and after 9:30 pm in another. One candidate said the final list weighed all four rounds together.

How many got through. Final selections were small: 18 at one 2023 drive, 12 at another, and 4 summer interns at a third.

Offer. One 2023 off-campus candidate received an international offer. Joining dates, team allocation and pay are not reported consistently enough to include.

The Codinzhub Next-Round Playbook

Candidates who moved forward knew their projects cold, explained their code aloud, and took the last two rounds seriously.

To get past application and shortlisting

  • Watch your placement cell: Deutsche Bank says Indian hiring runs through partner campuses, July to December.
  • Deploy your projects so you can show them live; one fitment interviewer asked to see them on his phone.
  • Attend the pre-placement talk and note the bank's values; one candidate said a later round was based on it.

To get past the online assessment

  • Bank partial credit: three candidates passed only some test cases on the third question and still got interviews.
  • Expect binary search hidden in a story: two 2023 drives had one.
  • In intern tests with MCQs, do the coding first, then the MCQs carefully: one 2023 shortlist needed every answer right.

To get past technical interview 1

  • Lead your introduction toward your strongest area; one interviewer asked for it directly, another for your favourite data structure.
  • Write clean code on paper: say the brute force, then improve it, and give the complexity.
  • Answer theory with a definition and a real-life example; real-life uses of data structures came up for 3 candidates.

To get past technical interview 2

  • Push past the first working answer; interviewers asked for the most optimised solution, and one gave hints toward a linear one.
  • Revise database scaling and design: indexing came up in 3 reports, CAP or sharding in 3, and one candidate designed a library database.

To get past the professional fitment round

  • Have team stories for conflict, a missed dependency and a credit-taking teammate.
  • Stay calm when challenged: one interviewer staged "your skills do not fit this role" to see how the candidate argued.

To get past the HR round

  • Have a specific "why Deutsche Bank" and "what does the bank do" answer ready.
  • Be honest: one candidate warned that HR interviewers notice bluffing.

To get through the result

  • Keep your energy for a long day: results came that night in 6 reports.

How the loop differs by level

Almost every record is an entry-level campus hire, so "level" means the track: intern or full-time graduate. Full-time candidates get one more technical interview. No record at any level had a system design round.

LevelWhat candidates describe
TDI or summer internAn OA with 2 coding questions in two 2023 intern tests (one added 20 MCQs), then one technical interview of about 45 to 60 minutes, then the fitment and HR rounds. Examples: implement a sort on paper, insert array elements into a BST, Kadane's algorithm, reverse a linked list, virtual memory and threads. One intern noted that no banking knowledge was expected. Based on 3 reports.
Graduate Analyst or SDE (full time)An OA with 3 coding questions in 90 minutes, then two technical interviews, the fitment round and HR, on one day. Round 1 leans on theory (OOP pillars, ACID, SQL vs NoSQL, Dijkstra); round 2 on longer DSA problems (bottom view of a tree, longest palindromic subsequence, house robber, Jump Game III). The closest thing to design was an OOP calculator on paper, a library database and CAP or sharding questions. Based on 9 reports.
Off-campus (international offer)Two 60-minute technical interviews, two interviewers in the first: projects and machine learning concepts, valid parentheses, group anagrams, an integer palindrome without extra space, and questions on investment and banking. Based on one 2023 report.

No counted record covers experienced (lateral) hires.

Most-asked topics

Across the 16 candidate experiences, the interviews tested CS fundamentals as much as DSA: your projects, OOP and databases came up as often as any coding pattern.

TopicWhat it meansSeen inReported examples
Projects and resumeYour own projects: design, stack choices, what you would change16 of 16 reportsWalk through your project; show and explain your projects, then say what you would improve
Arrays, linked lists, stacks, sorting and searchingClassic data-structure basics and sorting or binary search13 of 16 reportsWrite merge sort; reverse a linked list; Kadane's algorithm; collecting coins
DBMS theory and SQL queriesTransactions, normalization, NoSQL, indexing, plus written queries13 of 16 reportsACID properties; SQL vs NoSQL; fetch alternate rows; design a library database
OOP theory and class designThe four pillars, polymorphism, inheritance problems, a small class design13 of 16 reportsOOP pillars with real-life examples; overloading vs overriding; OOP calculator
Dynamic programming, trees and graphsRecursion with memory, tree traversals, shortest paths12 of 16 reportsDijkstra and where it fails; bottom view of a binary tree; house robber
Operating systems and networksScheduling, memory, deadlocks, OSI layers, network devices10 of 16 reportsRound robin vs SJF; paging vs segmentation; OSI vs TCP/IP
PuzzlesClassic logic and arithmetic puzzles, asked in any round9 of 16 reports25 horses; clock angle at 10:15; water jugs

The puzzle count includes puzzles candidates did not name.

The question patterns that keep coming back

Most questions fall into seven patterns. The Deutsche Bank style is breadth: one round can move from your project to a linked list, to ACID, to a puzzle.

1. Projects and resume deep dives

Project questions appear in 16 of 16 experiences: in the first technical round in 13, and in the fitment round in 9 of 13. Expect "why this database?", a design or ER diagram drawn on the spot, and in one 2026 interview, "sell it to me as an investor". How to prepare: for each project, know the problem, your part, the architecture, why each tool beat its alternative, and one thing you would change.

Reported examples. Walk through your project and its stack choices; draw your project's ER diagram; why Node.js; if you had funding, which stack would you choose?

2. Arrays, linked lists, stacks, sorting and searching

13 of 16 reports. These are the short coding questions of the first round, and the bulk of the OA. How to choose: "in place" or "without extra space" means two pointers; "find the middle" or "detect a loop" means slow and fast pointers; matching brackets means a stack; "minimise the maximum" or "smallest speed that works" means binary search on the answer.

Reported examples. Write merge sort, then compare it with quick sort; reverse a linked list; detect a loop and where it starts; odd and even elements without extra space; a Koko Eating Bananas-style OA question.

3. DBMS theory and SQL queries

13 of 16 reports. ACID properties were among the most repeated questions (6 candidates), with SQL vs NoSQL close behind (5). How to answer: a definition, then an example from your own project's database; for queries, "per group" means GROUP BY, "alternate rows" means a row number with MOD, and "highest" means ORDER BY with LIMIT or a MAX subquery.

Reported examples. ACID properties; SQL vs NoSQL; normalization; why indexing is used; students per state from two tables; design a college library database.

4. OOP theory and class design

13 of 16 reports. Explaining the four OOP pillars with real-life examples was asked of 6 candidates. How to answer: a one-line definition, a real-life example, then a short code sketch; know overloading vs overriding and the diamond problem.

Reported examples. OOP pillars with examples; overloading vs overriding; friend class; diamond problem; design a calculator with OOP on paper, then add percentage and mod.

5. Dynamic programming, trees and graphs

12 of 16 reports, across both technical rounds and the OA. How to choose: "maximise without taking neighbours" is 1D DP; "palindromic subsequence" is interval DP; "view from below" is a level-order walk with horizontal distances; weighted shortest path is Dijkstra, which fails with negative edges.

Reported examples. Dijkstra and where it fails; bottom view of a binary tree; longest palindromic subsequence; house robber; Jump Game III.

6. Operating systems and networks

10 of 16 reports, as theory in both technical rounds. How to answer: compare two things on one axis at a time.

Reported examples. Round robin vs preemptive SJF; paging vs segmentation; deadlocks; OSI vs TCP/IP; ARP and MAC; LAN vs WAN.

7. Puzzles

9 of 16 reports, in any round. How to answer: say your reasoning aloud, try small cases, and give a partial approach if you are stuck; one candidate offered several creative ideas to an unfamiliar puzzle and still moved on.

Reported examples. Fastest 3 of 25 horses; clock angle at 10:15; water jugs of 4 and 5 litres; mislabelled jars; four people on a rickety bridge.

Preparing for the professional fitment and HR rounds

The fitment round digs into your projects and how you work in a team; HR asks why the bank, then about you. Both can end your day (see Stage 4).

Build your story bank. Prepare six to eight real stories, each under two minutes, covering the themes candidates were asked about:

ThemeReported prompt (paraphrased)Follow-up to expect
ProjectsShow and explain your projects"Which stack would you choose if you got funding?"
Team conflictA conflict or disagreement in your team; an angry senior colleagueNot reported
Dependencies and deadlinesYour team is blocked when team B misses its deadlineNot reported
Ownership under pressureA critical bug the evening before a deadline; a teammate ill on presentation dayNot reported
FairnessA teammate does less but takes the credit"What if it happened to you in industry?"
MotivationWhy Deutsche Bank? Why a bank or finance company?"What does Deutsche Bank do?"
BackgroundFamily background and parents' work; hobbies"Any plans for higher studies?"

Structure each story. The situation in one line, what you did (say "I"), the result, and what you would do differently. Use your own experiences: in one report the fitment interviewer was a solution architect with 15+ years, and the HR interviewer had notes from every earlier round.

Know the bank. "Why Deutsche Bank?" came up for 6 of 16 candidates, "what does it do?" for 3, and its values for 2. One candidate said a round was based on the pre-placement talk, and another advised talking about learning and growing.

A six-week plan

The plan follows the patterns above, most common first, and ends with mocks that match the real day. Plan on two to three focused hours a day.

  1. Week 1: Projects, OOP and DBMS. For each project: architecture, why each tool, one change you would make, an ER diagram. Then the OOP pillars with real-life examples, overloading vs overriding, the diamond problem, ACID, normalization, SQL vs NoSQL and indexing. Habit: answer every theory question as a definition plus an example from your project.
  2. Week 2: Arrays, linked lists, stacks and sorting. Reverse a linked list, find the middle, detect a loop and its start, odd and even elements in place, Kadane's algorithm, valid parentheses, merge sort and quick sort from scratch. Habit: write each solution on paper first and state its complexity.
  3. Week 3: SQL queries and searching. Joins with GROUP BY, highest salary, alternate rows, a schema of your own design; binary search on the answer, rotated-array search, greedy problems. Habit: write the query by hand before running it.
  4. Week 4: Dynamic programming, trees and graphs. House robber, longest palindromic subsequence, grid path DP, BST insertion, bottom view of a tree, BFS and DFS on a grid, Dijkstra and where it fails. Habit: say what each recursive call returns before coding it.
  5. Week 5: Operating systems, networks and puzzles. CPU scheduling, paging, deadlocks, threads; OSI vs TCP/IP, ARP, switches and routers; ten classic puzzles (horses, jugs, bridge, jars). Habit: solve each puzzle aloud.
  6. Week 6: Mocks. Two timed 90-minute tests with 3 coding questions each, then three mock interview days: two 45-minute technical rounds (projects, 2 coding questions on paper, theory), a 30-minute fitment round and a 20-minute HR round. Rehearse your stories and your "why Deutsche Bank" answer aloud.

Interns, with one technical round, can trim week 4 to basics; full-time candidates should keep it, because the second technical round carried DP, tree or graph problems in 5 of 11 reports.

Only two weeks? Three days on projects, OOP and DBMS theory; three on linked lists, arrays and sorting; two on SQL and binary search; two on DP, trees and graphs; one on OS, networks and puzzles; three on timed mocks and fitment and HR stories.

Practice problems that match these experiences

These are well-known practice problems that match the patterns above. They are not claims about Deutsche Bank's question bank unless a row says the problem was asked as-is. Projects, OOP, OS and puzzles have no coding analogue; use the question bank for those prompts.

#Practice problemPatternSeen in these experiences as
1Reverse Linked ListPointer manipulationAsked as-is in 2 first technical interviews
2Maximum SubarrayKadane's algorithmAsked as-is in 2 first technical interviews
3Linked List Cycle IISlow and fast pointersAsked as-is: detect a loop and where it starts
4Validate IP AddressString parsingAsked as-is in one 2023 online test
5Koko Eating BananasBinary search on the answerAn OA question the candidate called similar to it
6Combine Two TablesSQL joinsStudents per state from Student and Location tables
7House Robber1D dynamic programmingAsked as-is in one second technical interview
8Longest Palindromic SubsequenceInterval DPAsked as-is, taken to the most optimised solution
9Bottom View of Binary TreeLevel-order with horizontal distanceAsked as-is in one second technical interview
10Jump Game IIIBFS or DFS on indicesAsked as-is, then pushed to a linear solution
11Group AnagramsHashing by a sorted keyAsked as-is in one off-campus interview
12Minimum PlatformsSorting and sweepAsked as-is in one first technical interview

How to handle a question you have never seen

Interviews mix unfamiliar puzzles and short DSA questions on paper, so a repeatable method beats memorised code.

  1. Repeat the problem and one example. Say the input and expected output back before you write, especially for puzzles.
  2. Say the brute force and its complexity. It sets a baseline the interviewer can push from: one candidate went from brute force to DFS and BFS to a linear solution.
  3. Name the bottleneck. Repeated lookups suggest a hash map; "without extra space" suggests two pointers; "smallest value that works" suggests binary search on the answer; overlapping choices suggest DP.
  4. Say when you are stuck. One interviewer gave clues toward the linear solution, and one candidate who could not answer a puzzle offered several partial approaches and still moved on.
  5. Write in small pieces while talking. On paper you cannot run the code, so name helpers clearly and keep the main loop short; one interviewer later read the first round's paper.
  6. Dry-run one case and fix the wrong line. Trace your example by hand and state the time and space complexity at the end, as one selected candidate advised for every piece of code.

Why candidates were rejected

Three counted reports end in a rejection, and none gives a reason. Read these as risk points from those reports and warnings from selected candidates, not as Deutsche Bank's stated reasons.

  • The first round can end it. One 2026 SDE candidate was rejected in the first technical interview after OOP explained "as if to someone who knows nothing", an unusual task to write a "virus" in C++, folder-switching code, and a request to sell the project like a pitch to an investor.
  • The fitment and HR rounds are scored. One 2023 candidate did not reach HR after a fitment round in which the interviewer staged a scenario saying their skills did not fit the job. A 2024 Graduate Analyst was rejected after all four rounds, two of them almost entirely team and conflict questions.
  • Resume items you cannot defend. Three selected candidates advised listing only projects and subjects you know in depth, because interviewers asked about each in depth.
  • Bluffing. Two selected candidates advised saying "I don't know" honestly; one added that HR interviewers are experienced enough to notice.

Selected vs. rejected: do this, not that

No selected candidate described a flawless day; a few habits repeated.

Do thisNot thatWhat the reports show
Own every project: deploy it, know why you chose each tool, and know what you would improvePadding the resume: listing projects or subjects you cannot defendA project deep dive came up in the first technical round in 13 of 16 reports and the fitment round in 9 of 13.
Brute force, then optimise, aloud: give the complexity of every piece of codeJumping to code in silence: or stopping at the first working answerInterviewers pushed for the optimal or no-extra-space answer in 5 reports; one candidate advised stating the complexity of everything you write.
Research the bank: its values, what it does, and the pre-placement talkA generic "why Deutsche Bank": an answer that fits any company"Why Deutsche Bank?" came up for 6 of 16 candidates, "what does it do?" for 3 and its values for 2.
Show teamwork in your stories: what you did inside a team, conflicts includedSolo-hero stories: only individual achievementsOne selected candidate said the bank focuses on teamwork, not only individual skill; team conflict came up for 3 candidates.
Say "I don't know" honestly: then reason aloud from basicsBluffing: inventing an answer under pressureTwo selected candidates gave this advice.

If you remember only five things

  1. A campus test, then one long interview day. An online test of usually 3 coding questions in 90 minutes, then two technical interviews (one for interns), a professional fitment round and an HR round, with the result often that night.
  2. Your projects come up in nearly every report. Project questions appeared in 16 of 16 experiences; know the design, the tool choices and what you would change.
  3. Theory weighs as much as DSA. After projects, the OOP pillars, ACID and SQL vs NoSQL were the most repeated first-round questions.
  4. The non-coding rounds cut candidates. Prepare team stories and a specific "why Deutsche Bank".
  5. Write on paper and think aloud. Some rounds had no way to run code, and puzzles came up in 9 of 16 experiences.

FAQ

What is the online test like?

Usually 3 coding questions in 90 minutes on HackerEarth; 2 coding questions plus MCQs in intern-season tests. Partial test-case scores still reached interviews.

How many interview rounds are there?

Four for full-time candidates in the 10 reports describing a full campus loop: two technical, professional fitment and HR. Interns had one technical round, then fitment and HR.

What is the professional fitment (ProFit) round?

A 20 to 40 minute round in most reports that mixes your projects with team, deadline and background questions, and sometimes a technical task such as an OOP calculator on paper. It cut candidates in two drives.

Do I need finance or banking knowledge?

Not for the technical rounds: one intern noted none was expected. But "why Deutsche Bank?", "what does it do?" and "why a bank?" came up, and one off-campus candidate was asked about investment and banking.

Is system design asked?

No record had a system design round. The closest were a project design or ER diagram, a library database, an OOP calculator, and CAP or sharding questions.

About this guide

The Codinzhub team researched and wrote this guide from 22 Deutsche Bank software engineering records, mostly 2023 to 2026, including experiences and online assessment questions shared on Codinzhub. We kept only what candidates described, plus what Deutsche Bank states officially. The questions are our own short summaries, and the practice links are similar problems unless marked as asked as-is. If you interviewed recently, share your Deutsche Bank interview experience on Codinzhub and we will update this guide.

Disclaimer. Deutsche Bank's process changes by campus, track and year. Use this guide to build a foundation, and confirm the current format with your placement cell.

Search the question bank

The questions from each round above, with practice links for similar problems. Log in to search every question we collected for this role, including questions shared on Codinzhub.

Showing 20 of 103 questions

  • Minimum operations to convert an array into a permutation

    A Deutsche Bank online assessment question shared on Codinzhub (IIT (BHU) Varanasi, November 2026).

    On CodinzhubIIT (BHU) Varanasi, November 2026ArraysCodingOnline assessment
  • Maximum subarray sum with equal first and last elements

    A Deutsche Bank online assessment question shared on Codinzhub (IIT (BHU) Varanasi, November 2026).

    On CodinzhubIIT (BHU) Varanasi, November 2026ArraysCodingOnline assessment
  • Minimum number of cars to turn back

    A Deutsche Bank online assessment question shared on Codinzhub (IIT Guwahati, October 2026).

    On CodinzhubIIT Guwahati, October 2026Not reportedCodingOnline assessment
  • Count anagrams without adjacent equal characters

    A Deutsche Bank online assessment question shared on Codinzhub (IIT Guwahati, October 2026).

    On CodinzhubIIT Guwahati, October 2026StringsCodingOnline assessment
  • Largest perfect binary subtree

    A Deutsche Bank online assessment question shared on Codinzhub (IIT (BHU) Varanasi).

    On CodinzhubIIT (BHU) VaranasiTreesCodingOnline assessment
  • Vertices stop disappearing

    A Deutsche Bank online assessment question shared on Codinzhub (MNNIT Allahabad).

    On CodinzhubMNNIT AllahabadGraphsCodingOnline assessment
  • 13

    A Deutsche Bank online assessment question shared on Codinzhub.

    On CodinzhubCount anagrams without adjacent equal characters: On-campus OA, 3 DSA questions in 90 minutes, 16 October 2026CodingOnline assessment
  • 14

    A Deutsche Bank online assessment question shared on Codinzhub.

    On CodinzhubMaximum distance to a hospital: Question 1 of a 3-DSA on-campus OACodingOnline assessment
  • 15

    A Deutsche Bank online assessment question shared on Codinzhub.

    On CodinzhubLargest perfect binary subtree: Question 2 of a 3-DSA on-campus OACodingOnline assessment
  • 16

    A Deutsche Bank online assessment question shared on Codinzhub.

    On CodinzhubPalindrome with wildcards: Question 3 of a 3-DSA on-campus OACodingOnline assessment
  • 17

    A Deutsche Bank online assessment question shared on Codinzhub.

    On CodinzhubRectangle coverage: maximum points: N distinct points on a 2D plane and an even number; details behind the paywallCodingOnline assessment
  • 18

    A Deutsche Bank online assessment question shared on Codinzhub.

    On CodinzhubAmbulance service: longest driving time: N districts connected by M streets; details behind the paywallCodingOnline assessment
  • Validate an IP address

    Level: Graduate Analyst.

    String parsing and validationCodingRound not stated
  • Collecting coins: each hero beats every monster of power at most its own

    Level: Graduate Analyst.

    Sorting, prefix sums, binary searchCodingRound not stated
  • Largest number up to 1e9 that divides at least K array elements

    Level: Graduate Analyst.

    Divisor countingCodingRound not stated
  • Binary-search-on-answer problem like Koko Eating Bananas

    Level: Graduate Analyst.

    Binary search on the answerCodingRound not stated
  • Grid path DP problem related to Rat in a Maze

    Level: Graduate Analyst.

    Grid dynamic programmingCodingRound not stated
  • Variation of the next greater element problem

    Level: Intern.

    Monotonic stackCodingRound not stated
  • Core CS MCQs on operating systems, DBMS, networks and OOP

    Level: Intern.

    CS fundamentalsCodingRound not stated
  • Walk through your project: design, stack choices and why

    Level: Graduate Analyst, SDE, Off-campus SWE.

    Why this database and not another? Draw the designCodingRound not stated
Page 1 of 6

Keep preparing on Codinzhub

Ready for the next topic?

Keep track of what you’ve learned.