Skip to content

Citi Placement Papers 2026

Citi is a global bank offering consumer banking, institutional trading, and corporate financial services across more than 160 countries. India technology centers in Pune, Chennai, Bengaluru, and Mumbai build banking platforms, risk systems, and digital products for global operations.


HQ: New York, USA
Employees: 200,000+
Revenue: $80B+
Website: citi.com ↗

Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career

Citi fresher eligibility for campus drives

Who this hub is for

  • For: Students targeting technology roles in Citi India (Pune, Chennai, Bengaluru) or analyst-style campus tracks where aptitude dominates.
  • Not the same track: Pure investment-banking associate case loops with DCF-heavy days if your JD is software; pure LeetCode if your JD is analyst aptitude.
  • Career switchers: IT/ECE profiles clear tech tracks when OA coding and SQL are real - CGPA helps the screen, it does not replace accuracy under time.

Good fit: You like timed tests, you can explain a payments or controls idea without buzzword soup, and you will complete OA within the window. Internships help; they do not replace passing sections cleanly.

Harder path: You copy a friend’s tech prep for an analyst drive (or vice versa); you ignore SQL; you refuse Pune/Chennai/Bengaluru relocation. Citi’s late-stage drops are often behavioral clarity and domain storytelling - not only one missed DP.

Tech vs analyst tracks

Track OA lean Interview lean Prep priority
Technology / SWE Coding + CS DSA, OOP, SQL, projects Java/Python + SQL
Analyst / business Aptitude + verbal Domain reasoning, fit Quant/LR/verbal + basics

Do not assume one Citi OA for all roles. Read the JD and invite.

Detailed eligibility criteria breakdown

Item Typical expectation (candidate-reported) Reality check
CGPA / % 7.0+ CGPA or 70% Higher helps; skills decide
Degree B.E./B.Tech/M.Tech/MCA or as per JD Full-time preferred
Year Final year or recent grad Drive-dependent
Backlogs None active preferred Clear before joining
Skills Aptitude, coding, finance domain Track-specific
Languages Java, Python, SQL Confirm invite

Selection chances by CGPA band

CGPA range Rough chances Reality check
Below 7 Low (on-campus) Off-campus possible with exceptional skills
7.0-7.4 Eligible Need strong OA
7.5-8.4 Solid Matches many selected stories
8.5+ Stronger shortlist odds Still loses if OA collapses

Academic requirements

Marks: 7.0+ CGPA or 70%

Degree: B.E./B.Tech/M.Tech/MCA or as per notification

Year: Final year students and recent graduates

Backlogs: No active backlogs preferred at joining

Skills & focus

Primary focus: Aptitude, coding, finance domain

Languages: Java, Python, SQL

Exam filter: Citi Online Assessment

On-campus vs off-campus

Route What usually changes What stays the same
Campus Batch OA window, PPT timing, CGPA list Track-specific bar
Careers / referral Resume volume; year-round Still expect OA + interviews
Tech vs analyst Entire OA flavour HR still checks fit/location

Off-campus does not mean easier tests. If your CGPA sits near 7.0, spend energy on mocks - not mythical cutoff blogs.

Branch myth: Non-CS students clear tech tracks when coding and SQL are real. Branch openness is permission to attempt, not a free pass.

Gap years and backlogs: active backlogs are a common hard stop. Cleared historical backlogs are often fine. Education gaps need a clean story.

Compliance awareness at fresher depth: know why banks care about access control, audit trails, and data handling. You do not need a law degree - you need not to shrug when HR asks about ethics.

India banking-tech context

Citi’s India centres support global banking technology at scale. Compared with product unicorns, expect more process formality and compliance talk. Compared with pure services staffing, expect a real coding/SQL bar on tech tracks. Compared with JP Morgan TA chatter, candidate-reported fresher bands for Citi often sit lower - compare total offers carefully, not brand alone.

