Glassdoor users rated their interview experience at Fidelity Investments as 100% positive with a difficulty rating score of 2 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Anonimous and rated their interviews as the hardest, whereas interviews for Anonimous and roles were rated as the easiest.
Here are the most commonly searched roles for interview reports -
Hr screening, then interview with branch. Not a whole lot to report as questions were fairly standard relating to planning experience and client relationship management abilities. Did not get position as even though I was told I interviewed well they had many qualified internal candidates.
One online technical assessment focused on SQL and Excel, with multiple choice questions then 2 SQL coding questions. Then a panel interview with the recruiter and project managers. The panel interview was online and approximately 30 minutes long
Interview questions [1]
Question 1
Tell me about a time where you faced a bug in your code and your process of resolving it.
The first round was a phone interview with HR.
The second round was a technical/behavioral round with the hiring manager
The final round was a live coding/technical round with 2 principal software engineers.
The whole process took almost 2 months.
Interview questions [1]
Question 1
The hiring manager asked questions about the resume and some STAR questions. Then, she asked a brief coding question to test my problem-solving skills. I didn't need to write any code. They were okay with pseudocode.
The final round was a live coding and core Java questions with 2 principal engineers. One of them was friendly, but the other engineer had a rude tone. They should consider who they should have for interviews. Don't invite them to interviews just because they are principal devs.
The live coding was an easy level of string manipulation. What shocked me was that they didn't know what map.getOrDefault() method does. Instead of admitting their lack of knowledge, the rude dev questioned me and said, "this doesn't seem supported in Java". The audacity of asking a coding question and not knowing a basic method is crazy to me. Even when I successfully wrote the code, that guy kept nitpicking and said my code looks okay, but there are other ways to write it. I mean, no shoot Sherlock. I asked him what other way he'd write, and he said he would use Streams instead of a loop, as if that makes the algorithm different.
Maybe because I used to work for SV companies, but they didn't seem knowledgeable for principal-level engineers.