Software Engineer applicants have rated the interview process at Fidelity Investments with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 72% positive. To compare, the company-average is 67.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 17 days to get hired, when considering 136 user submitted interviews for this role. To compare, the hiring process at Fidelity Investments overall takes an average of 28 days.
Common stages of the interview process at Fidelity Investments as a Software Engineer according to 136 Glassdoor interviews include:
Phone interview: 23%
One on one interview: 18%
Skills test: 14%
Group panel interview: 11%
Presentation: 9%
Background check: 7%
Drug test: 7%
Personality test: 6%
IQ intelligence test: 5%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Fidelity Investments (Westlake, TX) in Apr 2012
Interview
1 phone interview purely technical, 5 1:1 onsite interviews consisted of technical, resume, work experience, and basic hr questions. Got a call in a couple of days and accepted the offer.
HR was the first round
Followed by HM
HR asked for availability and resume then just disappeared
Even after following up, no response
Then next week for the same role, same message she sent to a friend of mine
Interview questions [1]
Question 1
They asked for availability and then totally ghosted me
1. DSA Round (Easy Level)
They usually don’t go very deep into complex algorithms. Expect fundamentals like:
Anagram check (e.g., compare two strings efficiently)
Palindrome check (string or number)
Basic array/string manipulation
Sometimes simple hashing or sorting logic
2. DBMS Basics
What is a primary key / foreign key
Difference between SQL joins (INNER, LEFT, RIGHT)
Basics of normalization
Simple query writing
They usually keep it conceptual + a few practical questions.
3. OOPs Concepts
Very standard questions, such as:
Pillars of OOP: Encapsulation, Inheritance, Polymorphism, Abstraction
Real-life examples
Difference between overloading vs overriding
Why OOP is useful
They may ask you to relate this to your project.
4. Puzzle / Logical Thinking
These are not super hard—just to test reasoning:
Basic math/logical puzzles
Pattern-based questions
Situational problem solving
5. Project Discussion
Explain your project clearly:
Problem statement
Your role
Tech stack
Be ready for:
“Why did you choose this approach?”
“What challenges did you face?”
“How would you improve it?”
I interviewed at Fidelity Investments (Durham, NC)
Interview
Behavioral interview with the hiring manager centered around STAR-style questions and getting an understanding of your current position. Focused on finding overlap in your experience with the experience needed for the role