Students who clear usually treat Citi like a bank that ships software: accuracy under time, clean SQL thinking, and calm behavioral answers. Prestige hunting without a banking-tech story underperforms in HR.

Who usually fits and who struggles

Good fit: You can sit a timed test without panicking, you like correctness over theatrics, and you are open to Pune, Chennai, or Bengaluru. You will learn enough banking vocabulary to sound like you understand why controls exist.

Harder path: You only want “fintech startup vibes” and resent process; you cannot explain a join; you treat compliance questions as HR fluff. Bank interviews notice dismissiveness quickly.

Internship signal: A backend or data internship helps tech tracks. A finance internship helps analyst tracks. Cross-over is fine when you can narrate transferable skills without forcing buzzwords.

India technology centre reality

Large India centres mean real software ownership and also real process. Expect background verification, structured HR, and less “move fast break things” language than consumer startups. If that culture fits you, say why. If it does not, do not fake it through six rounds.

Citi placement papers - last few years

Comments & Suggestions

What Citi previous year papers actually train

Citi papers are simulators for OA stamina and interview themes, not leaked live exams. Themes repeat more than exact clones. Track differences matter more here than at many product companies.

Round (typical) What to practice
Online Assessment Aptitude and/or coding by track
Technical DSA/SQL/CS or domain reasoning
HR Banking values, relocation, Why Citi

Themes that keep repeating (2024-2026)

  • 2024: Dual-track reality already clear - tech coding vs analyst aptitude; SQL shows up in tech interviews; compliance/fit language in HR.
  • 2025: Same shell with stricter timed execution; cleaner communication; more “controls and reliability” vocabulary in tech chats.
  • 2026: Continuity + polish; OA remains the volume filter; students still fail by using the wrong track’s prep plan.

Practice coverage on this site includes 2024-2026 prep. Patterns update from student-reported trends - trainers, not live leaked papers.

How to use a paper: time exactly as your invite; mark speed vs concept misses; rewrite solutions that fail hidden tests; then spend 15 minutes listing which pattern you missed. Three reviewed papers beat ten skimmed PDFs.

Across recent drives, coding families recombine more than they reinvent: searching, hashing, two pointers, and SQL-shaped logic. Aptitude families stay classic bank-style: percentages, ratios, data interpretation, logical puzzles, verbal reasoning. If those pillars are solid, “new pattern” rumours rarely change outcomes.

Year pages give theme depth; the PDF gives timed full runs. Use both. After each pack, force a spoken explanation once - interviews reward narration that OA alone does not train.

Campus vs off-campus in practice: on-campus means reserved seats and season alignment; off-campus means denser pools and year-round attempts. Technical content for a given track does not magically get easier off-campus.

Paper → interview bridge: after each timed pack, explain one answer aloud as if a panel asked “why this approach?”. Accuracy without narration fails interviews.

Sample mental model for OA triage

  1. Skim the full paper in 2-3 minutes
  2. Bank easy aptitude or easy coding marks first
  3. Protect accuracy - wrong rushes hurt more than students admit
  4. Leave hard items for a second pass
  5. Never let one stuck coding problem erase an entire section

Students usually say Citi’s first round is time-tight - easy marks vanish if you sit too long on one hard question. Languages people commonly use: Java, Python, SQL.

Coding / aptitude pattern cousins

Theme What to drill next
Arrays / searching Binary search, two pointers
Hashing Frequency maps, duplicates
SQL logic Joins, nth highest, indexes intuition
Quant aptitude Percentages, ratios, DI
Verbal / LR Bank-style critical reasoning

Citi placement process, round by round

Citi runs campus and off-campus hiring. Campus clusters with placement seasons; careers portal roles appear year-round. Same seriousness either way - track differences matter more than venue.

How to apply

Campus recruitment

Placement cell → PPT → OA → interviews.

Online applications

citi.com / Citigroup careers portals.

Referrals

