Interview experience
HDFC Bank Interview Questions and Answers (2026)
Overview
Section titled “Overview”HDFC Bank’s Technology Analyst / SDE process is a DSA-plus-SQL loop wrapped around a longer interview chain than most banks - some candidates report a hiring-manager round and a separate senior-leadership round on top of the standard technical and HR stages.
HDFC Bank interview process at a glance
Section titled “HDFC Bank interview process at a glance”| Round | Duration | What they test |
|---|---|---|
| Online Assessment | 90-120 min | Aptitude + coding / technical MCQs |
| Technical Round 1 | 45-60 min | DSA, OOPs, SQL |
| Technical Round 2 | 45-60 min | Projects, domain (banking apps), Java/JS/frameworks |
| HR / managerial round(s) | 20-30 min each | Motivation, location, background verification, sometimes a separate leadership round |
Online Assessment
Section titled “Online Assessment”A 90-120 minute test measuring numeracy, logical ability, and language proficiency, plus a coding/technical section scoped to your specialty area. Shortlist decisions typically arrive within a few days.
Common questions
- Quantitative aptitude and logical reasoning MCQs
- Language/verbal-ability questions
- A timed coding problem (Easy-Medium), clean fully-passing solutions score better than partial cleverness
Technical Round 1
Section titled “Technical Round 1”Opens with a DSA coding problem, then moves into OOPs and SQL fundamentals - the two topics candidates say open the most HDFC Bank panels.
Common questions
- Valid parentheses / expression checks (expected approach: stack)
- Find duplicates in a stream (expected approach: hashing)
- SQL + coding hybrid - nth highest salary, joins, window functions
- OOPs fundamentals - abstraction, inheritance, polymorphism with examples
Technical Round 2
Section titled “Technical Round 2”Shifts to a detailed project discussion and domain conversation about HDFC Bank’s banking apps. Engineering-heavy roles add Java, JavaScript, or framework questions (Spring Boot, React).
Common questions
- Walk through your project’s architecture, hardest bug, and what you’d rebuild
- Explain a banking-app concept in plain language - inputs, outputs, what breaks at scale
- Java/JS fundamentals or framework-specific questions (Spring Boot, React) for engineering roles
- Bottlenecks and failure modes in a system you’ve built
Round-by-round narratives are on the HDFC Bank interview experience page.
HR / managerial round(s)
Section titled “HR / managerial round(s)”A closing conversation on motivation and logistics. Some reports describe this as more than one touchpoint - an HR coordinator’s screening call, a mixed technical+behavioral round with the hiring manager, and occasionally a final senior-leadership discussion - rather than a single HR interview.
Common questions
- Why banking technology / why HDFC Bank?
- Comfort with background verification timelines
- How would you handle an unhappy customer whose complaint you can’t resolve immediately?
- How would you prioritize your day to consistently meet an aggressive sales target?
Sample answer frameworks for each of these are on the HDFC Bank HR interview questions page.
Why the interview chain can run longer than expected
Section titled “Why the interview chain can run longer than expected”Unlike a single HR round, some HDFC Bank candidates - particularly for Technology Analyst/SDE and off-campus hires - report a longer chain: an HR coordinator’s initial screen, a technical/functional round, a mixed technical+behavioral round with the hiring manager, and a final senior-leadership discussion. Budget closer to 3-4 weeks if your process includes this extra layer, rather than assuming a single closing HR call.
Common technical interview questions and answers
Section titled “Common technical interview questions and answers”Q: How do you check whether a string of brackets is valid?
Use a stack. Scan the string left to right: push every opening bracket, and on every closing bracket pop the top and check it is the matching opener. The string is valid only if every pop matches and the stack is empty at the end - an empty stack on a closing bracket means an unmatched close, and a non-empty stack at the end means an unclosed open. For example “([)]” fails because the ‘)’ pops a ‘[’, while “([])” succeeds. Time complexity is O(n) and space is O(n) in the worst case, where n is the string length.
Q: How do you find duplicates in a stream of numbers?
Keep a hash set of everything seen so far. For each incoming value, check membership first: if it is already in the set it is a duplicate, otherwise insert it. Each lookup and insert is O(1) on average, so processing the whole stream is O(n) time with O(k) space for k distinct values. If the values are known to be bounded - say IDs from 1 to n - you can swap the hash set for a boolean array or bitset and cut memory sharply, which is the follow-up interviewers usually push for.
Q: Write a SQL query to find the nth highest salary.
The portable approach uses DENSE_RANK: SELECT salary FROM (SELECT salary, DENSE_RANK() OVER (ORDER BY salary DESC) AS rnk FROM employees) t WHERE rnk = 3 for the third highest. DENSE_RANK matters here because RANK skips numbers after ties and ROW_NUMBER gives duplicate salaries different ranks, so both give wrong answers when two people earn the same amount. A simpler engine-specific version is SELECT DISTINCT salary FROM employees ORDER BY salary DESC LIMIT 1 OFFSET 2, where OFFSET is n minus 1. Always mention the tie behaviour - that is what the panel is testing.
Q: What is the difference between GROUP BY and a window function in SQL?
GROUP BY collapses rows: ten rows for one department become a single output row, and you lose access to the individual rows. A window function computes an aggregate over a set of rows but keeps every row in the output - SELECT name, salary, AVG(salary) OVER (PARTITION BY dept_id) AS dept_avg FROM employees returns one row per employee with the department average attached. That is why window functions are the natural tool for running totals, rankings, and comparing a row against its group, all of which come up in banking reports.
Q: What is the difference between an INNER JOIN and a LEFT JOIN?
An INNER JOIN returns only rows where the join condition matches on both sides. A LEFT JOIN returns every row from the left table, filling the right table’s columns with NULL where there is no match - so it is how you find customers with no transactions, using LEFT JOIN transactions t ON c.id = t.customer_id WHERE t.customer_id IS NULL. A common trap is putting a condition on the right table in the WHERE clause instead of the ON clause: a WHERE filter on the right table’s columns silently discards the NULL rows and turns your LEFT JOIN back into an INNER JOIN.
Q: Explain abstraction and encapsulation with an example.
Encapsulation is bundling data with the methods that operate on it and restricting direct access to that data - a BankAccount class keeps balance private and exposes deposit() and withdraw(), so no outside code can set a negative balance. Abstraction is exposing only the essential behaviour and hiding the implementation - a PaymentMethod interface declares pay(amount) while UpiPayment and CardPayment implement it differently. In short, encapsulation hides data behind access control, abstraction hides implementation behind a contract; encapsulation is a how-to-protect mechanism, abstraction is a what-to-expose design decision.
Q: What is the difference between compile-time and runtime polymorphism?
Compile-time polymorphism is method overloading - several methods share a name but differ in parameter list, and the compiler picks one from the argument types, so transfer(int) and transfer(int, String) are resolved before the program runs. Runtime polymorphism is method overriding - a subclass redefines an inherited method, and the JVM picks the implementation from the object’s actual type at execution time. So Account a = new SavingsAccount(); a.calculateInterest(); runs the SavingsAccount version even though the reference type is Account. Overriding requires an identical signature; overloading requires a different one.
Q: What are ACID properties, and why do they matter in a banking application?
ACID describes the guarantees a database transaction gives. Atomicity means all statements in a transaction succeed or none do - in a fund transfer, the debit and the credit either both land or neither does. Consistency means the transaction moves the database from one valid state to another, respecting constraints such as a non-negative balance. Isolation means concurrent transactions do not see each other’s partial work, which prevents two simultaneous withdrawals from both reading the same stale balance. Durability means once the transaction commits, the change survives a crash because it is written to a persistent log. Banking is the canonical ACID use case precisely because a half-applied transfer is unacceptable.
Frequently asked questions about HDFC Bank interviews
Section titled “Frequently asked questions about HDFC Bank interviews”What is the HDFC Bank interview process for freshers?
HDFC Bank’s Technology Analyst / SDE process typically runs 4 stages: 1. Online Assessment (90-120 min) - aptitude (numeracy, logical ability, language proficiency) plus a coding/technical section. 2. Technical Round 1 (45-60 min) - DSA, OOPs, and SQL. 3. Technical Round 2 (45-60 min) - projects and domain discussion, sometimes a group discussion at campus drives. 4. HR / managerial round(s) (20-30 min each) - some reports describe this stretching into a hiring-manager round plus a final senior-leadership discussion. Total duration is roughly 2-4 weeks, a bit longer if the extra leadership round is added.
What questions are asked in HDFC Bank interviews?
Coding rounds lean on stack/hashing problems (valid parentheses, find duplicates in a stream) and SQL (joins, window functions, nth-highest queries). Technical rounds also probe Java, JavaScript, and frameworks like Spring Boot or React for engineering roles, plus a detailed walkthrough of your strongest project. Domain conversation centers on HDFC Bank’s banking apps and how they’d hold up at scale.
How many rounds are there in the HDFC Bank interview?
Most fresher drives run 4 stages: Online Assessment, Technical Round 1, Technical Round 2, and HR. Some reports describe an additional layer for experienced or off-campus hires - an HR screening call, a technical/functional round, a mixed technical+behavioral round with the hiring manager, and a final senior-leadership discussion. Check your specific drive’s structure with the placement cell or recruiter.
What is the HDFC Bank technical interview like?
Technical Round 1 (45-60 min) mixes a DSA coding problem - candidates report stack-based problems like valid parentheses, and hashing problems like finding duplicates in a stream - with OOPs and SQL fundamentals. Technical Round 2 shifts into a detailed project discussion (architecture, hardest bug, what you’d rebuild) plus domain questions about HDFC Bank’s banking apps, explained in plain language rather than buzzwords.
How should I prepare for HDFC Bank interviews?
Practise LeetCode-medium DSA and timed SQL queries (joins, window functions) since both open the technical rounds. Revise OOPs, and be ready to discuss Java, JavaScript, or frameworks like Spring Boot/React if the JD lists them. Prepare one detailed project story and a plain-language explanation of banking-app concepts - a coherent explanation beats a high CGPA with weak communication.
What mistakes do candidates commonly make in HDFC Bank interviews?
Coding before clarifying constraints, treating the HR round as a formality, and reaching for system-design jargon without a simple, concrete story. Candidate reports consistently note that connecting your project work to HDFC Bank’s world (banking apps, SQL-heavy systems) lands better than generic answers.