Citi interview process (2026)
Round-by-round breakdown of the Citi software engineering interview across 4 levels and 19 rounds: what each round covers, what interviewers evaluate, sample questions, and preparation tips.
Technology Analyst (Campus / New Grad)
Difficulty: Medium · Timeline: ~2-4 weeks · Recommended prep: 4-6 weeks
-
Round 0: Online Assessment (AMCAT / HackerRank)
Assessment · ~2 hours · difficulty 2/5 · elimination round
Focus: Quantitative aptitude, logical reasoning, technical MCQs, DSA coding
Proctored campus screen, usually on AMCAT (some cycles use HackerRank/HackerEarth). Reported pattern: ~16 quant questions (time-and-work, profit-loss), ~14 logical reasoning, ~20 technical MCQs (predict-the-output, time complexity, OOPs) and 2 coding questions in your language of choice. Coding is easy-to-medium: strings, arrays, trees, backtracking; one campus cycle even saw a max-flow style pipeline problem. Heavy filter: in one drive 654 applicants were cut to 129 after this round.
What they evaluate: Speed and accuracy across aptitude sections plus the ability to fully solve at least one coding problem. Partial scores on coding count, but clean MCQ accuracy (no negative marking, all mandatory) decides the shortlist.
Sample question: Given a string S and an index k, reverse only the portion of S from index k to the end and print the resulting string. Example: S = citibank, k = 4 -> citiknab.
Tips: Drill aptitude under time pressure (IndiaBix-style sets) — most rejections here are aptitude, not coding. For MCQs revise output-prediction in C/Java and Big-O of common snippets. In coding, bank an easy full solve before attempting the harder question.
-
Round 1: Technical Interview I
Onsite · ~30-45 min · difficulty 2/5 · elimination round
Focus: DSA basics, Java/OOPs, DBMS, projects, logic puzzles
Panel of two (often one technical + one HR-adjacent). Resume and project walkthrough, then fundamentals: overloading vs overriding, Java Collections, HashMap vs Hashtable, ACID and transactions, pointers in C/C++. Expect 1-2 logic puzzles and occasionally a short live-coding exercise on stacks or linked lists.
What they evaluate: Clarity on core CS fundamentals, honest depth on your own projects, and structured thinking on puzzles. They probe whatever languages your resume claims, so only list what you can defend.
Sample question: Given a string containing the characters ( ) [ ] { }, check whether the brackets are balanced using a stack. Print "balanced" or "not balanced".
Tips: Prepare a 2-minute walkthrough of your best project with one concrete technical decision you made. Revise OOPs pillars with Java examples and ACID with a bank-transfer example — it lands well at a bank.
-
Round 2: Technical Interview II (select cycles)
Onsite · ~30 min · difficulty 2/5
Focus: SQL joins and nested queries, OOPs depth, time complexity
Some campuses and the off-campus Technology Analyst graduate programme run a second technical round. Focus shifts to SQL (joins, nested queries, GROUP BY), exception handling in Java, time-complexity analysis, and a deeper dive into one project. Chennai typically hires Software Developer roles and Pune Technical Analyst roles; preference is asked here.
What they evaluate: Whether you can write correct SQL on paper and reason about complexity without hand-waving. Consistency with what you said in the previous round matters — panels compare notes.
Sample question: Employees(id, name, dept_id, salary). Write a SQL query to fetch the second-highest salary in each department, along with the department id. Explain how your query handles departments with a single employee.
Tips: Practice the classic SQL set: second-highest salary, duplicate emails, department-wise top-N with window functions. Say the words ROW_NUMBER and DENSE_RANK — interviewers reward knowing both the subquery and window-function forms.
-
Round 3: HR Round
Behavioral · ~10-15 min
Focus: Introduction, motivation, relocation, offer formalities
Short and friendly: introduction, hobbies, why Citi, family background, willingness to relocate among Pune/Chennai/Bangalore, and your questions. Results are usually declared within a week; in one drive 37 of 52 finalists received offers.
What they evaluate: Communication and genuine interest in a banking-technology career. Not a real filter at this stage unless you show disinterest or location rigidity.
Tips: Have one concrete reason why fintech/banking tech interests you (scale of payments, regulatory-grade engineering). Keep it short — this round often runs under ten minutes.
Officer — Software Engineer (2-5 yrs)
Difficulty: Medium · Timeline: ~3-5 weeks · Recommended prep: 6-8 weeks
-
Round 0: Recruiter Screen
Phone · ~20 min · elimination round
Focus: Resume walkthrough, tech stack, notice period, location
Call from Citi TA or a partner agency. Resume walkthrough, primary stack (Java/Spring dominates Citi India, with some Python/C# teams), current and expected CTC, notice period, and preferred location among Pune, Chennai, Bangalore and Gurgaon. Officer (C10-C11 grade) maps to roughly 2-5 years of experience.
What they evaluate: Stack fit for the specific team (most Citi India openings are Java/Spring/Oracle or Kafka-based platforms) and logistics: notice period under 60 days is a real advantage.
Tips: Lead with your Java/Spring depth even if your current role is polyglot. Ask which business line the role sits in (ICG/markets, cards, treasury) — prep differs and asking signals seriousness.
-
Round 1: HackerRank Online Assessment
Assessment · ~90 min · difficulty 3/5 · elimination round
Focus: Arrays, strings, hashing, SQL, Java MCQs
Timed HackerRank (some teams use Codility): typically 2 coding problems at LeetCode-medium level — array manipulation, string processing, prefix sums, hashing — plus MCQs on Java, basic SQL, and occasionally concurrency reasoning. Edge-case handling is scored, not just happy-path output.
What they evaluate: Both problems fully passing hidden test cases is the safe bar. Reviewers also look at code hygiene when scores tie — naming and decomposition matter more here than at product companies.
Sample question: You are given N daily transaction amounts (can be negative for reversals) and a target K. Count the number of contiguous subarrays whose sum equals exactly K. N up to 10^5, so an O(N) approach is expected. Input: N K, then N integers. Output: the count.
Tips: Grind the LeetCode medium band on arrays/strings/hashmaps; Citi rarely goes into DP-hard territory. Read constraints first — an O(N^2) brute force that passes samples but times out on hidden cases is the most common failure reported.
-
Round 2: Technical Round I — Core Java + DSA
Onsite · ~60 min · difficulty 3/5 · elimination round
Focus: Core Java internals, collections, multithreading, live coding
Virtual round with senior engineers. Core Java depth: HashMap internals and resizing, ConcurrentHashMap vs synchronized collections, equals/hashCode contract, immutability, streams vs loops, thread pools and producer-consumer. Then a live coding problem in a shared editor — cache design, string/array manipulation, or implementing a small data structure end to end.
What they evaluate: Production-ready code, not just a working sketch: they push on edge cases, complexity, and how your solution behaves under concurrent access. Java internals questions separate genuine experience from interview prep.
Sample question: Implement an LRU cache with O(1) get and put. First line: capacity and number of operations Q. Each of the next Q lines is either "GET k" (print the value or -1) or "PUT k v". Discuss what changes if multiple threads access the cache.
Tips: Be fluent on HashMap + doubly-linked-list composition and say LinkedHashMap exists in Java — interviewers at Citi explicitly reward knowing the standard-library shortcut and when not to use it. For the concurrency follow-up, mention striped locks or Caffeine rather than synchronizing every method.
-
Round 3: Technical Round II — Spring Boot + Design Basics
Onsite · ~45-60 min · difficulty 3/5
Focus: Spring Boot, REST API design, microservices, SQL, DB modeling
Backend engineering round: Spring Boot annotations and bean lifecycle, REST API design (versioning, idempotency, error contracts), microservices vs the monolith you maintain, Kafka basics on some teams, SQL joins and indexing, and schema design for a small banking scenario. Naukri/Code360 reports describe this as the second of two technical rounds before the managerial round.
What they evaluate: Whether you can design a clean service boundary and defend it: transaction handling, idempotent retries, validation layering. SQL is checked for real fluency — expect to write a join with aggregation live.
Sample question: Design the REST API for an internal funds-transfer service: endpoints, request/response bodies, status codes, and how you guarantee a transfer is not executed twice when the client retries after a timeout. Sketch the tables you would need.
Tips: Bring the word idempotency-key into the transfer-API answer along with a unique constraint at the DB layer — it is the exact follow-up most reports mention. Revise @Transactional propagation levels; it is a Citi favourite.
-
Round 4: Managerial + HR Round
Behavioral · ~30-45 min · difficulty 1/5
Focus: Project ownership, incidents, agile process, compensation
Hiring manager (sometimes with a client-team lead as a fourth round) covering ownership of past deliveries, a production incident you handled, working with QA/BA in agile ceremonies, and why you are leaving. Ends with or is followed by an HR call on compensation and joining date.
What they evaluate: Reliability signals: do you take ownership of failures, communicate risk early, and function in a regulated, process-heavy environment. Overclaiming on incidents gets probed hard.
Tips: Prepare two STAR stories: one production incident with your specific role in resolution, one conflict with a stakeholder. Citi managers ask compliance-adjacent situationals — never improvise an answer that bends process.
AVP — Senior Software Engineer
Difficulty: Medium · Timeline: ~4-6 weeks · Recommended prep: 6-8 weeks
-
Round 0: Recruiter Screen
Phone · ~20-30 min · elimination round
Focus: Experience mapping, grade fit, logistics
AVP (C12 grade) at Citi India maps to roughly 6-10 years of experience. The recruiter validates hands-on coding (AVP here is still an individual-contributor senior engineer, not a manager), team-leading exposure, stack alignment, and CTC band. Glassdoor pegs the AVP funnel at ~43 days end to end, so expect a slower pipeline than startups.
What they evaluate: Grade fitment: enough experience for C12 without being priced out, plus evidence you still code daily. Mentorship or small-team leadership is a plus, not a requirement.
Tips: State clearly that you are hands-on — Citi rejects AVP candidates who present as pure people-managers. Negotiate grade (C12 vs C11) at this stage; it is nearly impossible to change after the loop starts.
-
Round 1: Coding Screen (HackerRank or Live)
Assessment · ~60-90 min · difficulty 3/5 · elimination round
Focus: DSA at LeetCode-medium, code quality, edge cases
Either a HackerRank test or a live pairing session depending on the team. Difficulty stays at LeetCode-medium — arrays, intervals, hashing, occasionally a small design-flavoured implementation. Seniors are judged more on code structure, naming, and testing instincts than on algorithmic tricks.
What they evaluate: Clean, defensible code under time pressure. At AVP level an unfinished-but-well-structured solution with articulated trade-offs can pass; sloppy passing code often does not.
Sample question: You receive settlement windows as intervals [start, end] from multiple upstream systems. Merge all overlapping intervals and return the consolidated list sorted by start time, then state the total time covered. Walk through complexity and how you would unit-test it.
Tips: Narrate your invariants while coding — silent seniors get marked down for collaboration. Finish with a quick pass listing the unit tests you would write; several AVP reports say this is what interviewers remember.
-
Round 2: Technical Panel — Java + Architecture Deep Dive
Onsite · ~60 min · difficulty 4/5
Focus: JVM, concurrency, Kafka, microservice patterns, resiliency
Senior panel drills into the systems you have actually built: JVM memory tuning and GC choice, executor sizing, ConcurrentHashMap vs locks, Kafka consumer-group semantics and exactly-once trade-offs, circuit breakers and retries, transaction management across services, and database scaling on Oracle/PostgreSQL. Expect follow-the-thread questioning off your resume rather than a fixed script.
What they evaluate: Depth over breadth: they keep drilling until they find your floor. Claiming Kafka or multithreading on the resume without production war stories is the most cited rejection reason at this level.
Tips: Pick your two deepest systems and rehearse the numbers: TPS, latency, data volumes, failure modes. When you hit the edge of your knowledge, say so and reason from first principles — bluffing is fatal with this panel.
-
Round 3: System Design Round
System_design · ~60 min · difficulty 4/5
Focus: HLD, banking-grade reliability, auditability, data consistency
Design a mid-scale banking system end to end: a payment-status notification service, breaking a legacy monolith into microservices, or a reconciliation pipeline. Citi-specific emphasis: auditability (every state change traceable), strong consistency for money movement, idempotency, DR strategy, and coexisting with legacy mainframe/Oracle systems rather than greenfield NoSQL fantasy architectures.
What they evaluate: Pragmatism in a regulated environment: correct consistency choices for money paths, an audit trail in the design unprompted, and honest capacity estimates. Buzzword architectures without failure-mode analysis fail this round.
Sample question: Design a service that ingests payment status events from 4 legacy systems (file drops + MQ) and exposes a consistent, audited status API to internal apps, handling out-of-order and duplicate events. Cover storage choice, ordering, idempotency, reconciliation, and how auditors can replay history.
Tips: Say audit trail and idempotency before being asked — bank interviewers listen for them. An event-sourced or append-only ledger design with a read model lands very well here; also address dedupe keys for the duplicate-event case.
-
Round 4: Managerial Round
Behavioral · ~45 min · difficulty 1/5
Focus: Situational leadership, delivery, stakeholder management
Hiring manager, in India sometimes a panel of up to five, on situational and leadership questions: driving delivery with offshore/onshore splits, handling an audit finding or compliance deadline, mentoring juniors, disagreeing with a product owner. Glassdoor rates the overall AVP loop 3.3/5 difficulty with ~60% positive experience.
What they evaluate: Judgment under regulatory constraints and the ability to lead without authority. They test whether you escalate appropriately — both failing to escalate and escalating everything are marked down.
Tips: Prepare a story where you pushed back on a deadline for a risk/compliance reason and one where you delivered anyway by descoping. Panels of five feel intimidating — address the questioner but sweep eye contact across everyone.
VP — Engineering Lead
Difficulty: Medium · Timeline: ~6-8 weeks · Recommended prep: 8+ weeks
-
Round 0: HR / Recruiter Discussion
Phone · ~30 min · elimination round
Focus: Role scoping, leadership vs IC mix, grade and CTC band
VP (C13) in Citi India tech typically means 10-15 years of experience leading a team or owning a platform while staying technical. The recruiter scopes whether the role is lead-IC or people-management heavy, validates domain exposure (payments, markets, risk, cards), and sets CTC expectations. VP loops average ~43 days and often run 4-5 conversations.
What they evaluate: Seniority calibration and domain adjacency — banking or fintech domain experience materially improves VP conversion at Citi.
Tips: Get the role charter in writing: team size, systems owned, and whether you carry delivery or architecture accountability. VP roles vary wildly between Citi business lines and prep should match the charter.
-
Round 1: Technical Round with Senior Engineers
Onsite · ~60 min · difficulty 3/5
Focus: Hands-on coding judgment, architecture of past systems
Yes, VPs still get technical rounds at Citi. Senior engineers walk through a system you owned, then test hands-on judgment: reviewing a flawed code snippet, reasoning about a concurrency bug, API contract design, or a compact coding exercise. Depth expectations are calibrated to leadership scope but hand-waving architecture without implementation grounding is a rejection pattern.
What they evaluate: Whether your technical depth survived your management years: can you still spot the race condition, question the index choice, and make implementation-level trade-offs credibly.
Tips: Refresh core Java/SQL even if you have not coded daily — reports consistently mention VP candidates being asked implementation-level questions. Bring one system where you personally made a low-level call that mattered.
-
Round 2: Architecture + System Design Review
System_design · ~60-75 min · difficulty 4/5
Focus: Enterprise architecture, resiliency, DR, compliance, migration
Design at organizational scale: multi-region resiliency and DR for a payments platform, migrating a mainframe-adjacent estate to cloud (Citi runs large modernization programs), data-residency and regulatory constraints across jurisdictions, capacity planning, and vendor/build-vs-buy calls. Auditability and controlled change management are recurring themes.
What they evaluate: Architecture with a cost, risk and compliance lens — not just boxes and arrows. Strong answers sequence a migration with rollback points and quantify blast radius; ivory-tower target-state diagrams without a path fail.
Sample question: You own a core settlement system running on-prem with an Oracle backend and strict RPO of zero for money movement. Lay out a 3-phase plan to make it resilient across two regions, including data replication choice, failover decisioning, what you would never automate, and how you prove RPO/RTO to regulators.
Tips: Anchor on RPO/RTO numbers early and distinguish money-movement paths (sync replication, manual failover approval) from read paths (async, automated). Mentioning regulator evidence — DR test reports, replay logs — signals real banking scar tissue.
-
Round 3: Hiring Manager + Managerial Panel
Behavioral · ~60 min · difficulty 2/5
Focus: Tech leadership situationals, delivery, people management
Director-level hiring manager, in India often a panel, on leadership situationals: turning around a failing delivery, managing a senior underperformer, handling audit findings, balancing feature pressure against tech debt in a regulated codebase, and cross-region team coordination (India teams partner with NY/London/Singapore). Expect deep probing on team scale and what you personally drove versus inherited.
What they evaluate: Evidence of outcomes you personally caused, people judgment, and comfort operating inside heavy process. Inflated team sizes and borrowed wins get exposed by follow-up questions.
Tips: Quantify every leadership claim: team size, attrition you reduced, release cadence improvement, audit findings closed. Prepare a crisp answer for why bank pace instead of a startup — they genuinely filter on it.
-
Round 4: Senior Stakeholder + Fitment Round
Other · ~30-45 min · difficulty 1/5
Focus: Org fit, cross-line stakeholder view, compensation
Final conversation with a senior director or business-line stakeholder (sometimes from the global team, scheduled across time zones): org fit, how you would work with risk/compliance partners, and vision for the platform. Followed by HR on compensation — Citi India VP offers combine base, bonus and deferred stock, and the grade band is fairly rigid.
What they evaluate: Executive communication: can you explain technical strategy to a non-engineer in five minutes. This round rarely rejects on skills but does reject on arrogance or misaligned expectations.
Tips: Prepare a five-minute non-technical narrative of your best platform win framed as business impact. On comp, negotiate the bonus target and joining bonus — base bands at a given Citi grade have little flex.
Other companies' interview processes
Worked sample solutions (code, design diagrams, and STAR answers) for every round are available in the FAANGPlus app: open interview processes.