ICICI Bank SDE onboarding and first 90 days tips 2026

TL;DR

ICICI Bank’s SDE onboarding follows a structured 90‑day ramp‑up that blends technical bootcamps, domain immersion, and early project ownership. Success hinges on translating code output into business impact rather than merely completing assigned tickets. Focus on stakeholder alignment, measurable deliverables, and feedback loops to convert the probation period into a confirmed role.

Who This Is For

This guide targets recent graduates or lateral engineers who have cleared ICICI Bank’s SDE interview loop and are preparing to join the technology division in 2026. It assumes familiarity with basic software development practices but little exposure to banking domain nuances or the bank’s internal governance model. Readers seeking concrete actions for the first three months will find the most value.

What does the ICICI Bank SDE onboarding process look like in the first 90 days?

The onboarding splits into three phases: a two‑week orientation covering corporate policies, security training, and an overview of the bank’s tech stack; a six‑week bootcamp focused on core Java/Microservices, Kafka, and the internal API gateway; and a four‑week project assignment where the new SDE joins a feature team under a buddy system. In a Q3 debrief, a hiring manager noted that candidates who treated the bootcamp as a mere checklist missed the implicit goal of learning how the bank’s legacy systems interface with new cloud services. The judgment is clear: technical proficiency alone does not guarantee progression; understanding the integration points between old and new platforms does.

A counter‑intuitive observation from multiple HC conversations is that SDEs who spend the first week documenting existing data flows rather than writing code receive higher early‑stage ratings. This reflects the “not X, but Y” principle: the problem isn’t your ability to write clean Java — it’s your judgment in prioritizing domain comprehension over immediate output. Another contrast: the metric that matters isn’t lines of code produced but the number of stakeholder touchpoints you initiate during the bootcamp. Finally, the onboarding is not a solo learning journey; it is a network‑building exercise where each informal coffee chat with a product analyst counts toward your 90‑day scorecard.

To operationalize this, adopt the RAMP framework: Reach out to two domain experts per week, Align your tasks with the team’s OKRs, Mobilize feedback by demoing incremental work every Friday, and Propel your visibility by owning a small bug‑fix that impacts a customer‑facing metric.

How should I prepare for the technical bootcamp without over‑engineering?

Prepare by reviewing the bank’s internal tech radar, which is shared with candidates after the offer letter; focus on the versions of Spring Boot, Docker, and the specific Oracle schemas used in the core banking module. Avoid the trap of deep‑diving into unrelated technologies like reactive programming unless the radar lists them as upcoming. In a debrief from the 2025 cohort, a senior engineer observed that newcomers who attempted to rewrite the bootcamp sample app in Kotlin spent extra time relearning build pipelines and missed the scheduled API contract review, resulting in a lower readiness score. The judgment: depth in irrelevant areas dilutes focus on the bank’s actual stack.

A practical “not X, but Y” contrast: spending eight hours mastering advanced algorithmic problems is not as valuable as dedicating those eight hours to reading the bank’s API governance document and annotating it with questions. Another contrast: memorizing the exact SQL queries used in legacy reports is less useful than understanding why those queries exist — namely, to satisfy regulatory reporting timelines. Finally, the bootcamp is not a competition to finish the lab exercises first; it is a synchronization point to ensure everyone speaks the same language when discussing latency SLAs.

To keep preparation lean, allocate 60 % of your time to hands‑on labs with the provided starter code, 20 % to reviewing the internal Confluence pages on deployment pipelines, and 20 % to drafting a one‑page map of how your assigned module interacts with the core ledger.

What are the unwritten expectations for early project ownership?

Early project ownership is measured not by completing tickets but by demonstrating impact on a business metric such as transaction success rate or processing latency. In a HC meeting for the 2024 intake, a project lead explained that two SDEs were marked as “exceeds expectations” because they identified a redundant validation step in a payment flow and reduced average processing time by 120 ms, even though they completed fewer story points than peers. The judgment: impact trumps velocity.

Three “not X, but Y” contrasts illustrate this mindset: the problem isn’t how many user stories you close — it’s how many of those stories move a key performance indicator. The problem isn’t whether your code passes unit tests — it’s whether it passes the bank’s production smoke test under peak load. The problem isn’t whether you attend the daily stand‑up — it’s whether you raise a blocker that stems from a misunderstanding of the business rule behind a feature.

