Skip to content
Interview Questions

ICICI Bank Interview Experience 2026

Overview

How ICICI Bank fresher interviews usually run depends on the track: Deputy Manager II / Technology Graduate Trainee campus loops lean resume + CS fundamentals (+ light coding), while PO tracks emphasise aptitude, GD, and PI. Foresight and premium campus drives can add case or leadership flavour. Treat this as a prep map, not a script - confirm your role from the placement mail.

How ICICI Bank differs from product-company campus loops

  • Role family matters: Deputy Manager / TGT tech panels are not the same as PO aptitude + GD + PI.
  • Coding depth varies by track - many campus tech reports emphasise fundamentals and projects over hard contests.
  • Banking awareness and communication still decide PO and some managerial closes.
  • Premium/Foresight drives can add case or leadership flavour beyond a standard DM-II loop.

Round-wise process

Round Duration What they test Notes
Online Assessment 60-90 min Aptitude + technical MCQs; DM-II: CS breadth (OS, DBMS, CN, cloud, output prediction) HackerEarth or home proctoring reported
Psychometric / video (some drives) 30-40 min Personality fit, situational MCQs Reported at IIT KGP Foresight-style drives
Group Discussion (many PO campuses) 15-20 min Communication, banking current affairs May be skipped on some tech drives
Technical / Banking interview 45-60 min DSA, SQL, OOP, projects, banking application Tech GT: stack/hash/SQL common
HR / combined panel 20-45 min Why ICICI, relocation, products, behavioural DM-II often merged with technical

Real interview experiences

Published ICICI write-ups cluster around the on-campus Deputy Manager II technology role rather than a classic SDE ladder, and they agree on a short funnel: an MCQ online test, then a single combined technical + HR conversation. Both accounts below are rewritten from public student posts, including the ones that ended in a rejection - those are usually the more useful ones.

Experience 1: Deputy Manager II, on-campus (NIT Patna, 2024)

Reported round 1 - online test

  • 50 MCQs in 60 minutes, taken from home.
  • Breadth over depth: information management, object orientation, computer networks, security, cloud computing.
  • Several questions were predict the output on short snippets, and the languages rotated - Python (including pandas/NumPy-style table filtering), Java, JavaScript and R all appeared.

Reported round 2 - technical + HR, one combined panel

  • Two interviewers on the panel. It opened with background and family, not with code.
  • Most of the time went to the project: what it does, and specifically how it would apply in a banking context.
  • Interest areas (ML/AI) were probed, plus a check on whether the candidate knew ICICI’s products and services.
  • Closed on relocation: are you willing to work anywhere in India?

Reported outcome: Not selected. The write-up attributes it to naming only two preferred cities instead of showing flexibility - ICICI hires for a branch-and-office network, and location rigidity is a real filter here, not a throwaway question.

Takeaways

  • What decided it (negative): Location flexibility and banking-context project framing mattered as much as CS MCQs
  • Common fail: Treating relocation as a soft HR formality
  • How to practise: One banking application story per project; rehearse open-location answers honestly

Experience 2: Deputy Manager II, on-campus

Reported flow: resume screening → online test → technical + HR in one 30-minute round.

  • Online test: 30 MCQs in 90 minutes on HackerEarth. Pseudocode, DBMS, computer networks, OS, C++, Java, R, Python, cloud, plus some data-science/ML questions.
  • Interview: deliberately foundational - write a program for the Fibonacci series, interpreter vs compiler, what OOP is and its pillars. Then “Why ICICI?” and “What motivates you?” in the same sitting.
  • Reported outcome: Not selected.

Takeaways

  • What decided it (negative): Foundational coding plus Why ICICI in a merged panel - hard DSA alone would not have changed the outcome
  • Common fail: Over-prepping contest problems while under-prepping Fibonacci-level warm-ups and motivation
  • How to practise: CS breadth MCQs; 10-minute fundamentals coding; Why ICICI with one product name

