Citi Data Analyst interview typically runs 2-4 rounds: HR screen, analyst/department interviews, and a final presentation or superday. Timeline is often weeks, and the process is uneven but mostly behavioral with light technical checks.
$71K
Avg. Base Comp
$146K
Avg. Total Comp
3-5
Typical Rounds
2-6 weeks
Process Length
Our candidates consistently describe Citi as a process that rewards people who can connect their experience to the role in a clear, practical way. The strongest signal isn’t deep technical complexity; it’s whether you can explain your background, your projects, and your day-to-day working style without sounding rehearsed. Multiple candidates reported being pressed on why Citi, team fit, and how they handled a project or client situation, which tells us the bar is less about flashy answers and more about whether you sound credible in a banking environment.
A recurring theme is that Citi likes to see candidates think out loud on simple problems. We’ve seen basic SQL, Excel, Python, and even OOP-style questions, but the emphasis stays on structured reasoning rather than trick questions. One candidate was asked to work through a live document presentation, while another had to digest a case brief on the spot and discuss metrics for a credit card launch. That combination suggests Citi values analysts who can move from raw information to a clean recommendation quickly, especially when the prompt is business-facing.
We also see a pattern of unevenness across interviewers, with some candidates describing the process as polished and others calling it messy or inconsistent. That means small things matter: being concise, staying organized, and showing that you can handle ambiguity without losing your thread. In our experience, the candidates who do best here are the ones who make their thinking easy to follow and show they can operate comfortably in a practical, client-aware finance setting.
Synthetized from 4 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Citi process.
The hardest part for me was that the process felt a little uneven depending on who I was speaking with. My first round was with HR and a current analyst, and it was mostly behavioral plus a walk-through of my CV. They wanted to understand why I was interested in the team specifically and whether I could handle the day-to-day demands of the role. After that, I had another round with two people from the department, and that one ended with a presentation based on a document they provided. That was the most distinctive part of the process because it was less about abstract interview questions and more about how I would organize and explain material on the spot.
The technical side was not especially deep, but I did get a few basic finance questions and some problem-solving/logical questions where I had to talk through my thinking step by step. I also remember being asked straightforward things like salary expectations and notice period, so they were clearly moving quickly once they felt the fit was there. Overall, the interviewers were professional and friendly, and when the process moved smoothly it felt organized and focused on the key requirements for the position. The only downside was that the timeline could drag, with weeks between stages and not much momentum, which made it harder to know where I stood. In the end I received an offer, and my main takeaway is to be ready for a mix of CV discussion, basic technical/finance review, and a presentation-style round rather than expecting a heavy algorithm interview.
Prep tip from this candidate
Review basic finance technicals and be ready to explain your interest in the specific team. Also practice presenting a provided document clearly, since one round was built around that format.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Citi
Write a query to show the number of users, transactions, and total order amount per month in 2020
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Replace Words with Stems | |
| Loan Model | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| Employee Salaries | |
| Closest SAT Scores | |
| Top Three Salaries | |
| Find the Missing Number | |
| Experiment Validity | |
| Slacking Employees Salaries | |
| Bagging vs Boosting | |
| Compute Deviation | |
| Prime to N | |
| Last Transaction | |
| 500 Cards | |
| Department Expenses | |
| Session Difference | |
| Rain in N Days | |
| Random SQL Sample | |
| P-value to a Layman | |
| Bank Fraud Model | |
| Subscription Overlap | |
| Paired Products | |
| Size of Joins |
Synthesized from candidate reports. Individual experiences may vary.
Some candidates were asked to complete a Codeility assessment with 3 questions before the interview day. The assessment appears to be a basic technical screen rather than a deep algorithm test.
The first conversation is typically with HR and focuses on your background, CV walkthrough, education, work experience, and motivation for Citi and the specific team. Candidates were also asked practical fit questions such as salary expectations, notice period, and whether they were comfortable working from home.
This round mixes behavioral questions with light technical checks. Interviewers asked about project experience, client conflict handling, basic finance concepts, Excel, SQL, Python, and simple coding or OOP topics such as palindrome checks, grouping, and Java fundamentals.
Candidates met with two or more people from the department for a more role-specific discussion. In some cases, this round ended with a presentation based on a document provided by Citi, and in others it included a live case study where candidates had to quickly read, organize, and explain the material while discussing business metrics and decision-making.
The final stage was often a superday made up of three separate interviews. These rounds combined behavioral fit, resume walkthroughs, theory, and practical problem-solving, with questions spanning OOP, Excel, R/Python, basic SQL, and business judgment.