Real, anonymous reports from people who interviewed for Software Engineer at Fidelity Investments, newest first and distilled into what to expect across the loop.
My process started with a laid-back team intro/screening call. It felt more like a conversation than a formal interview: the recruiter walked through my resume and we talked about the role, then they asked where my experience intersected with their needs.
My first round started with HR, and it was followed by a hiring manager request where they asked for availability and my resume. After that, things stalled in a way that made the whole process feel unfairly uncertain.
Candidates reported a lack of clear communication and updates throughout the interview process, leading to uncertainty about their status and the overall timeline. Many expressed frustration over delayed responses and feeling ghosted after interviews.
The initial recruiter calls were generally described as relaxed, focusing on the candidate's background and fit for the role, with a conversational tone that eased candidates into the process.
Technical interviews often included a mix of coding challenges, primarily focused on data structures and algorithms, with some candidates experiencing low-level design tasks. The difficulty varied, but many found the expectations for clarity and reasoning to be high.
Behavioral interviews were common and typically utilized the STAR method, focusing on past experiences and how candidates handled challenges. Candidates noted that these rounds were crucial for demonstrating fit and communication skills.
For some candidates, later rounds included system design discussions that required a deeper understanding of engineering principles and practical applications, moving beyond simple coding tasks to evaluate overall problem-solving skills.
Many candidates expressed disappointment over the lack of feedback after interviews, feeling that the absence of closure contributed to a negative overall experience, regardless of their performance during the interviews.