Deutsche Bank Of India Interview Experience For Graduate Analyst
Interview Experience
In this article, I'd like to share my interview experience for a Graduate Analyst role at Deutsche Bank Of India during their recent campus recruitment drive. My goal is t...
Full Details
In this article, I'd like to share my interview experience for a Graduate Analyst role at Deutsche Bank Of India during their recent campus recruitment drive. My goal is to provide valuable insights into the interview process. The interview process began with an online assessment consisting of three questions. I completed all of them, advancing to the
next round. The interview process itself consisted of four rounds: two technical rounds, a professional fitness round, and an HR round.
Technical Round 1 The interviewer was a Web Developer professional with 7 years of experience. Focused on DSA, DBMS, OOPs, OS and Project DSA : Discussed an algorithm to move negative numbers to the beginning and positive numbers to the end of an array in constant extra space (Problem Link ). Dry run and Explanation with different variants of the question like Maintain the order of element Moving zeroes to the end or front Different approaches DBMS: Explained ACID properties in detail. OOPs: Discussed Polymorphism in detail, with cross-questions on function overloading and different types of polymorphism. OS: Briefly explain the OSI model layers and their order. Explained the difference between paging and segmentation, including internal and external fragmentation, and how each can occur. Puzzles: Mislabelled Jar 10 Balls In 5 Lines Projects: Discussed projects in detail, showcasing deployed versions. My project Links Squad - one-to-one video calling web app ( made from scratch). I also showed my Firebase console to make sure that, she felt, I understood every bit of the project. Unwind - movie search web application ( made from YouTube). It takes some time to load the movies SDLC: Explained the Software Development Life Cycle and basic methodologies. I asked about her role and experiences.
Technical Interview The interviewer was a Team Lead with 15-16 years of experience. Projects: Focused heavily on project discussions, so be prepared for detailed explanations and cross-questions. How much data speed is required for a video calling web app ( Based on my project Squad)? Discussed problems encountered during project development and how they were solved. Emphasize your problem-solving and leadership skills. Problems encountered between team members and how you manage it. ( As Squad is a team project). Puzzle: Solved another puzzle ( 85 Chain Link Puzzle ). Again I asked about his role and experiences in leading teams. Professional Fitness Round The interviewer was a Solution Architect with 15+ years of experience. Behavioural: Focused on teamwork and real-world scenarios. Scenario 1 : Discussed how to handle a conflict with an angry senior colleague. Scenario 2 : Explained your approach to managing a crucial project assigned during your wedding time. Highlight your leadership and project management skills. What improvement you can make to your projects? Again I asked about his role and experiences in leading teams.
HR Round: The interviewer had vast experience (around 19 years) in various sectors (specific role unclear). Business Ethics: Briefly discuss business work ethics. Team Conflict: Discussed a team conflict scenario and your approach to resolving it. Open to Questions : The interviewer offered the opportunity to ask questions about the company or role. Unexpected Question: When I repeat the same question: "What is your role and how was your experience". He had all my feedback from previous rounds. So, he said in a friendly manner "You asked the same question to all interviewers, don't you have any other questions or do you just remember one question to ask" and laughed. I smiled and said: " Sir when I ask about the role and experience of anyone, each person gives me a brief idea about their life and experience, which gives me a good idea of how corporate professionals are. Not only that, asking different questions to different people without any basis just messed up everything, so why not ask the question about something that can be generalized to help me in future." He laughed and said it was a good reason. and told me about his experiences.
Note: I haven't included specific HR questions, as it might not be ideal for your unique interview. Final
Verdict Selected for the Graduate Analyst Role.
About This Question
This is a candidate experience report from a deutsche bank interview for a eng manager role (new grad level) during the oa round reported in 2025.
It covers the following topics: Arrays .
Difficulty rating: Easy
Topics
More Deutsche Bank Interview Questions
About Deutsche Bank Interview Reports
This question was reported by a candidate who interviewed at Deutsche Bank. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Deutsche Bank are the higher-signal extractions to take from this report.
For broader preparation context, the Deutsche Bank interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Deutsche Bank reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Deutsche Bank Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Deutsche Bank reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.