ICICI Bank's tech interviews are heavier on SQL and core Java than most product companies, with a distinct emphasis on banking domain knowledge: think UPI reconciliation flows, CBS integration, and idempotency in payment APIs.
The process runs 3 to 4 rounds and is tighter than HDFC's in terms of SQL complexity. Candidates who can explain exactly how a NEFT transaction commits and rolls back have a visible edge over those who only practice LeetCode.
About ICICI
ICICI Bank is India's second-largest private sector bank, offering retail and corporate banking, insurance, asset management, and securities. Its tech team (iWork) is one of the largest banking IT organisations in India.
Resume screen: campus drives, job portals, or internal referrals
Online Assessment: aptitude, SQL problems, and 2 coding questions (easy to medium, 90 min)
Technical Round 1: Java, data structures, SQL deep-dive, and REST API concepts
Technical Round 2 or System Design: BFSI system architecture, transaction handling, and domain knowledge
HR Round: background verification, compensation, and behavioral questions
Online Assessment (90 min)
aptitude, 2 to 3 SQL problems with joins and aggregations, and 2 medium coding problems; SQL is harder than most banks.
Technical Round 1 (45 to 60 min)
Java collections and concurrency, OOP design, database indexing, and 1 live coding problem on arrays or strings.
Technical Round 2 or System Design (45 to 60 min)
design a UPI payment service or reconciliation engine, with specific attention to idempotency and rollback.
HR Round (30 min)
competency questions, notice period, and compensation alignment.
Sourced from 2+ candidate post-mortems. Hit Practice to answer any one with AI voice feedback.
2 more questions. Sign up to unlock all
Sign up free: unlock all questionsThe typical ICICI recruitment process has 5 stages: Resume screen: campus drives, job portals, or internal referrals → Online Assessment: aptitude, SQL problems, and 2 coding questions (easy to medium, 90 min) → Technical Round 1: Java, data structures, SQL deep-dive, and REST API concepts → Technical Round 2 or System Design: BFSI system architecture, transaction handling, and domain knowledge → HR Round: background verification, compensation, and behavioral questions.
ICICI typically conducts 4 interview rounds: Online Assessment (90 min): aptitude, 2 to 3 SQL problems with joins and aggregations, and 2 medium coding problems; SQL is harder than most banks.; Technical Round 1 (45 to 60 min): Java collections and concurrency, OOP design, database indexing, and 1 live coding problem on arrays or strings.; Technical Round 2 or System Design (45 to 60 min): design a UPI payment service or reconciliation engine, with specific attention to idempotency and rollback.; HR Round (30 min): competency questions, notice period, and compensation alignment..
HireStepX recommends the Transaction-safety design framework for this type of interview: Frame every system design around idempotency, two-phase commit trade-offs, and audit log completeness before moving to scale.
To answer this question well, HireStepX recommends the Transaction-safety design approach: Frame every system design around idempotency, two-phase commit trade-offs, and audit log completeness before moving to scale. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Transaction-safety design approach: Frame every system design around idempotency, two-phase commit trade-offs, and audit log completeness before moving to scale. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Transaction-safety design approach: Frame every system design around idempotency, two-phase commit trade-offs, and audit log completeness before moving to scale. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Transaction-safety design approach: Frame every system design around idempotency, two-phase commit trade-offs, and audit log completeness before moving to scale. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Transaction-safety design approach: Frame every system design around idempotency, two-phase commit trade-offs, and audit log completeness before moving to scale. Ground your answer in a specific real example from your own experience.