Citi Software Engineer candidates commonly report a recruiter or HR contact, a Karat-style technical screen, and later team interviews. Java fundamentals, debugging existing code, project discussion, and behavioral questions recur.
$124K
Avg. Base Comp
$155K
Avg. Total Comp
3-4 rounds
Typical Rounds
2-3 weeks
Process Length
Reported Citi Software Engineer processes include Karat-style technical screens and later team interviews. The screen is repeatedly described as practical code work rather than a pure algorithm drill: candidates report questions on equality and hashing, exceptions, OOP, design patterns, Spring, concurrency, and Java fundamentals. Several candidates were shown existing code, asked to identify a defect, fix a failing test, or implement methods after first explaining their approach.
Prepare to read and change unfamiliar code under time pressure. Practice narrating a short implementation plan, testing assumptions, and making a focused fix. Reports also include Java collections, HashMap use, multithreading, and debugging asynchronous or singleton-related code. Some candidates instead encountered .NET async/await questions and practical implementation tasks, so align your review with the stack on your resume and the role conversation.
Candidates who advanced describe later team or panel conversations that mix technical discussion with projects, motivations, conflict, teamwork, and system-design-style reasoning. Be ready to explain your own project architecture and trade-offs clearly, then connect it to the role. Reported formats vary by team and technology stack; the recurring pattern is fundamentals plus practical explanation rather than one fixed question set.
Synthesized from 36 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.
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 | |
| Attribution Rules | |
| Hurdles In Data Projects | |
| Dijkstra implementation | |
| 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 | |
| Client Solution Pushback | |
| Index Fund Return | |
| Above Average Product Prices | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Singly Linked List | |
| Student Tests | |
| Concentric Circles | |
| Measuring Text Difficulty | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report recruiter emails, calls, or HR screens before technical interviews. These conversations may cover availability, technologies you are comfortable with, your background, and resume projects; some reports also include motivation or culture questions.
Many candidates report a virtual, third-party Karat-style screen lasting about an hour. Java questions may cover equality, hashing, memory, exceptions, OOP, design patterns, Spring, or concurrency, followed by debugging existing code, fixing tests, or implementing methods.
Candidates who report later stages describe conversations with engineers or panels about prior projects, Java backend development, cloud or frontend technologies, and practical coding. Depending on the team, this may include system-design-style discussion or an additional technical interview.
Later interviews may include why Citi, conflict, teamwork, leadership, expectations, and detailed project discussion alongside technical content. One candidate reported a full day with three interviews, including behavioral and technical conversations.
