Citi India Technology Analyst and related campus roles filter hard on the SHL OA, then probe projects and banking-flavoured DBMS. This page synthesizes PBWM, multi-round campus, and EIOT internship patterns into round tables, funnel notes, and prep traps.
How Citi technology campus loops differ from product startups
Bank technology analyst loops mix DSA with OOPs, SQL, and sometimes aptitude vendors (e.g. AMCAT patterns).
PBWM / EIOT / TA tracks are not identical - read the role name on the drive mail.
Regulatory and reliability framing can appear in “why banking tech” answers more than at consumer apps.
HR/managerial often probes stability, location, and client-facing composure after technicals.
Computer Programming MCQs: OOP in C/C++, searching/sorting, arrays/stacks/queues/trees
Coding (2 Q, 45 min total): (1) return array values in a given range; (2) sort by frequency
Sectional timers; no section switching; no negative marking
Candidate finished ~30 min early; both coding all tests passed
Round 2 - Techno-HR (~35 min, Zoom, two interviewers)
Intro + internship deep-dive (tooling explained with real-life analogies)
DBMS/SQL: Full Join; names starting with a given prefix; SQL vs NoSQL
Projects: Firebase vs MongoDB choices; translate some SQL to Firebase-style queries
Hobby/role-model chat; Why software role from electronics; Why Citi; 5-year plan
Comfort with legacy code
Result: Rejected (drive selected 4 CS students)
Key takeaways: OA coding is often easy-medium interval/frequency work - do not lose marks on verbal/quant pace. Interviews reward project justification and SQL comfort more than hard LeetCode.
Takeaways
What decided it: Full AC on range/frequency coding plus calm SQL and stack-choice answers in techno-HR (this account still lost to a CS-heavy select list)
Common fail: Finishing coding early then bleeding verbal/quant; soft answers on Full Join, SQL vs NoSQL, or Firebase vs MongoDB
How to practise: Timed SHL sections; code range filter + frequency sort; sketch join examples and one project stack defence with a banking consistency angle
Technical interview experience 2 - Citi India On-Campus 2023 (4 rounds)
Technical interview experience 2
Candidate profile: On-campus 2023 four-round loop (rejected). Source: GeeksforGeeks Citi India On-Campus 2023. Related VJTI accounts add SQL keys, ATM-ACID walkthrough, HTML/CSS on web projects.
Online Aptitude
Verbal, LR, Advanced Quants, 2 coding - easy to medium overall
Technical Round 1
Pure project focus (internship + course): tech-stack choices, features, cross-questions
Closed with Why Citi
No OOP/DBMS/OS/CN quiz in this particular panel
Technical Round 2
Favourite subject → DBMS normalisation
Scenario: one bank, one company; employees have many accounts - how many tables?
Coding: swap two numbers without a temporary variable (two approaches asked)
Situational: what do you hate about the corporate world?
HR Round
Project you are proud of; challenges faced
PPO from internship company?; relatives working at Citi?
Questions for interviewer
Final result: Rejected
Key takeaways: Have a crisp ERD answer for bank-customer-account modelling. Practise XOR / arithmetic swap and a honest corporate situational answer.
Takeaways
What decided it: Surviving a project-only Tech-1 then normalisation, bank/company ERD, and swap-without-temp in Tech-2
Common fail: No table sketch for multi-account modelling, or only one swap method when two approaches are asked
How to practise: Draw a 3NF bank-employee-account schema aloud; code arithmetic and XOR swaps; prep honest PPO/relatives/HR challenge answers
HR interview experience
HR interview experience
Reported prompts: proud project + challenges; PPO status; relatives at Citi; relocation; Why Citi / 5-year plan; legacy-code comfort. Keep answers factual - conflict-of-interest style relative questions are asked literally.
Round 1: AMCAT ~120 min - aptitude (quant, logical, verbal), technical MCQs (OOP, SQL, CS fundamentals), two coding problems in 60 minutes
Rounds 2-4: Offline interviews shortly after OA; results sometimes same day
Interview emphasis: projects, OOP, DBMS/SQL, lighter live coding than OA
Key takeaways: When your invite says AMCAT, prioritise sectional pacing on aptitude - coding alone does not shortlist you.
Sample answers for high-frequency questions
Q. SQL vs NoSQL - when each? A. SQL: fixed schema, joins, strong transactions - account ledgers, payments. NoSQL: flexible documents/key-value, horizontal scale - profiles, logs, rapidly changing product data. Tie answer to consistency needs in banking.
Q. Bank + company employees with many accounts - table sketch? A. Typical 3NF: Company, Employee (FK company), Account, Employee_Account (or Account.customer_id → Employee) depending on whether accounts are personal. State assumptions out loud - interviewers score modelling reasoning.
Q. Swap without temp - two approaches? A. Arithmetic: a = a + b; b = a - b; a = a - b (overflow caveat). XOR: a ^= b; b ^= a; a ^= b for integers. Prefer temp in production for readability/safety.
Q. Explain ACID with an ATM withdrawal. A. Atomicity: debit either fully happens or not. Consistency: balance rules hold. Isolation: concurrent ATM ops do not corrupt balance. Durability: committed withdrawal survives crash. Walk steps: card auth → balance check → debit → dispense.
Dense prep checklist
SHL verbal + quant pace; programming MCQs
Coding: range filter, frequency sort, swap without temp
SQL joins, Full Join, LIKE, normalisation, SQL vs NoSQL
These links are research inputs used to map Citi OA patterns, techno-HR themes, and campus funnels - not copied page mirrors. We reorganized them into process tables, outcome notes, and prep takeaways.
Confirm eligibility, role name (PBWM/ICG/EIOT), and OA vendor against the current PPT.
