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.
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 two principal engineers. One of them was friendly, but the other engineer had a rude tone. They should consider who they select for interviews and not just invite them 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 the 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 it, 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.
The following metrics were computed from 40 interview experiences for the Fidelity Investments Senior Software Engineer role in United States.
Fidelity Investments's interview process for their Senior Software Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Fidelity Investments's Senior Software Engineer interview process in United States.