Citi Software Engineer interview typically runs 4 rounds: recruiter screen, technical screens, onsite or SuperDay, HR round. Timeline is about 1-3 months, and the process is structured and technical.
$116K
Avg. Base Comp
$137K
Avg. Total Comp
4-6
Typical Rounds
2-6 weeks
Process Length
We’ve seen Citi consistently reward candidates who can connect fundamentals to real systems, not just recite definitions. Across candidate experiences, the strongest signal was hands-on fluency with the stack on your resume: Java, Spring Boot, collections, Java internals, and even stack-specific questions like React or AWS basics when those tools were relevant. Multiple candidates noted that interviewers kept pulling them back to their current projects, asking them to explain architecture choices, debug failing tests, or walk through how a controller or microservice would actually behave in production.
A recurring theme is that Citi likes interviews to feel practical. Instead of pure algorithm drills, our candidates report scenario-based prompts, code fixes, whiteboard architecture, and system design discussions around communication between services, logging, load balancing, and database setup. That means the bar is less about cleverness and more about whether you can make sound engineering decisions under pressure. We also see a clear preference for candidates who can defend tradeoffs cleanly; one candidate was explicitly asked to justify why they should be hired when others have similar skills, which tells us Citi is looking for judgment as much as technical breadth.
The non-obvious make-or-break factor here is how well you can talk through your own experience with precision. Several candidates mentioned resume deep-dives, project architecture questions, and direct follow-ups on why they chose certain patterns or technologies. In other words, Citi seems to value engineers who are credible, grounded, and able to explain the “why” behind their work. That combination of practical depth and clear communication shows up again and again in the strongest outcomes.
Synthetized from 7 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 first round was a Karat-style interview, and that was probably the part I remember most because it felt more like a conversation than a grilling. The interviewer was professional and kept it pretty standard, with no trick questions, but they still wanted to see whether I actually understood the basics. I got asked about Java features and design patterns, and then there was a coding portion where I had to correct a failing test case. That made the round feel a little different from a normal whiteboard problem, since it was less about inventing an algorithm from scratch and more about spotting what was broken and fixing it cleanly.
After that, the process moved into a full day with three rounds. There was a mix of technical concepts and behavioral questions, and the behavioral side came up a lot more than I expected. They asked about handling conflict, past experience, coding projects, data structures, why Citi, and what I was expecting from the role. I also had an on-campus interview format in one part of the process, where the first round was HR plus tech and they focused more on knowledge than anything too deep. In that round I was asked a couple of coding questions that I solved with HashMap, and there was even a question about how toCharArray() works internally, which was a good reminder that they care about fundamentals. Later, there was a SuperDay with three interviews, one behavioral and two technical, and the technical ones were not really hard, just varied in difficulty. Overall the process felt structured and fairly standard, and the interviewers were professional throughout. I ended up getting an offer, so my main takeaway is to be ready for Java fundamentals, design patterns, basic coding, and to explain your projects and motivations clearly.
Prep tip from this candidate
Be ready to explain Java features and design patterns clearly, and practice talking through how you would debug or fix a failing test case. Also prepare concise answers for why Citi, handling conflict, and your past coding projects, since those came up repeatedly.
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 | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Concentric Circles | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Find the Missing Number | |
| Maximum Profit | |
| Prime to N | |
| Rolling Bank Transactions | |
| String Shift | |
| Comments Histogram | |
| Employee Salaries | |
| Closest SAT Scores | |
| Random SQL Sample | |
| Rectangle Overlap | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Slacking Employees Salaries | |
| Size of Joins | |
| Over 100 Dollars | |
| Scrambled Tickets | |
| Minimum Change | |
| Cumulative Distribution | |
| Level Of Rain Water In 2D Terrain |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically apply online and may wait some time before hearing back. In some cases there is no recruiter contact at first, while in others the recruiter reaches out to confirm availability, timeline, and the technologies the candidate is comfortable with.
This is usually a non-technical screening focused on logistics and fit. Recruiters ask about availability, expected timeline, resume projects, and basic motivation for Citi, including why you want the role and what you know about the company.
The first technical round is often run by Karat or another external interviewer and is live over video. It tends to focus on core stack knowledge rather than pure algorithms, with questions on Java fundamentals, Spring Boot, React, AWS basics, design patterns, and sometimes a debugging or test-fixing exercise.
Candidates then move into a set of technical interviews that may be scheduled as a full day or spread across multiple rounds. These interviews cover Java, backend fundamentals, microservices, system design, architecture tradeoffs, coding, and project deep-dives, often with scenario-based questions and live problem solving.
Behavioral questions are mixed into the process and can be a significant part of the loop. Interviewers ask about conflict handling, past projects, why Citi, what you are looking for in the role, and how you would explain your experience and decisions.
The final HR conversation is typically used to confirm fit, availability, and next steps. In some cases it happens after the technical rounds and may be followed by an offer, while in others the process ends after this stage.