Real, anonymous reports from people who interviewed for Software Engineer at Citadel, newest first and distilled into what to expect across the loop.
My process followed a clean new-grad structure: a first round, then a superday, and finally a team interview. It felt organized and aligned with what was advertised, and each step built on the last.
I started with a recruiter screen where they asked about my background and pushed on why I ended up laid off at my previous company. They also made the next step sound like it would lean on C++, and then I moved into the technical portion.
The interview process begins with a challenging online assessment on HackerRank, typically involving two algorithmic problems that test both coding ability and efficiency. Candidates noted that the assessment often feels more difficult than expected, with hidden correctness checks that can lead to disqualification even if some tests pass.
Following the online assessment, candidates participate in multiple technical interviews that focus heavily on LeetCode-style coding problems, often requiring clear communication of thought processes and implementation choices. The interviews can vary in difficulty, with some emphasizing language-specific knowledge and others incorporating system design elements.
Behavioral questions are integrated throughout the interview process, often starting with discussions about past projects and experiences. Candidates are expected to articulate their motivations and thought processes clearly, which can be as critical as technical performance in the evaluation.
The interview process is structured with a clear progression from an initial recruiter call to technical assessments and multiple back-to-back interviews, often culminating in a superday format. Candidates noted the intensity of the process, with limited time to prepare between rounds and a focus on maintaining performance under pressure.
Candidates reported that interviewers place a strong emphasis on communication skills, expecting clear explanations of thought processes during coding tasks. The ability to articulate reasoning and handle ambiguity is seen as crucial, with interviewers often probing deeper into candidates' logic and decision-making.
Many candidates expressed frustration over the lack of feedback after assessments and interviews, with some feeling that the process was more about fit than pure coding ability. Outcomes can vary widely, and candidates often leave feeling that performance under pressure and alignment with the interviewers' expectations were key factors in their success or failure.