Deutsche Bank technology hiring sits between bank screens and product coding. Expect aptitude/OA coding and interviews on reliability, SQL, and CS.
What actually rejects people
Treating it like pure service aptitude - DB tech expects real coding.
First round: Deutsche Bank OA + interviews
Time split that matches how candidates report outcomes (not a marketing pie chart):
Aptitude/logical 35%
Coding/SQL 35%
CS + domain 20%
HR 10%
Patterns are from student reports and vary by role and drive. Trust your college placement email over blog folklore.
Stage
Time
What they check
OA
timed
Aptitude and/or coding
Technical + HR
multiple
Coding/SQL + fit
Data Structures & Algorithms (40% time) - Focus on arrays, trees, graphs, dynamic programming
Coding Practice (30%) - Solve medium to hard problems on LeetCode, HackerRank
System Design (15%) - Banking systems, low-latency systems, distributed systems
Technical Interview Prep (10%) - Core CS subjects, projects discussion
Aptitude & Math (5%) - Quantitative reasoning, probability, statistics
One timed block that matches Deutsche Bank’s first round (aptitude/coding OA)
Log misses: topic + why you failed (speed, concept, carelessness)
Re-solve yesterday’s misses cold
Twice a week: 10 minutes of resume/project narration out loud
Week
Focus
Exit criteria
1-2
Aptitude / logical
Timed sectional accuracy
3-4
Coding + SQL
Joins + medium coding comfort
5-6
CS + reliability themes
Explain transactions/controls simply
7-8
Mocks + behavioral
Full assessment mock weekly
Confirm whether your invite is aptitude-heavy or coding-heavy
SQL practice if the JD mentions data/tech analyst/SDE
Coding correctness and SQL joins/indexes for tech roles
Talk about reliability and controls without fake finance jargon
Why Deutsche Bank, ethics/teamwork examples, relocation
Medium DSA + SQL joins
Discuss transactions and data consistency simply
Aptitude or coding per invite pattern
SQL fundamentals
Clean project narration
Risk, controls, correctness language
Java comfort for many India tech centers
Full-length mock every other day
Light revision only - no new rabbit holes
Sleep, ID proofs, machine/network checklist for test day
30 days out: weekly full OA-style mocks; close weak DSA patterns; draft STAR stories.
7 days out: alternate mock / review days; re-solve misses cold; no new patterns.
Day before: skim notes, check machine/network/ID logistics, sleep.
Treating it like pure service aptitude - DB tech expects real coding - fix this first
Preparing only interviews while failing Deutsche Bank’s first round
Collecting notes without timed mocks
Listing five frameworks on the resume and defending none
Changing language/stack one week before the drive
Finance trivia instead of engineering depth for tech roles
Goldman Sachs · JP Morgan · Morgan Stanley · Bank of America · Capital One · Wells Fargo
Next step: Run one timed mock this week that matches Deutsche Bank’s first round (aptitude/coding OA), then build the weeks around your weakest section - not around what is most fun to study.