Real, anonymous reports from people who interviewed for Software Engineer at Fidelity Investments, newest first and distilled into what to expect across the loop.
Get your personalized Fidelity Investments Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
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.
Most of the questions centered on my familiarity with cryptography, my security principles, and what I knew about Java. Overall it didn’t feel overly intense, and the pace was pretty relaxed, which made it easier to talk through my background clearly.
3 weeks ago
Average Neutral Chennai
My biggest issue wasn’t with the interviews themselves—it was what happened after the online assessment. The process felt like it could have been smooth, but once I finished the assessment, I didn’t get clear updates on what the next rounds would be.
There was no transparent timeline, and follow-ups didn’t get answered for an extended period. I kept checking in because I genuinely didn’t know whether I’d moved forward, and that uncertainty dragged out the experience more than any single technical question would have.
4 weeks ago
Difficult Neutral Bengaluru
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 st…
1 month ago
Difficult Negative Westlake, TX
My interview journey had one behavioral round followed by two coding rounds, and the overall vibe was pretty challenging. For the coding parts, the pr…
1 month ago
Average Positive United States
After a recruiter call, I moved through a fairly straightforward sequence that felt organized and not overly stressful. The early conversations focuse…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
The Loop & Timeline
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.
CommunicationTimelineUncertainty
Recruiter & Initial Screening
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.
Recruiter CallBackground FitConversational
Technical Rounds & Coding Challenges
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.
Coding ChallengesData StructuresLow-Level Design
Behavioral Interviews & STAR Method
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.
BehavioralSTAR MethodPast Experiences
System Design & Depth of Technical Discussion
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.
System DesignTechnical DepthProblem-Solving
Feedback & Closure
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.