Academic snapshot
Marks: 70% or 7.0+ CGPA (when listed)
Degree: B.Tech/B.E./M.Tech CS/IT/related
Year: Final year + recent grads (~2 years)
Backlogs: None active
Deutsche Bank Placement Papers 2026
Deutsche Bank is a major global bank offering investment banking, retail banking, and financial services across markets worldwide. Its India technology and operations centers in Pune, Bengaluru, and Jaipur hire engineers to build trading, risk, and banking platform systems.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Deutsche Bank eligibility & CGPA (2026)
Deutsche Bank India’s technology hiring for freshers usually targets Graduate Analyst roles on banking platforms, risk, and trading-adjacent systems. The CGPA floor gets you shortlisted; the 90-minute OA and same-day interview stack decide the offer.
Who this hub is for
- For: CS/IT/related engineers aiming at Graduate Analyst (Technology) and similar early-career tech roles in Mumbai, Pune, or Bangalore.
- Not the same funnel: Pure sales, operations, or non-tech analyst hiring without a coding OA.
- Quant angle: Some Quantitative Analyst chatter exists for strong math + coding profiles - still verify the JD; do not assume every tech drive is quant.
Degree, CGPA, branch
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 70% or 7.0+ across 10th, 12th, graduation | Higher GPA helps screens; OA decides |
| Degree | B.Tech / B.E. / M.Tech CS/IT/related | ECE/EEE appear when DSA is strong |
| Backlogs | None active | Clear before joining |
| Gap | Often max ~2 years with reason | Explain with skills |
| Languages | C, C++, Java, Python | One deep language for drive day |
Is 7.0 enough? It matches many reported floors. A 7.2 with clean timed coding and edge-case discipline beats an 8.9 that ships half-broken DP solutions.
Skills bar
OA: Coding + math aptitude
Interviews: DSA + banking system design
Languages: Java, Python, C++ (C allowed)
Hubs: Mumbai, Pune, Bangalore
Who usually fits and who struggles
Good fit: You enjoy medium-hard DSA, can discuss transaction consistency without hand-waving, and only put projects on the resume you can defend for 20 minutes.
Harder path: You skip math aptitude; you list five projects you barely remember; you optimize prematurely and miss correctness. Campus notes repeatedly warn: interviewers dig into whatever you wrote.
Hackerearth-style OA notes from campus
Multiple Graduate Analyst write-ups describe HackerEarth (or similar) papers with three coding problems in ~90 minutes, sometimes with an aptitude component. Treat platform familiarity as part of prep:
- Practice on the same style editor
- Know how custom test cases work
- Watch the scoreboard only if it helps you - anxiety is optional
If your invite names a different vendor, trust the invite. Platforms change; medium-hard DSA themes do not.
Shortlist math from real campus notes
One 2024-style note: OA shortlisted 44 students; interview day cut 27 → 22 → 18 selects. Numbers vary by college strength and seat count, but the shape is consistent - OA is the steep cliff, interviews still eliminate, HR is rarely the main filter if you were honest.
Implication: invest the largest share of hours in timed coding + edges. Professional Fitness matters, but it will not save a failed OA.
DP / binary search / graphs - why they recur
Bank tech OAs like problems that admit a clean optimal solution and punish careless edges:
- Binary search on answer / sorted arrays
- DP on sequences
- BFS/DFS on implicit graphs
- Prefix sums and difference arrays for range updates
When a year pack shows “one easy + two medium,” the mediums are usually where ranks separate. Train finishing mediums with 10 minutes to spare for dry runs.
Design vs “pro-fitness” confusion
Students sometimes prep only DSA and then freeze when Round 2 asks for a transfer-system sketch, or when Professional Fitness asks for conflict stories. Separate your calendar:
- Tue/Thu: coding
- Wed: design sketch
- Fri: STAR rehearsal
- Sat: full OA mock
Mixing all four into one anxious Sunday night produces none of them well.
After you clear - notes worth writing
If you select, write a short public note: OA date, platform, problem themes (not confidential exact text if barred), interview round labels, and one tip. Specifics help the next batch more than motivational paragraphs. That habit also locks your own memory if you interview again later for another team.
Deutsche Bank previous year papers & PDFs
Download 2026 Deutsche Bank placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Deutsche Bank previous year papers actually train
Sets on this site are pattern trainers for OA and early technical rounds - not leaked live assessments. Full archive: previous year question papers.
| Round (typical) | What to practice |
|---|---|
| Online assessment | 90-min coding (2-3 problems) + quantitative/math aptitude |
| Technical 1 | Live DSA with optimization talk |
| Technical 2 | Banking/trading design + project depth |
| Professional Fitness / Managerial | Ownership, pressure, culture |
| HR | Why DB?, location, goals |
Themes that keep repeating (2024-2026)
- 2024: DP, graphs/trees, and array/string work dominate coding blocks; math aptitude still appears. Same-day interview stacks after OA are common on campus.
- 2025: More notes stress optimization and edge cases; system design with scalability shows up in Round 2. Binary search / DP mixes appear in OA shortlists.
- 2026 prep expectation: Keep medium-hard DSA and light quant warm. Expect fresher-depth design on banking systems - not staff-level HFT theater for every Graduate Analyst seat. AI/ML chatter appears in hiring themes - do not replace DSA with buzzwords.
How to use one paper set in a sitting
- Timed: 90 minutes with coding + aptitude mix.
- Untimed: rewrite cleaner solutions; list failed edges.
- Map misses to themes via coding questions.
- 20 minutes: sketch a payments/ledger or market-data fan-out design aloud.
- Rehearse one project deep-dive you might get asked the next day.
Round 1 coding: optimal vs acceptable
Interviewers often accept a correct solution first, then ask you to optimize. That means:
- Ship a correct approach quickly
- Discuss complexity honestly
- Improve if time remains
Students who freeze until they invent O(n) from minute zero sometimes leave zero working code. Deutsche Bank tech culture values production judgment - correctness under time is part of that judgment.
Managerial vs HR - do not mix answers
Professional Fitness/Managerial wants behavioral evidence of how you work. HR wants logistics, motivation, and integrity. Reusing the same 3-minute project monologue for both wastes the Fitness round. Map stories to competencies; keep HR tighter on Why DB?, location, and timeline.
Offer comparison worksheet
When multiple bank offers arrive, score each 1-5 on: CTC clarity, location, team domain (payments vs risk vs platforms), learning, and work-life signals from alumni. Weight what you actually care about before the first HR call. Impulsive accepts are how people end up miserable in month two.
India tech hubs - practical notes
Mumbai, Pune, and Bangalore dominate fresher chatter. Cost of living and commute differ a lot. Ask alumni on LinkedIn about your specific team’s hybrid pattern - company-wide slogans rarely match squad reality. Confirm joining city on the offer letter before you book housing.
Reattempt strategy after a reject
If you clear OA but fail Fitness, drill STAR stories. If you fail OA, drill timed edges. If you fail Round 2 design, schedule weekly banking sketches. Match the fix to the failure mode - generic “I’ll work harder” plans repeat the same reject.
Deutsche Bank hiring rounds in 2026
Campus drives often open August-September for final years; off-campus and experienced hiring run more continuously via careers and referrals.
How to apply
Campus
Placement cell → OA (often HackerEarth-style) → same-day or near-term interview stack.
Off-campus
Apply via Deutsche Bank careers; year-round for some roles.
Referrals
Faster resume visibility; same technical bar.
Round-by-round walkthrough
-
Online Assessment - ~90 minutes
Section Questions Time Difficulty Focus Coding 2-3 60-70 min Medium-Hard Arrays, strings, DP, graphs Math aptitude 5-10 20-30 min Medium Probability, stats, quant Languages: C, C++, Java, Python. No negative marking in most reports. Partial credit for approach sometimes appears. Clear rates often cited ~15-20%.
Time boxing: secure one full coding AC early, protect aptitude minutes, then push problem two. Leaving aptitude blank to chase a third hard problem is a common fail mode.
-
Technical Interview 1 - ~45 minutes
2-3 coding problems or deep follow-ups on OA themes. Evaluation: approach, code quality, complexity, communication. Roughly ~40% of OA survivors advance in student tallies.
-
Technical Interview 2 - ~45 minutes
System design for banking/trading/low-latency ideas, project deep-dives, scalability talk. ~50% of Round 1 survivors move on in many write-ups.
-
Managerial / Professional Fitness - ~45 minutes
Behavioral ownership, teamwork, pressure, light technical discussion. Campus notes often call this Professional Fitness. ~60% advance in optimistic tallies.
-
HR - ~30 minutes
Why Deutsche Bank?, location (Mumbai/Pune/Bangalore), career goals, integrity. ~70% of managerial survivors receive offers when logistics align.
Timeline
| Phase | Duration | Activities |
|---|---|---|
| Application & screening | 1-2 weeks | Resume + eligibility |
| Online assessment | ~1 week window | Coding + aptitude |
| Technical interviews | Often 1 day on campus | Tech 1 + Tech 2 |
| Managerial & HR | Same day or 3-5 days | Fitness + HR |
| Result | 3-5 days | Offer / joining |
Total: often 3-4 weeks, but campus stacks can compress interviews into a single day after OA (see candidate notes below).
What interviewers listen for
- Optimized, correct code with spoken complexity
- Honest resume depth - “mention only projects you know well” is a recurring select tip
- Banking-domain curiosity without fake quant swagger
- Calm communication under same-day interview fatigue
Quant refresh that is enough
You do not need CAT-level quant for most Graduate Analyst OAs. You do need clean school-level speed:
- Percentages and ratios under 60 seconds
- Basic probability (cards, dice, independent events)
- Mean/median intuition
- Permutations/combinations at standard campus level
- Reading a small table without arithmetic mistakes
Drill 15-minute quant bursts three times a week. If you are already contest-strong in math, keep it maintenance-only and spend the hours on DSA edges instead.
System Design prompts for bank tech freshers
| Prompt | Talking points |
|---|---|
| Fund transfer API | Auth, validation, ledger, idempotency, notifications |
| Account statement feed | Pagination, indexing, caching, consistency lag |
| Fraud alert pipeline | Event stream, rules, false-positive trade-offs |
| Market data fan-out | Pub/sub, fan-out lag, backpressure (high level) |
| Password reset flow | Tokens, expiry, audit, rate limits |
Timebox each to 25-30 minutes. Stop when the design is coherent - overbuilding into Kafka-everywhere fantasies signals insecurity more than skill.
Live coding habits interviewers reward
- Restate constraints and ask about input sizes
- Start with a correct approach, then optimize
- Narrate trade-offs (“O(n log n) sort vs O(n) count if alphabet small”)
- Test with empty, single, duplicate, and large-ish mental cases
- Clean naming - they may reopen this code in Round 2
Silent coding with a perfect answer still underperforms a slightly slower solution with clear speech.
Peer mock schedule (final 3 weeks)
| Session | Format | Goal |
|---|---|---|
| Weekly OA | 90 min solo timed | Score + error log |
| 2x coding | 45 min peer | Narration under pressure |
| 1x design | 30 min peer | Banking prompt |
| 1x Fitness | 30 min peer | STAR stories |
If you lack a peer, record yourself on phone explaining a solution - cringe review works.
How db prep overlaps with other banks
| Firm | Shared | Add for Deutsche Bank |
|---|---|---|
| JP Morgan / GS | Hard DSA | Specific Professional Fitness labeling + India hub talk |
| Morgan Stanley | Coding stamina | Quant light + banking design |
| Capital One | Product/analytics flavor | More classic bank platform design |
Keep one DSA trunk. Branch “Why this bank?” answers so you do not mix brand stories under stress.
Offline PDF drills when wi-fi fails
Hostel networks die on OA weeks. Download the Deutsche Bank Placement Papers PDF (2026) and keep two handwritten notebooks: one for coding dry-runs, one for quant bursts. Time yourself with a phone clock. Platform familiarity still matters - when Wi-Fi returns, do at least two mocks on an online editor so mouse/keyboard habits match test day. Paper-only heroes sometimes freeze on IDE shortcuts they never practiced.
Also bookmark online assessment, coding questions, and interview experience for the nights you need theme cousins after a miss. The hub is the map; linked practice pages are the gym.
Where to practise for Deutsche Bank
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
What to practise before a Deutsche Bank drive
If a Deutsche Bank invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Deutsche Bank sits around ₹12-15 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Deutsche Bank fresher eligibility 2026 (from student reports): typically 70% or 7.0+ CGPA across 10th, 12th, and graduation; B.Tech/B.E./M.Tech in CS/IT or related fields; final-year students and recent grads (within ~2 years); no active backlogs. Strong Java, Python, or C++ helps. Always verify the campus JD or careers portal.
What you are training for: Typical Graduate Analyst (Technology) loop: Online Assessment (~90 min coding + math aptitude) → Technical Interview 1 (DSA) → Technical Interview 2 (system design / projects) → Managerial or Professional Fitness → HR. Many campus drives stack interviews on one day after OA. End-to-end often 3-4 weeks, sometimes faster inside a drive week.
Short version of the prep split: Split time roughly: DSA ~40%, timed coding mocks ~30%, banking/trading system design ~15%, CS fundamentals + projects ~10%, quantitative aptitude ~5%. Focus on optimization and edge cases - DB interviewers notice incomplete brute force.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Deutsche Bank previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Deutsche Bank drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Deutsche Bank usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Deutsche Bank?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Deutsche Bank-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Deutsche Bank story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Deutsche Bank PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Deutsche Bank papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Deutsche Bank papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Deutsche Bank-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed Deutsche Bank paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Deutsche Bank. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
What to carry into the interview room
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Deutsche Bank, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
Tracking that does not become a second job
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Deutsche Bank mistakes, you are collecting content, not preparing.
Extra drill block (2)
Sit one more mixed Deutsche Bank set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Extra drill block (1)
Sit one more mixed Deutsche Bank set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Last-mile notes for Deutsche Bank prep
A note on mocks vs. random problem lists
Random Deutsche Bank problems feel productive. Timed mocks are what move the needle. If you only have an hour tonight, sit 40 minutes of a previous-year Deutsche Bank set and spend 20 minutes on the three misses. That loop beats an untimed 8-problem grind you will not remember tomorrow.
How to use this page the night before
Do not reread the whole Deutsche Bank hub. Skim eligibility once, open your error log, and recast the two STAR stories you will actually say. If the drive names an OA platform, click around it for five minutes so login panic is not your first round.
Pairing with a friend
One useful Deutsche Bank drill: you set a 25-minute timer, your friend picks a question from this site, you talk the approach before typing. Swap. You will hear the holes an interviewer hears. Do this twice a week in the last fortnight, not every night.
Deutsche Bank compensation & benefits
Figures below are candidate-reported as of August 2026 (total annual bands). Confirm written offers.
Technology ladder
| Level | Experience | Base (approx.) | Total package | Typical background |
|---|---|---|---|---|
| Graduate Analyst | 0-1 years | ₹10-12 LPA | ₹12-15 LPA | Strong coding freshers |
| Associate | 1-2 years | ₹15-18 LPA | ₹18-22 LPA | Design depth |
| Senior Associate | 2-3 years | ₹20-25 LPA | ₹25-30 LPA | Ownership |
| Vice President | 3-5 years | ₹30-40 LPA | ₹40-50 LPA | Domain expertise |
Other roles mentioned
| Role | Level | Total package | Notes |
|---|---|---|---|
| Quantitative Analyst | Graduate | ₹15-20 LPA | Strong math + coding |
| Risk Analyst | Associate | ₹18-25 LPA | Risk + finance literacy |
Benefits candidates cite
Health cover for family, performance bonus (often discussed as ~15-30% of base in chatter), learning budgets, hybrid norms on some teams, PF/gratuity style retirement benefits. Equity/stock language varies - read the letter.
Graduate analyst vs quant paths
Most engineering students should prepare for Graduate Analyst (Technology). Quant roles, when open, usually signal heavier math/stats and sometimes different CTC chatter. If your JD says Graduate Analyst, do not derail into stochastic calculus cosplay in week two of prep. If your JD says Quantitative Analyst, raise the math share and confirm coding expectations on the notice.
Bonus and CTC reading tips
Student bands like ₹12-15 LPA often mix base and variable. In HR:
- Ask for CTC breakup politely if not shared
- Clarify joining bonus vs annual bonus
- Confirm location HRA assumptions if comparing offers
Do not argue from a GFG comment. Argue from the letter in your inbox.
One-day interview nutrition
Same-day stacks fail from blood sugar as much as from DP. Practical checklist:
- Protein breakfast
- Water between rounds
- 3-minute walk after Tech 1 if schedule allows
- No new “quick tip” videos between rounds
Your brain already knows enough. Protect it.
If you miss OA by a little
Common recoveries:
- Off-campus careers applications next cycle
- Referral after an internship elsewhere
- Stronger mock discipline for 8 weeks, then reapply when eligible
Do not spam applications weekly inside blackout windows. Fix the error log that actually failed you - usually edges or timeboxing, not “I need more motivation.”
Recent Deutsche Bank placement trends
Skills emphasis
AI/ML and cloud-native talk appears in hiring themes; coding + design fundamentals still decide offers.
Process
System design weight remains meaningful for Round 2. Behavioral/Professional Fitness stays explicit on campus stacks.
India footprint
Tech teams continue in Mumbai, Pune, Bangalore - confirm joining city on the offer.
Prep implication
No shortcut past timed medium-hard DSA. Add one banking design sketch weekly.
Common questions about Deutsche Bank hiring
Papers & process
Can I download Deutsche Bank placement papers PDF?
Yes. Free Deutsche Bank placement papers PDF with coding, math aptitude, and interview themes are on this site - no registration. Start with the 2026 PDF.
What is the Deutsche Bank placement process?
OA (~90 min coding + math aptitude) → Technical 1 → Technical 2 → Managerial/Professional Fitness → HR. Campus drives often stack interviews on one day after OA. End-to-end commonly 3-4 weeks.
How many rounds are there in Deutsche Bank interview?
About five stages in most Graduate Analyst write-ups. Labels vary (Professional Fitness vs Managerial).
What is Deutsche Bank Online Assessment exam pattern?
Typically 90 minutes: 2-3 medium-hard coding problems plus 5-10 math aptitude questions. Languages C/C++/Java/Python. Clear rates often ~15-20%.
What is Deutsche Bank Professional Fitness round?
A behavioral/managerial-style round on many campus stacks - ownership, teamwork, pressure, light project talk - between technical rounds and HR.
Eligibility & languages
What is Deutsche Bank eligibility criteria for freshers 2026?
From student reports: 70% or 7.0+ CGPA across 10th/12th/graduation when listed; CS/IT-related degrees; final-year or recent grads; no active backlogs. Verify your JD.
What programming languages are required for Deutsche Bank?
C, C++, Java, Python are commonly allowed. Java and Python are frequent in India tech talk. Use one language consistently on drive day.
Can I apply with backlogs?
Active backlogs are usually blocked. Cleared historical backlogs are typically fine.
Salary & comparison
What is Deutsche Bank salary for freshers in 2026?
Graduate Analyst commonly ₹12-15 LPA in student reports; Associate ~₹18-22; Senior Associate ~₹25-30. Confirm written offers for Mumbai/Pune/Bangalore roles.
Deutsche Bank vs Goldman Sachs vs JP Morgan - which is better?
DB India tech often sits around Graduate Analyst ₹12-15 LPA with banking platform work. GS/JPM may post higher fresher bands on some campuses with heavier quant pressure. Compare team and letter, not Twitter rankings.
Prep
How to prepare for Deutsche Bank placement?
Roughly DSA 40%, timed mocks 30%, banking design 15%, CS/projects 10%, quant 5%. Weekly 90-minute OA simulations beat passive problem collecting.
Any pro tip for Deutsche Bank placement preparation?
Optimize for correctness and complexity. Practice edges deliberately. Only list resume projects you can defend in depth.
What topics should I focus on?
Arrays, trees, graphs, DP, hash maps; probability/stats basics; banking transaction and low-latency design at fresher depth; OOP/DBMS for follow-ups.
Is Deutsche Bank OA only coding?
Many reports describe coding plus mathematical aptitude inside ~90 minutes. Weighting varies. Practice both; do not assume a pure LeetCode contest format unless your invite says so.
What is asked in Deutsche Bank Technical Round 2?
Commonly system design for banking/trading-style systems, scalability talk, and deep project discussion. Expect follow-ups on technologies you listed. Fresher depth: clear components and trade-offs, not HFT microstructure trivia unless the role is quant-heavy.
How important is the Professional Fitness round?
It is a real filter on campus stacks - not a formality. Weak STAR stories and arrogance after clearing Tech rounds do get people rejected. Prepare ownership and conflict examples before interview day.
Deutsche Bank - recent candidate experiences
A Graduate Analyst campus select (write-up titled 2024) dated the funnel tightly: “Online Assessment Round was conducted on 13th Aug, 2023 and all the interviews were conducted on 17th Aug, 2023” - a 90-minute HackerEarth paper with three coding problems, then Technical 1, Technical 2, Pro-Fitness, and HR stacked the same interview day (GeeksforGeeks).
Deutsche Bank visited for Graduate Analysts on 27 July 2024; OA on 22 July (one easy + two medium coding, binary search/DP) shortlisted 44 students (GeeksforGeeks). Same-day virtual Tech I/II, Professional Fitness, and HR cut to 27 → 22 → then 18 final selects. Tip from the selected candidate: “Mention only those projects and subjects in your resume that you know very well because they will ask in-depth questions from them.”
Deutsche Bank Graduate Analyst loops reward optimized correct code, honest resumes, and steady communication across a long interview day. Treat Professional Fitness as seriously as Technical Round 1 - campus notes show it removes people who thought the hard part was already over.
Keep one banking design sketch and one STAR story warm the morning of interviews - not a new algorithm textbook chapter. Calm beats cramming.
Related companies to compare
Goldman Sachs · JP Morgan · Morgan Stanley · Bank of America · Capital One · Wells Fargo