Real, anonymous reports from people who interviewed for Software Engineer at Citigroup, newest first and distilled into what to expect across the loop.
I applied through the career portal for a senior Java developer role at Citi, and my process ended quickly. After getting scheduled, I was rejected right after the first round.
I went through an on-campus interview for a senior Java-focused role, and it ran in three rounds. I cleared the first one, which combined HR with a technical component. That first stage leaned heavily toward core knowledge rather than broad discussion.
The interview process typically follows a structured sequence, starting with a recruiter screen, followed by technical interviews, and concluding with a behavioral or cultural fit discussion. Candidates noted that the organization and communication throughout the process were generally positive, making it easier to navigate each stage.
Candidates faced a variety of technical assessments that included coding challenges, debugging tasks, and questions on core Java concepts, data structures, and algorithms. The focus was often on practical coding skills and understanding underlying principles rather than just theoretical knowledge.
Behavioral interviews were a significant part of the process, with questions aimed at understanding candidates' motivations, teamwork, and problem-solving approaches. Candidates felt that these discussions influenced the overall tone of the interviews and were critical in assessing fit within the company culture.
The difficulty of the interviews varied, with some candidates finding them challenging due to the depth of technical knowledge required and the need for clear communication during problem-solving. Many reported feeling unprepared for the level of detail expected, especially in live coding scenarios.
Several candidates expressed frustration with the lack of feedback and communication after their interviews, noting that delays or silence from HR left them feeling uncertain about their status. This aspect significantly impacted their overall impression of the interview experience.
Candidates reflected on the importance of preparing for both technical and behavioral components of the interviews, emphasizing the need to articulate thought processes clearly during coding tasks. Some wished they had practiced more on specific topics like system design or situational questions.
