Deutsche Bank interview experiences from Cary, New York and India

Deutsche Bank interview experiences in the US describe a phone or virtual screen, then a Superday of mostly behavioral interviews with conversational Java questions, puzzles or a LeetCode-medium problem. In India, the campus Analyst loop is a 90-minute HackerEarth test, two technical rounds on DSA, DBMS, OOP, projects, puzzles and SQL, a pro-fitness round, then HR, often on the same day.

TDI graduate (typical): SHL online assessments → HackerRank coding OA (~90 min, MCQs + 2 problems) → HireVue recorded behavioral → Superday (~1 week later, 3 back-to-back live interviews).

Classic campus Analyst (typical): 90-minute OA (often three coding problems on HackerEarth) → Technical 1 (DSA, DBMS, OOP, OS, projects) → Technical 2 (deeper projects, puzzles, SQL) → Pro-fitness → HR. Total timeline often 3-4 weeks from application to offer.

Deutsche Bank interview process in the US: Cary and New York reports, 2022-2026

Each bullet is one Glassdoor review from a US location. Deutsche Bank runs its US technology internships and graduate program in Cary, North Carolina and New York; New York is also home to its investment bank teams.

• Software Engineer New Grad, Cary, NC, November 2024 (accepted offer): Applied online and finished in a little over a week. Round-robin interviews, mostly behavioral, with conversational technical questions on Java and their technical background. They rated it easy and said the behavioral questions were standard ones you can find online.
• Software Engineer Intern (review posted October 2026, listed Orlando, FL; no offer): About three interviews on one day: a technical round, a round of puzzles and riddles, and questions on the resume, ending with a conversation with an engineer. They put the coding at LeetCode medium.
• Analyst, New York, March 2022 (campus recruiting, accepted offer): A 30-minute phone interview with standard behavioral and technical questions, then an in-person Superday of two one-on-one interviews.
• Capital Markets Analyst, New York (review posted October 2026, accepted offer): The first conversation covered current market trends and the macro environment; the Superday was brain teasers, behavioral questions and why Deutsche Bank.
• Investment Banking Summer Analyst, Princeton, NJ (review posted October 2026, accepted offer): An online assessment, a behavioral first-round screen, then a Superday of two 30-minute interviews, one behavioral and one technical. The offer call came the same week.

Round-wise process: India campus and global TDI

Deutsche Bank India interview experiences

Experience 1: Graduate Analyst, on-campus (August 2023)

Source: GeeksforGeeks write-up - online assessment on 13 August 2023, all four interviews on 17 August

Online assessment (90 min, HackerEarth)

• Three coding problems: validate an IP address (medium), a greedy “collecting coins” problem (easy), and the largest number up to 10^9 that divides at least K array elements (hard).

Technical round 1 (45-50 min, with the CTO)

• Hackathon project: its USP and high-level design, including authentication and forgot-password flows.
• Git internals; middle of a linked list; real-life uses of BST, stack and linked list, and when a linked list beats an array; OOP pillars; SQL vs NoSQL (dynamic schema, CAP, ACID).

Technical round 2 (65-70 min)

• Git from clone to merge; SQL vs MongoDB speed in different scenarios; create a table, insert rows and query it live.
• DSA: find the duplicate in a 100-element array; implement a stack; Fibonacci and its uses.
• Two puzzles: a rupees-and-paise bank withdrawal puzzle (not solved in time) and the four-people bridge crossing.

Pro-fitness round (50 min)

• Projects shown on a phone: a college fest website and a resume site hosted on S3 behind CloudFront; how they handled high traffic, what stack they would pick with funding, planned improvements; behavioral questions, family background, higher-studies plans.

HR (15-20 min, Teams)

• Hobbies and favorite games; situational: a critical bug the evening before a deadline; why Deutsche Bank.

Result: Selected
What helped, per the candidate: knowing how each data structure is implemented with real-world uses, full-stack projects you know thoroughly, and starting from basics on hard questions.

Takeaways

• What decided it: Clearing a three-problem OA, then project depth and DS implementation questions, puzzles, a scalability talk in pro-fitness, and a critical-bug HR scenario
• Common fail: Knowing DS APIs without implementations, or freezing on a timed puzzle
• How to practice: Implement stack/LL/BST from scratch; Git workflow drills; bridge and money puzzles; prepare a scalability story for one project

