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.
Synthesized from 7 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.
To be completely honest, I expected a "driving test" interview: trick algorithm questions and code I’d never see in production. What I got was much closer to a pair programming session with a senior engineer who wanted to see how I think, not just what I can recite.
First Impression: The "Karat" That Wasn’t Just Karat It was the first round, virtual, with someone from Karat. The interviewer started with what seemed like a simple Java question: "What’s the difference between equals() and ==?". I was so comfortable giving the textbook answer that I almost got complacent. Then, the dynamic shifted. He asked me to look at a code snippet on a shared screen. It wasn’t a new algorithm; it was a microservice with a subtle concurrency bug that caused data corruption under certain load conditions.
Questions asked: What helped me most was the specific mix of questions that moved beyond textbook definitions into real-world application, starting with deep Java internals like explaining the memory mechanics of String.toCharArray() and the exact difference between equals() and == for custom objects, followed by a request to design a thread-safe singleton and then intentionally break it to find race conditions. The most intense part was the Karat-style debugging round where I had to fix a failing unit test in a Spring Boot microservice without just patching the test, requiring me to identify a subtle concurrency bug in the production code, while the system design round challenged me to architect a payment service that handled network failures and idempotency, specifically asking how I would manage audit logs without slowing down writes. They also threw in scenario-based prompts like, "Why should we hire you over someone with identical skills?" and "Walk me through your 3 AM outage response if logs are silent," which forced me to defend my engineering trade-offs and communication style rather than just reciting algorithms, proving that the real test was my ability to articulate the "why" behind my technical decisions under pressure.
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 | |
| Real-Time Transaction Streaming | |
| Hurdles In Data Projects | |
| Replace Words with Stems | |
| Concurrent LLM Serving | |
| Offer Matching API Design | |
| Loan Model | |
| Seller Type Modeling | |
| String Palindromes | |
| International e-Commerce Warehouse | |
| Text Editor With OOP | |
| Unified Event Pipeline | |
| Index Fund Return | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Concentric Circles | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N |
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.