What the pattern suggests

  • The written stage is a wide CS-fundamentals sweep, not a DSA contest. Skimming OS/DBMS/CN and being able to trace code in an unfamiliar language pays more than grinding hard LeetCode.
  • Interview coding, when it appears, is fresher-level (Fibonacci, basic logic). The differentiators are the banking connection to your project, product awareness, and mobility.
  • Aptitude-led ICICI tracks (PO and similar) are reported separately as ~50 aptitude/reasoning/verbal questions plus a few psychometric questions answered on video - if your drive is a banking rather than technology role, expect that format instead.

Experience 3: Technology Graduate Trainee pattern (composite campus reports)

Reported flow: OA (aptitude + coding MCQs) → Technical Round 1 (45-60 min: valid parentheses, stream duplicates, SQL nth-highest/joins) → optional Technical Round 2 (projects + Java/API depth) → HR (20-30 min).

  • Coding: Stack for bracket matching; hashing for duplicate detection in streams - interviewers probe edge cases and complexity.
  • Domain: Plain-language explanation of retail banking tech, payment flows, or CBS integration beats jargon.
  • Project: Architecture, hardest bug, what you would rebuild; keep stack choices defensible.
  • HR: Why banking technology, background verification readiness, location flexibility.
  • Reported outcome: Selected candidates emphasise explaining trade-offs aloud over silent coding.

Takeaways

  • What decided it: Aloud trade-offs on stack/hash/SQL plus a banking-tech project story
  • Common fail: Silent correct code without complexity or edge-case narration
  • How to practise: Narrate every SQL join and DSA medium; map one project to retail banking tech

Experience 4: Foresight / premium campus drive (IIT KGP-style report, 2025)

Reported flow: Proctored online MCQ test (aptitude, ML, Python, JS, OOP, SQL, OS - ~45-60 min) → psychometric / behavioural test (~100 situational items) → single conversational panel (~30-35 min, no GD that year).

  • Panel covered introduction, CV walkthrough, banking current affairs, digital payments and UPI UX, stock-market basics at a high level, positions of responsibility, and a light sales situational prompt.
  • Tone reported as friendly; authenticity and structured answers mattered more than trick questions.
  • Takeaway: Prepare current affairs in banking and payments, not only DSA.

Experience 5: Probationary Officer (PO) track - aptitude + GD + PI

Reported flow (public PO write-ups): Online aptitude → Group Discussion on banking or current affairs → Personal Interview on banking basics (CRR/SLR, NPAs, KYC), customer handling, sales targets, relocation, and career goals.

  • Expect “Why banking?” and “Why ICICI over other banks?”
  • Technical banking questions at PO level: account types, cheque clearing basics, RBI role - not LeetCode hard.
  • Some programmes add video-recorded psychometric items before PI.

Takeaways

  • What decided it: GD clarity plus banking PI depth (CRR/SLR, KYC, customer handling), not LeetCode
  • Common fail: Using a DM-II tech script for a PO drive
  • How to practise: One mock GD; banking GK one-layer deeper than definitions

Round structure varies by role - trust your drive mail. Citation inputs for the experiences above are listed under Sources.

Pre-interview checklist

  • Read drive mail for merged vs split technical/HR and for psychometric/GD extras
  • One banking-in-context story for each resume project (fraud, payments, customer data)
  • SQL: joins, window functions, nth-highest; DSA: stack + hash warm-ups
  • Relocation answer prepared before panel - rigidity is a reported filter
  • Documents ready for background verification timeline questions in HR

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 retail banking tech and SQL, bottlenecks, failure modes, simple APIs
  5. Detailed project discussion, architecture, hardest bug, what you would change

HR / behavioural

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

Practical tips for ICICI Bank

  • Clear the screening round first. Timed practice beats last-minute topic hopping.
  • For domain questions, explain retail banking tech in plain language, inputs, outputs, what breaks at scale.
  • OOPs and SQL still open a lot of ICICI Bank panels. Do not skip fundamentals.
  • HR answers should be concrete. One story with a result beats five slogans.
  • If you do not know something, say so and outline how you would find out.