Experience 2: Graduate Analyst, on-campus (July 2023)

Source: GeeksforGeeks write-up - 44 cleared the online round at that college, 18 were finally selected

What differed

• All interview rounds ran the same day (22 July 2023), back to back. The write-up’s main practical advice is about keeping your energy up.
• Technical 1 (30-40 min): microprocessors and microcontrollers from the ECE syllabus, OOP pillars, SQL on an employee table (highest-paid employees), C vs C++ vs Java, and two puzzles (cut a cake into eight with three cuts, measure 7 litres with 4- and 5-litre buckets).
• Technical 2 (30-40 min): why Node.js, asynchronous JavaScript, the project’s ER diagram, SQL vs MongoDB, why indexing, build a BST from an array, choosing a routing protocol for a scenario, and a logic puzzle.
• Pro-fitness (30-40 min): 12th-grade maths marks then a word problem, hometown vs college town, and branch-specific electronics questions for an ECE candidate (attenuation, CDMA vs GSM, multiplexing, op-amps).
• HR (5-10 min): describe yourself beyond the resume, people skills, why engineering, a stressful situation, online vs in-person semesters.

Result: Selected
Takeaway: puzzles came up in both Graduate Analyst write-ups, and the pro-fitness round pulled from the candidate’s own branch - this ECE candidate got ECE questions, not DSA.

Takeaways

• What decided it: Same-day stamina across OOP/SQL/puzzles, indexing/networking in Tech-2, and branch-specific pro-fitness
• Common fail: Prepping only DSA while ignoring puzzles and your own branch syllabus
• How to practice: Full-day mock loops; SQL salary queries; classic logic puzzles; revise core branch subjects

Experience 3: Summer Analyst TDI - on-campus (August 2025)

Source: Medium - Pritee Pardeshi - 8 August 2025; OA + 2 technicals + HR

Online assessment (90 min)

• 10 MCQs (DBMS, OS, networks, OOP output questions; no negative marking) and two coding problems: a minimum-time-to-destination variant with skips, and longest common substring (DP). All tests passed; 54 shortlisted.

Technical interview 1 (1 hr 15 min)

• ML project and Python: rotate a list; explain every sorting algorithm with complexities and write bubble sort; swap without a third variable; debug a pop() bug; add two numbers without + in C, C++, Java and Python
• ML scenario: 75% training vs 35% test accuracy (overfitting) and why logistic regression
• DBMS: DDL vs DML; join types with examples; query for the second-most-sold product on a date
• 27 moved on

Technical interview 2 (1 hr 20 min)

• OOP pillars with live code; abstraction vs interface; diamond problem; final to stop inheritance
• Puzzles: three mislabeled boxes; measure 9 minutes with 7- and 4-minute hourglasses
• “Why Deutsche Bank over Persistent?” (the candidate held a Persistent scholarship)
• SQL: department names with teacher counts in a range - the interviewer hinted to rewrite a rough query neatly, which mattered because the sheets were kept
• 17 reached HR

HR (20 min)

• Self-introduction, why Deutsche Bank, handling people who dislike you, handling an unexpected change (a hackathon date moved up)

Result: Selected for the 2026 internship (TDI)
Takeaway: SQL written neatly on paper, OOP depth and calm puzzle-solving counted as much as the OA coding.

Experience 4: TDI internship - MNIT Jaipur on-campus (2026 cycle report)

Source: LinkedIn - Maahir Taneja

Online assessment

• 10 MCQs on OOP, DBMS and networks; two DSA problems (a priority queue problem and DP on grids)

Technical interview 1 (VP-led, 20-25 min)

• In-depth projects; DBMS; computer networks; sorting algorithms and complexities

Technical interview 2 (about 1 hour of DSA)

• Four coding problems spanning dynamic programming and graphs; the interviewer said he did not expect fully optimized answers in the time, but the candidate got there

HR

• Personality, interests, situational prompts, college journey

Result: Selected for Summer Intern Analyst, TDI
Takeaway: Internship loops can pair a short VP-led fundamentals round with a separate heavy DSA hour - prep both.

Questions that come up often

Coding / technical

1. Valid parentheses / expression checks. Usually expects stack
2. Find duplicates in a stream. Usually expects hashing
3. SQL + coding hybrid (nth highest / joins). Usually expects window functions / careful queries
4. Discussion on settlement systems and Java, bottlenecks, failure modes, simple APIs
5. Detailed project discussion, architecture, hardest bug, what you would change

