Real, anonymous reports from people who interviewed for Software Engineer at Citi, newest first and distilled into what to expect across the loop.
My process started with an on-campus interview that felt tightly structured into three rounds. The first round combined HR and a technical component, and it leaned heavily toward core knowledge rather than open-ended discussion. I had to work through two main prompts: one involved using a HashMap approach, and another was centered on understanding how the toCharArray() function works and what’s happening under the hood.
After a recruiter touchpoint, I got pulled into a Karat-style technical screen that was very hands-on. The format was split into a couple of parts: first I did a quick introduction and then moved into Java questions for roughly 10–15 minutes. That was followed by debugging and fixing test cases for about 40 minutes, where the expectation was that I could read what was failing and correct it while staying organized.
The interview process is typically structured with a clear timeline, starting from an online assessment followed by a series of technical and behavioral interviews, often culminating in a superday format. Candidates reported a mix of HR and technical rounds, with varying expectations across interviews.
Technical interviews emphasize core Java knowledge, data structures, algorithms, and system design, often involving live coding and debugging scenarios. Candidates are expected to demonstrate a strong understanding of Java fundamentals and practical problem-solving skills.
Behavioral interviews assess cultural fit and communication skills, with questions about past experiences, motivations for joining Citi, and situational responses. Candidates noted the importance of being prepared to discuss their resume and how they align with the company's values.
Candidates experienced mixed communication regarding follow-up and feedback, with some reporting delays and a lack of clarity post-interview. It's advisable to remain proactive in seeking updates after interviews to ensure a smoother experience.
The overall difficulty of interviews is described as moderate, with a focus on foundational knowledge rather than speed. Candidates should prepare for a range of question types, including coding challenges and theoretical discussions, while maintaining a calm demeanor under pressure.
Candidates expressed a desire to better prepare for specific technical topics and to research the company more thoroughly to avoid being caught off guard during behavioral questions. Understanding the role's requirements and practicing coding problems are key recommendations.
