J'ai postulé en ligne. J'ai passé un entretien chez Fidelity Investments (Boston, MA) en févr. 2023
Entretien
1: Recruiter Call 2: HackerRank 3: Onsite: The onsite is a a bit different I will say. The interviewer was nice. They have a set of questions specific to the technology they use and the questions are to test your knowledge on that. 1 hour interview will be divided into different sections a) Spring boot questions(basics annotations) b) Angular Basics like what is a derivative c) CI/CD pipeline qs d) Database queries e) Any queue service or something they would be using in job Now, I can understand they have a tried and tested method to hire talent and I respect that, but rejecting solely on basis of this is just different and very demotivating imo since the candidate gets no idea of how they did or what they were lacking. Not knowing an answer to questions which they are using in their project is not a correct judge of what someones capabilities are.
Questions d'entretien [1]
Question 1
What is spring boot, DB queries, some basic angular questions. Just know what you have worked on.
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
Questions d'entretien [1]
Question 1
They asked for availability and then totally ghosted me
J'ai passé un entretien chez Fidelity Investments (Bengaluru)
Entretien
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?”
J'ai passé un entretien chez Fidelity Investments (Durham, NC)
Entretien
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