Citi Business Analyst interviews, as candidates describe them, mix behavioral and stakeholder questions with practical BA topics. Some candidates also report Python, SQL, coding or case-study elements. Formats vary by team.
$95K
Avg. Base Comp
$130K
Avg. Total Comp
2-4 rounds
Typical Rounds
2-13 weeks
Process Length
Candidates describe the Citi Business Analyst interview as mostly a fit and communication check, though the technical content varies noticeably by team. Several people report HR or recruiter screens followed by hiring-manager and team conversations. Many of these were behavioral: why Citi, why this role, how you handle pushback or conflict, and a walkthrough of past projects.
The technical side is less uniform. One candidate was asked about prioritization, requirements elicitation and agile ceremonies. Another was asked about change requests, impact analysis, RTM, epics versus user stories, and what a feature is in Agile. Others report basic Python and SQL questions, web analytics questions, a coding question in a short round, or a case study with numbers provided. One candidate was asked about risks versus controls and how to choose metrics for open-ended situations. Another was asked about KYC and Citi's international work. Because the technical bar differs between reports, read the job description closely and prepare for the skills it names.
Timelines also differ. Reports range from about two weeks to about three months, and a few candidates describe slow scheduling or missed follow-ups. Outcomes are mixed, so detailed, role-specific stories matter more than rehearsed generic answers. Prepare project walkthroughs with your responsibilities, stakeholders and results. Practice a concise answer on why Citi and why this role. Refresh core BA concepts. If the posting mentions coding or analytics, practice talking through those basics under time pressure.
Synthesized from 22 candidate 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.
I walked into my first round thinking I'd be facing some serious technical grilling, but it turned out to be fairly straightforward questions mostly centered on web analytics. The initial screening was technical in nature, which surprised me a bit given the Business Analyst title—I'd expected more process-focused material. What I didn't realize going in was how important it would be to actually prepare thoroughly on those fundamentals. I coasted on general knowledge and it showed.
The second round shifted gears. This one combined business and technical elements, which felt more aligned with what the role actually demanded. They wanted to understand not just my technical chops but how I thought about business problems end-to-end. Then came the HR round to close out the process. The whole thing moved pretty fast—wrapped up in about two weeks from start to finish.
Looking back, the questions were genuinely manageable. I didn't get tripped up by complexity or trick questions. The problem was that I treated them as easier than they were, assuming surface-level knowledge would cut it. For a Business Analyst role at a financial institution like Citi, they're clearly looking for people who can connect dots between data, process, and business impact. I didn't do enough to show that synthesis. My advice: treat every question like it's testing your thinking, not just your recall. Show you understand the why behind the what.
Prep tip from this candidate
Web analytics questions are a key part of the Business Analyst interview at Citi—don't assume they're easier than they sound. Prepare concrete examples of how you've worked with analytics, tracked user behavior, and translated insights into business decisions. The second round couples technical knowledge with business acumen, so practice connecting the technical dots to business outcomes.
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 | |
|---|---|
| Size of Joins | |
| Jars and Coins | |
| Attribution Rules | |
| New Partner Card | |
| Hurdles In Data Projects | |
| Above Average Product Prices | |
| International e-Commerce Warehouse | |
| Client Solution Pushback | |
| Loan Model | |
| Seller Type Modeling | |
| String Palindromes | |
| Company Acquisition Choice | |
| Unified Event Pipeline | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Data Cleaning Experiences | |
| Singly Linked List | |
| Student Tests | |
| Risk Model for a Mortgage Bank | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Find the Missing Number | |
| Rolling Bank Transactions | |
| Cumulative Distribution | |
| Payments Received | |
| Employee Salaries | |
| Paired Products | |
| Bagging vs Boosting | |
| Total Spent on Products |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically report starting with an online application, sometimes with a questionnaire, then a short HR or recruiter conversation. Reported topics include your background, why Citi, career goals and how long you plan to stay. Have a concise introduction and a clear reason for choosing this role ready.
Several candidates describe a conversation with the hiring manager or team members that mixes behavioral questions with project deep dives. Reported prompts include handling pushback, conflict and difficult stakeholders, a team vision, and walking through past projects and results. Prepare structured stories with a clear situation, action, outcome and lesson.
Some candidates report practical BA questions on prioritization, requirements elicitation, agile ceremonies, change requests, impact analysis and RTM. Others report basic Python and SQL, web analytics, a brainteaser, a coding question or metric-selection scenarios. The mix appears to vary by team, so check the job description and prepare for what it names.
Some candidates report a final stage with senior team members, a panel, or an assessment-center format. Reported elements include a case study read and presented in about 30 minutes, a case with numbers supplied upfront, and a competitive Zoom panel with other candidates. Not every candidate describes this stage, and some processes ended after fewer conversations. Practice clear, structured answers.