Higher resume visibility; same OA bar.

Round-by-round walkthrough

  1. Resume screening (3-10 days)

    Academics (7.0+/70%), projects, internships. Put one quantified line on impact. For tech, mention SQL/Java/Python honestly.

  2. Citi Online Assessment (timed; platform varies)

    Tech tracks lean coding/CS; analyst tracks lean aptitude/verbal. Confirm sections on the invite. Clear rate chatter is steep enough to treat OA as the volume filter.

  3. Technical / case-style interviews

    Tech: DSA, OOP, DBMS/SQL, projects, light system design. Analyst: structured reasoning on business/finance prompts. Expect compliance-aware behavioral probes woven in.

  4. HR / offer

    Why Citi?, teamwork, ethics, location (Pune, Chennai, Bengaluru), CTC discussion (~₹12-22 LPA band in reports).

Timeline from application to offer

Phase Duration What happens
Resume Screening 3-10 days Shortlist
Online Assessment 1 day Track-specific test
Interview Scheduling 2-7 days Loop coordination
Technical rounds 1-2 weeks Depth interviews
HR 3-7 days Fit + offer
Offer Communication 1-5 days Written offer

Total: often 2-6 weeks for campus batches.

Fit questions that show up

  • “Tell me about a time you handled sensitive data or access carefully.”
  • “Describe a production bug or data issue you fixed.”
  • “Why banking technology / why Citi?”
  • “Are you open to Pune, Chennai, or Bengaluru?”

Use STAR with one metric. Avoid bluffing product names. Compliance answers should be concrete - what you did, not slogans.

What each early stage actually asks

  • OA tech: coding correctness under time; sometimes CS MCQs
  • OA analyst: quant, verbal, logical
  • Tech interview: SQL joins/indexes, OOP, DSA, projects
  • HR: values, relocation, motivation

If you only remember three numbers: track matters, OA is time-tight, fresher band ~₹12-22 LPA.

Timeline realism

Campus waves can compress OA and interviews. Off-campus can stretch. Keep skills warm during waits. Do not freeze practice for a week of status refreshing.

Sample tech interview walkthrough mindset

  1. Clarify the problem and constraints
  2. Offer a brute force, then improve
  3. Code cleanly with edge cases
  4. Discuss SQL schema or indexing if data-shaped
  5. Tie a project lesson to reliability or auditability when honest

If you stall, narrate what you would try next. Silence reads as panic; a partial plan with a clear ask reads as coachable.

Evaluation checklist students forget

Null inputs; off-by-one; explaining complexity; distinguishing primary key vs index; not dumping memorised ACID definitions without examples; answering ethics questions with a real story instead of a slogan.

Behavioral tabs students actually rehearse

Ownership: “Tell me about a project you owned end-to-end” - STAR with scope, decisions, trade-offs, quantified impact.

Problem solving: “Hardest bug or data issue” - diagnosis, alternatives, validation, what you would change.

Why Citi? Tie interests to global banking technology or analyst work and compliance-aware culture. Avoid generic brand-name answers.

Practice these out loud twice a week. Written bullets are not the same skill as spoken answers under a panel’s silence.

Citi aptitude, coding & interview practice

How to train for Citi this season

If a Citi invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.

Typical fresher CTC chatter for Citi sits around ₹12-22 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, Python, C, Go. Pick one and stay with it in OA and interviews.

Eligibility reminder (from student reports): Citi fresher eligibility (candidate-reported, August 2026): typically 7.0+ CGPA or 70%, relevant degree for technology or analyst tracks, no active backlogs preferred, and skills in aptitude, coding, SQL, and finance-domain awareness. Verify careers.citi.com or your campus JD.

What you are training for: Typical path: Online Assessment (aptitude and/or coding by track) → Technical or case-style interviews → HR. Some loops add managerial rounds. Timeline often 2-6 weeks for campus batches. Tech and analyst OA patterns differ - do not assume one paper for all roles.