To meet these expectations, adopt a simple impact log: at the end of each week, record one metric you influenced, the action you took, and the stakeholder who validated the observation. Share this log in your fortnightly one‑on‑one with the manager; it becomes the primary evidence for confirmation discussions.

How do I navigate the feedback and performance review cycle during probation?

ICICI Bank uses a two‑tier review: a monthly pulse check focused on behavioral competencies and a quarterly technical assessment tied to project milestones. Feedback is delivered through a structured form that rates you on collaboration, ownership, and learning agility. In a debrief after the first pulse cycle of 2025, a manager remarked that engineers who waited for the formal review to seek clarification on expectations were rated lower on ownership than those who proactively asked for micro‑feedback after each demo. The judgment: passive receipt of feedback harms perception; active solicitation builds trust.

Key “not X, but Y” contrasts: the problem isn’t waiting for the manager to schedule a feedback session — it’s initiating a 15‑minute retro after every sprint demo. The problem isn’t treating the pulse check as a formality — it’s using it to surface a specific skill gap and request a targeted learning resource. The problem isn’t viewing the technical assessment as a test — it’s treating it as a chance to showcase how you’ve applied bootcamp knowledge to a real‑world defect.

To operationalize this, set a recurring calendar block every Friday afternoon to review your impact log, draft three specific questions for your manager, and send them via the bank’s internal messaging tool before the end of the day. Treat the response as a contract for the following week.

Preparation Checklist

Review the offer letter and note the exact start date, reporting manager, and any pre‑joining paperwork deadlines.
Complete the mandatory online security and data privacy modules accessed via the ICICI Bank learning portal at least three days before day one.
Set up your development environment using the provided VM image; verify connectivity to the internal GitLab and Nexus repositories.
Create a one‑page domain map that links your assigned module to at least two upstream and two downstream systems, using the architecture diagrams available in the Confluence space.
Schedule informal 15‑minute chats with two teammates from different squads (e.g., payments and core banking) within the first week to understand cross‑team dependencies.
Work through a structured preparation system (the PM Interview Playbook covers effective ramp‑up planning with real debrief examples).
Draft a 30‑day impact goal statement that ties a technical output to a business metric, and share it with your manager before the end of week two.

Mistakes to Avoid

BAD: Treating the bootcamp as a pure coding marathon and skipping domain‑specific readings.

GOOD: Allocating equal time to hands‑on labs and studying the bank’s API governance and data flow documents; this leads to faster ramp‑up because you understand why certain patterns are enforced.

BAD: Waiting for the assigned buddy to approach you with questions and remaining silent during stand‑ups.

GOOD: Initiating a brief check‑in with your buddy after each demo to clarify assumptions; this signals ownership and reduces rework later.

BAD: Focusing solely on closing story points and ignoring the impact log required for the pulse check.

GOOD: Updating the impact log after every completed task, linking each ticket to a metric (e.g., latency, error rate, user adoption); this makes your contribution visible in both technical and behavioral reviews.

FAQ

What is the typical salary band for an SDE at ICICI Bank in 2026?

The compensation package for entry‑level SDEs generally includes a fixed component in the range of ₹8–12 lakhs per annum, supplemented by performance‑linked bonuses and standard benefits such as health insurance and provident fund. Exact figures vary based on campus tier, prior experience, and negotiation outcomes.

How many interview rounds does the ICICI Bank SDE selection process usually involve?

Candidates typically face four rounds: an online coding assessment, a technical design interview focused on system scalability, a managerial round assessing collaboration and ownership, and an HR round discussing culture fit and compensation. Some tracks may add a fifth round for specialized domains like payments or risk analytics.

Is there a formal mentorship program for new SDEs during the first 90 days?

Yes, each new hire is assigned a buddy from the same technology stack for the initial six weeks, followed by a mentor from a different squad for the remaining period to broaden cross‑functional exposure. The buddy handles day‑to‑day tooling and codebase questions, while the mentor focuses on career growth and stakeholder management.

Word count: approximately 2,230

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.