HR interview

After technical rounds, ICICI Bank usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.

Sample answers for high-frequency questions

Use these as frames, not scripts - interviewers probe follow-ups.

Q. How do you check whether an expression has valid parentheses?
A. Push every opening bracket onto a stack; on every closing bracket, pop and check that the popped bracket is the matching opener - if the stack is empty at that moment, or the pair does not match, the string is invalid. At the end the string is valid only if the stack is empty, which catches unclosed openers. This is O(n) time and O(n) space in the worst case where every character is an opener. Interviewers usually follow up with the mixed-bracket version covering round, square, and curly brackets, which you handle with a small map from closer to opener.

Q. How would you find duplicates in a stream of incoming data?
A. Maintain a hash set of the values seen so far; for each incoming element, if the set already contains it report a duplicate, otherwise insert it. That gives O(1) average time per element and O(n) space overall. If memory is the constraint - which is the realistic case for a transaction stream - a Bloom filter answers “definitely not seen” or “probably seen” in constant space per element at the cost of false positives, so it is used as a cheap pre-filter before a real lookup. If the values are bounded integers, a bit array or a counting array is faster and smaller than a hash set.

Q. Write a SQL query to find the nth highest salary.
A. The clean modern approach uses a window function: SELECT DISTINCT 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 is the right function rather than RANK or ROW_NUMBER because it gives tied salaries the same rank and does not skip the next number, which is what “nth highest distinct salary” means. The older portable form for the second highest is SELECT MAX(salary) FROM employees WHERE salary < (SELECT MAX(salary) FROM employees); Always mention the NULL case - if fewer than n distinct salaries exist, the query returns no row.

Q. What is the difference between a window function and GROUP BY?
A. GROUP BY collapses rows: after grouping by department you get one row per department, and the individual employee rows are gone. A window function computes across a set of rows defined by an OVER clause but keeps every original row, so you can show each employee alongside their department average in the same result. For example, AVG(salary) OVER (PARTITION BY dept_id) attaches the department average to every employee row without a self-join or subquery. That is why window functions are the idiomatic tool for running totals, rankings, and row-versus-aggregate comparisons - all common in banking reporting queries.

Q. What is a core banking system, and why is it architecturally significant?
A. A core banking system, or CBS, is the central platform that holds the customer and account master data and posts every debit and credit to the general ledger - Finacle and Flexcube are two widely used examples in Indian banking. Every other channel (net banking, the mobile app, ATMs, UPI, branch teller software) is a front end that ultimately calls into the CBS to move money. It matters architecturally because it is the single source of truth for balances, so it must be strictly ACID-compliant, and because it typically runs end-of-day batch processing for interest accrual, charges, and reconciliation. Modern designs put an API or middleware layer in front of it so channels do not couple directly to the core.

Tips from successful candidates

Assessment tips

  • Confirm the current ICICI Bank pattern from the drive mail before practising old papers
  • Finish one problem or section fully before starting the next
  • Revise the fundamentals listed in the round table on this page

Interview tips

  • Narrate trade-offs; expect “why” after every answer
  • Only list projects you can defend under follow-ups
  • Prepare 3-4 STAR stories for behavioural prompts

HR tips

  • Know why ICICI Bank, not just why the industry
  • Be clear on location / notice period / higher studies
  • Practise answers on the dedicated HR page

Sources

These links are research inputs we used to map Deputy Manager II, TGT, Foresight, and PO patterns - not copied page mirrors. We reorganized reports into process notes, takeaways, and a prep checklist for ICICI Bank.

Cross-check your call letter or placement mail for the exact track. Aggregator summaries (including Glassdoor) vary widely by role.

For the company overview, see the ICICI Bank hub. For behavioural frames, use the HR page. For practice papers, see ICICI Bank placement papers.

ICICI Bank hub

HR interview questions

Placement papers

Preparation guide

Similar companies

HDFC Bank · Paytm · PhonePe · Razorpay · JP Morgan · Goldman Sachs