Short version of the prep split: Match prep to track: tech leans coding/CS/SQL; analyst leans aptitude/verbal/finance awareness. Take weekly timed mocks, keep an error log, and rehearse STAR stories plus Why Citi with banking-tech specifics.

A four-week plan that actually gets used

Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the Citi previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.

Week 2 - the steep filter. Most Citi drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.

Week 3 - talk tracks. Technical interviews at Citi usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Citi?” with one concrete product, lab, or business line - not a slogan.

Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. If you still have energy, redo only the questions you failed in week 2.

Where the hours should go

Slice Share of weekly hours What “done” looks like
Timed papers / OA ~40% You finish a Citi-style sit without guessing the clock
Coding / role technical ~30% You can explain a solution out loud in your chosen language
Fundamentals / domain ~20% You can teach one OS/DBMS/networks (or domain) topic to a friend
Stories + HR ~10% Two STAR stories and a specific Why-this-company answer

If you only have 10 days, keep the same ratios and cut volume, not the timed sits.

Practice pages to open this week

Use this hub for the Citi story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.

Common ways students waste a month

  • Collecting 12 Citi PDFs and never sitting one under a timer.
  • Switching languages every weekend because a senior used a different one.
  • Memorising HR answers before they can finish the OA.
  • Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.

If you do one thing after reading this: schedule three timed Citi papers on three different days, then interview prep on the leftovers.

If you are starting from a service-company prep base

A TCS/Infosys aptitude deck still helps the quant/logic slice of many Citi papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Citi-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.

10-day crash version

Days 1-3: one timed Citi paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Citi. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.

What to carry into the interview room

Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Citi, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.

Tracking that does not become a second job

A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Citi mistakes, you are collecting content, not preparing.

Extra drill block (1)

Sit one more mixed Citi set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.

Last-mile notes for Citi prep

A note on mocks vs. random problem lists

Random Citi problems feel productive. Timed mocks are what move the needle. If you only have an hour tonight, sit 40 minutes of a previous-year Citi set and spend 20 minutes on the three misses. That loop beats an untimed 8-problem grind you will not remember tomorrow.

How to use this page the night before

Do not reread the whole Citi hub. Skim eligibility once, open your error log, and recast the two STAR stories you will actually say. If the drive names an OA platform, click around it for five minutes so login panic is not your first round.

Citi fresher CTC in India (2026)

Figures are candidate-reported as of August 2026.

Role band Typical CTC (reports) Notes
Fresher / early-career ₹12-22 LPA Varies by track and Pune/Chennai/Bengaluru

Confirm base/bonus on the written offer.

Benefits students care about

Health coverage, learning support, hybrid/office norms by team, and global bank exposure. Bonus components vary - read the letter.

How to read the band: ₹12-22 LPA is the fresher range students most often cite. Compare carefully with peer banks; offer letters beat WhatsApp forwards.

Joining city affects lifestyle even when CTC looks similar. Ask hybrid norms after the offer conversation begins.

Offer hygiene checklist: verify CTC vs take-home assumptions, joining location, background-check timelines, and any bond/notice language in writing. Ask clarifying questions politely after the verbal offer - not as a first-minute demand in technical round one.

If you hold multiple bank offers, compare role scope and city, not logo size. A slightly lower CTC with better team fit can still be rational; just decide with eyes open.

Growth students ask about: tech IC ladders and occasional moves into specialised platforms (payments, risk, data). Analyst paths emphasise domain depth. Neither is “easier”; they filter different skills on day zero.

Growth chatter: tech ladders emphasise ownership of services and domain expertise in banking systems. Internal mobility exists but is process-heavy - set expectations calmly.

How Citi’s banking world should shape your “why”

HR rounds punish generic “I like finance” answers. A usable Why Citi mentions global banking scale, India tech centres, and a problem space you care about - payments reliability, risk controls, data platforms - in your own words. Tie it to a project where correctness mattered. If you have never touched banking, research one public Citi technology initiative and explain why that engineering problem interests you.

