Deutsche Bank Interview(virtual) Experience | On-campus for Internship (Pune)
Question Details
First Round: It was held on 13th August 2020. It was an online coding round of 1 hour 30 minutes. This assessment took place on Hackerearth. It consisted of 10 MCQ questio...
Full Details
First Round: It was held on 13th August 2020. It was an online coding round of 1 hour 30 minutes. This assessment took place on Hackerearth. It consisted of 10 MCQ questions and 2 coding questions. The coding questions were both from the topic arrays. To find if the given array of even number of elements is possible to rearrange such that left half of the array is equal to the right half that is if M=N/2 then a 1 =a (M+1) ,a 2 =a (M+2) ,.......,a M =a N . The output format had to be YES or NO. You are given an array arr containing N distinct integers. You must perform the following operations on the array: For each pair of integers of the array, you must find the absolute difference D between these integers and insert D into the array. If D is already an element of the array, then you are not required to insert D into the array You repeat task 1 until the array cannot be modified further. This implies that the absolute difference between any two elements in the array is already an element of the array. Write a program to find the Kth the largest element of the final array after the array cannot be modified further. If there is no such element then print -1. The MCQs which were asked were basic questions from DBMS, Computer networks,OOP, and Operating System. 28 students were shortlisted after this round. The next day on 14th August 2020 we had our pre-placement talk which started at 8:00 am and ended at 9:00 am. They told us that we will further have three rounds that are Technical, Professional fitness, and HR.
Technical Round :(Held over Skype Business): Asked me about the difference between arrays and linked lists. Examples were arrays and linked lists is used. Gave me around 3 questions and asked whether the code will compile and execute or not. Then he gave me two coding questions to do it on the notepad. They were very easy one was using a simple if-else loop and the other was given an array print the product of minimum k numbers. 19 students were shortlisted after this round. Professional Fitness Round:(Held over Skype Business): Asked me about my projects and interests. I did not talk much about my technological interests. This round did not go well for me. But mostly I believe he wanted to check whether you have the desired skills for the internship or not. If not then are you willing to learn these skills or not. 11 students were shortlisted after this round. I got eliminated in this round. HR Round:(Held over Skype Business): I asked my friends about how this round went they said it was a very informal round where they asked about interests and hobbies. All the 11 students were selected in this round.
About This Question
This is a reported interview question from a deutsche bank interview for a swe role (intern level) during the recruiter round reported in 2020.
It covers the following topics: Arrays, Linked List, Os, Oop .
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.