HR / behavioral

1. Why banking technology?
2. Comfort with background verification timelines
3. Location preference
4. Strengths and weaknesses

Practical tips for Deutsche Bank

• Clear the screening round first. Timed practice beats last-minute topic hopping.
• For domain questions, explain settlement systems in plain language, inputs, outputs, what breaks at scale.
• OOPs and SQL still open a lot of Deutsche Bank panels. Do not skip fundamentals.
• HR answers should be concrete. One story with a result beats five slogans.

HR interview

After technical rounds, Deutsche Bank usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioral stories.

Sample answers for high-frequency questions

Q. How do you check whether an expression has balanced parentheses?
A. Scan the string once with a stack. Push every opening bracket; on every closing bracket, pop the top and check it is the matching opener - if the stack is empty or the pair mismatches, the expression is invalid. After the scan the expression is balanced only if the stack is empty, which catches unclosed openers. Time complexity is O(n) and space is O(n) in the worst case, where every character is an opening bracket. Deutsche Bank’s HackerRank OA asks this as a valid-parentheses or expression-check problem, and interviewers often follow up by asking you to extend it to three bracket types or to report the index of the first mismatch.

Q. How do you find duplicates in a stream of numbers?
A. Keep a hash set of values already seen. For each incoming element, check membership in O(1) average time: if it is present, report a duplicate, otherwise insert it. Over n elements this is O(n) time and O(k) space for k distinct values. If the values are bounded - say integers from 1 to n - you can drop the hash set and use a bit array or the in-place index-negation trick for O(1) extra space. If the stream is unbounded and approximate answers are acceptable, a Bloom filter gives constant memory with a tunable false-positive rate but never false negatives.

Q. Write a SQL query to find the third-highest salary.
A. Use a window function: SELECT DISTINCT salary FROM (SELECT salary, DENSE_RANK() OVER (ORDER BY salary DESC) AS rnk FROM employees) t WHERE rnk = 3; DENSE_RANK is the right choice because it gives tied salaries the same rank and does not skip the next number, so the third-highest distinct salary really is rank 3. Using RANK instead would skip ranks after a tie and could return no row, and ROW_NUMBER would treat duplicate salaries as distinct values. The older correlated-subquery or LIMIT 1 OFFSET 2 forms also work, but window functions are what Deutsche Bank interviewers usually want to see.

Q. What is the difference between RANK, DENSE_RANK and ROW_NUMBER?
A. All three are window functions that number rows within a partition according to an ORDER BY. ROW_NUMBER assigns a unique sequential number even to ties, so two equal salaries get 1 and 2 arbitrarily. RANK gives ties the same number but then skips values - two rows tied at 1 are followed by rank 3. DENSE_RANK gives ties the same number and does not skip, so the same case is followed by rank 2. Pick ROW_NUMBER for deduplication or pagination, RANK when gaps are meaningful in a leaderboard, and DENSE_RANK for nth-distinct-value queries.

Q. What is trade settlement, and what does T+1 mean?
A. Settlement is the post-trade stage where the securities actually move to the buyer and the cash moves to the seller, completing the obligation created when the trade was executed. T+1 means settlement finalizes one business day after the trade date - Indian equities moved to T+1 in 2023 and US markets followed in May 2024, replacing the older T+2 cycle. Shorter cycles reduce counterparty credit risk and the margin clearing houses must hold, but they compress the window for confirmation, allocation and funding, which is exactly why banks invest heavily in settlement technology. A clearing house acts as central counterparty, netting obligations so far fewer gross transfers are required.

Tips from successful candidates

Sources

Cross-check your test invite for timings. For OA practice, see Deutsche Bank placement papers.

• Deutsche Bank Graduate Analyst on-campus - GeeksforGeeks (2023)
• Deutsche Bank Graduate Analyst - GeeksforGeeks
• Deutsche Bank internship 2026 experience - Medium (Pritee Pardeshi)
• Deutsche Bank TDI internship journey - LinkedIn (Maahir Taneja)
• Deutsche Bank interview reviews in the US, including Cary, New York and Princeton reviews - Glassdoor
• Deutsche Bank application process and online test rules - Deutsche Bank Careers

Similar companies

Goldman Sachs · JP Morgan · Morgan Stanley · Bank of America · Capital One · Wells Fargo