Compensation talk waits until invited. Know the ₹12-22 LPA candidate-reported band, your city constraint, and one thoughtful team question.

For tech candidates coming from pure product prep, add SQL and one banking-domain story. For analyst candidates coming from CAT-style aptitude only, add structured “Why Citi” and basic business awareness so HR does not feel empty. The OA gets you in the room; the story gets you the offer.

A practical calendar tip: keep one mock every weekend even when no drive is scheduled. Timed accuracy decays. When the shortlist mail arrives, you will not have seven free days to rebuild section timing from zero.

Hiring trends 2026

Track-specific OAs remain. SQL and compliance awareness stay relevant for tech. Communication quality is scrutinised.

Process shape

OA → Technical → HR is still the spine. Some loops add managerial rounds.

What to practice more

Timed OA triage, SQL for tech, and honest Why Citi stories.

Offer reality check

Treat ₹12-22 LPA as a reported band, not a guarantee.

Net for 2026: do not wait for a pattern rumor. Match prep to track, then double down on accuracy. Campus coverage varies - if your college hosts Citi, assume the bar matches other campuses and bring the same triage plan you would take to a metro drive without cutting corners on mocks.

India recruiting calendars: campus seasons cluster; off-campus appears year-round. Keep a standing mock habit if you graduate mid-year.

Net for juniors reading this in August 2026: Citi remains a serious banking employer with India tech scale. The process is beatable with track-matched mocks and honest communication. It is not beatable with last-minute brand obsession and zero SQL or aptitude timing practice.

Also expect more reliability/controls vocabulary in tech chats than older seniors remember from pure puzzle loops. Fundamentals did not get easier - the language around banking risk got clearer.

FAQs students ask about Citi placements

Papers & process

Can I download Citi placement papers PDF? Yes. Free Citi placement papers PDF and 2024-2026 practice are on this site. Start with the 2026 PDF or the archive.

What is the Citi placement process? OA → Technical → HR for many fresher loops. Track-specific OA. Often 2-6 weeks campus end-to-end.

How many rounds are there in Citi interview? About three major stages commonly. Some drives add rounds. Count the mailer.

Is Citi tech hiring the same as analyst hiring? No. Tech emphasises coding/CS/SQL. Analyst emphasises aptitude/verbal/domain. Confirm your JD.

Eligibility & offer

What is Citi eligibility criteria for freshers 2026? Candidate-reported: 7.0+ CGPA or 70%; relevant degree; no active backlogs preferred; track-appropriate skills. Verify careers.citi.com or your notice.

Is 7.0 CGPA enough for Citi? It meets the commonly reported floor. OA and interviews decide advancement.

What is Citi salary for freshers in India? Commonly reported around ₹12-22 LPA. Confirm the written offer. Hubs: Pune, Chennai, Bengaluru.

Do I have to relocate? Those three cities are the main hubs candidates report. HR checks willingness. Be honest early.

Prep & Citi-specific

How to prepare for Citi placement? Match track, then timed mocks + interview depth + STAR. Details: preparation guide.

Which languages are allowed? Commonly Java, Python, SQL. Confirm the invite.

Do tech roles need finance knowledge? Deep IB valuation is not the main filter. Basic banking-domain awareness, controls vocabulary, and SQL help.

Citi vs JP Morgan vs Barclays - which fits better? All competitive banks. Bands and cultures differ; Citi fresher chatter often cites ₹12-22 LPA. Customise Why stories; compare written offers.

Can non-CS branches apply to Citi tech roles? Often yes when the JD opens software tracks. You still need the coding/SQL bar. Branch openness is permission to attempt, not a free pass.

What SQL topics should I revise for Citi? Joins, aggregations, indexes intuition, primary vs foreign keys, and basic transaction vocabulary. Be ready to write or reason about queries on a whiteboard or shared doc.

