Real, anonymous reports from people who interviewed for Software Engineer at Citadel, newest first and distilled into what to expect across the loop.
I went through an OA and phone-stage coding loop for a Software Engineer role, with a couple interview rounds before ultimately not moving forward.
I hit mainly the assessment-heavy path where the main hurdle was passing automated tests quickly, and I didn’t get meaningful human feedback.
Candidates typically start with a challenging online assessment that includes multiple LeetCode-style problems, often with strict time limits and hidden tests that require careful handling of edge cases. Performance on this assessment is crucial for advancing in the interview process.
The interview process includes multiple technical rounds focused on data structures and algorithms (DSA), where candidates solve coding problems and discuss their thought processes. Interviews are often timed and can include follow-up questions to probe deeper understanding.
Candidates undergo behavioral interviews that assess cultural fit and alignment with Citadel's values, often combined with technical discussions about past projects and experiences. These rounds are critical for evaluating overall candidate suitability.
The final stages often involve a 'superday' format with back-to-back technical interviews, which can include a mix of coding and system design questions. Candidates should be prepared for a high-intensity experience with limited breaks.
Candidates report varying experiences with interviewer engagement, ranging from supportive to condescending. Clear communication and the ability to articulate thought processes are essential for success.
Candidates often experience opaque feedback and quick rejections, particularly after early assessments. Understanding that both technical performance and perceived fit can influence outcomes is important for future applications.