Does Citi hire ECE/IT for tech roles? Yes on many drives when coding and SQL are strong. Bring projects you can defend and do not rely on branch alone.

Should I prepare system design for Citi fresher roles? Light fresher design - APIs, data choices, failure modes - helps some tech loops. Do not sacrifice OA accuracy to study distributed systems textbooks end-to-end.

Any pro tip for Citi placement preparation? Skim OA in two minutes, bank easy marks, keep SQL warm for tech, and rehearse one plain-language controls or payments story.

What should I put on my Citi resume? Projects with metrics, honest tech stack, and any data/reliability ownership. Do not invent banking tools you cannot defend.

Where can I read interview experiences? Start with interview experience on this site and campus blogs. Label whether the story is tech or analyst before copying prep.

How hard is Citi OA? Time pressure is the usual killer. Students who clear protect easy marks and avoid ego fights with one hard question.

Citi - recent candidate experiences

Public nested notes on this site emphasise multi-track bank hiring - pattern is role-type specific - more than a single universal paper. Students who clear usually say the first round rewards speed with accuracy: skim, bank easy marks, protect sections.

Successful prep patterns include timed mocks, an error log for weak aptitude or DSA topics, SQL practice for tech interviews, and at least one project story with metrics and trade-offs. Behavioral rounds map to ownership, teamwork, and banking values - prepare concrete STAR examples, including an ethics/compliance-aware story if you have one.

Another pattern across 2024-2026 chatter: candidates fail by using a roommate’s tech plan for an analyst OA (or the reverse). Always label your track. HR relocation questions for Pune/Chennai/Bengaluru are real filters - bluffing city flexibility and reneging later is a bad plan.

Public candidate stories may be thinner for Citi than for Cisco or BrowserStack right now - which means your own campus seniors and verified drive emails matter even more. Use this site for structure and drills; verify live format every time.

What to steal: confirm track; practise triage; keep SQL warm for tech; write a specific Why Citi; sleep before OA.

Students who cleared after a miss often cite better OA triage - banking easy marks first - not a brand-new advanced course the night before. Keep a standing weekly mock even between drives.

When comparing Barclays, HSBC, JP Morgan, and Deutsche Bank hubs on this site, reuse aptitude/DSA bases but swap Why stories and domain vocabulary. Do not submit identical motivation paragraphs to every bank.

Similar banking employers share OA filters but differ on culture, bands, and India hub mix. Label your track in every note you read so you do not train the wrong section.

Do not treat one blog as a fixed paper template - use it as a vibe check, then return to timed mocks on this site and keep your error log honest about whether misses were speed, concepts, or wrong-track prep.

Concrete junior checklist: (1) one full OA mock matching your track this week, (2) one SQL session if tech, (3) rewrite two STAR stories, (4) decide city constraints honestly before HR and pack a calm two-minute OA triage reminder on a sticky note.

For students comparing offers with JP Morgan, Barclays, HSBC, or Deutsche Bank, compare role, city, and written CTC components - not logo prestige alone. A Citi-shaped prep plan still helps nearby bank interviews if you rewrite Why stories.

Do not treat one blog post as a fixed paper template - use it as a vibe check, then return to timed mocks.

Keep this site explore links handy during prep week so you are not hunting nested URLs under stress the night before the online assessment window opens on your laptop at home or in the campus lab you reserved ahead of time for quiet focus and peace of mind on that very important online assessment test day morning practice session itself today for sure.

Keep a short weekly checklist on paper: one mock, one SQL or aptitude drill, one STAR rehearsal, one Why Citi rewrite. Consistency beats last-week panic more than any single PDF dump ever will for serious banking placement drives across the current campus hiring season still clearly ahead of you right now today.

Similar companies

Barclays · Bank of America · HSBC · JP Morgan · Deutsche Bank