← Back to Directory

Fidelity

Large Enterprises

Screna has 14 Fidelity interview write-ups. The most reported round is the technical phone screen (11).

14 interview notes · updated Jul 2026

Fidelity·Software Engineer·Technical Phone Screen

Jul 2026
Fidelity software engineer interview that was basically a Java 8 deep dive. They wanted you to know the features cold, not just name them but actually explain when you'd reach for each one.
  • Walk me through the major features introduced in Java 8 and explain when you'd actually use each one, including lambda expressions, the Stream API, Optional, default interface methods, and the new date/time library.

“This is broader than it sounds.”

View Post

Fidelity·Software Engineer·Technical Phone Screen

Jul 2026
Had a technical screen for a software engineering role at Fidelity that went pretty deep into distributed systems concepts. The MapReduce question took up most of the session and they really wanted specifics, not just a surface-level answer.
  • Walk me through how MapReduce works for processing large datasets, covering the roles of the map and reduce functions, how data gets partitioned, what combiners do, how sorting and shuffling fit in, fault tolerance, and performance considerations. Use a concrete example job to illustrate.

“This is a lot to cover in one question and I did not pace myself well.”

View Post

Fidelity·Software Engineer·Technical Phone Screen

Jul 2026
Interviewed for a software engineer role at Fidelity and got hit with a pretty wide range of topics, from Java internals to Angular to MapReduce. Felt like a breadth-first search across the whole stack rather than a deep dive into any one area. Walked out not totally sure how I did.
  • What tech stack are you currently working with and what versions are you using?
  • What new features were introduced in Java 8?
  • What is the difference between Spring and Spring Boot?
  • What are the key features Angular provides as a frontend framework?
  • How would you use MapReduce effectively for large-scale data processing?
  • How do you handle concurrency issues in Java?
  • What are SQL constraints and how do they enforce data integrity?
  • How do you distinguish a well-written test from a poorly written one?
  • What makes an integration test effective?

“Straightforward opener but I fumbled on the version numbers.”

View Post

Fidelity·Software Engineer·Technical Phone Screen

Jul 2026
Technical screen for a software engineer role at Fidelity, pretty much a deep dive into Angular fundamentals. One big question covering a lot of ground, felt more like a knowledge audit than a conversation.
  • Walk me through the core features of Angular, including modules, components, templates, dependency injection, change detection, observables, routing, and both approaches to forms.

“This was a lot to cover in one question.”

View Post

Fidelity·Backend Engineer·Technical Phone Screen

Jun 2026
Technical phone screen for a backend role at Fidelity, heavy on Spring internals. One question but it went pretty deep, felt like they wanted to see if you actually understood the proxy mechanics or just memorized the annotation.
  • How do rollbackFor and noRollbackFor work in Spring's @Transactional, and what happens when both apply to the same exception?

“I knew the basics: Spring only rolls back on unchecked exceptions by default, and rollbackFor lets you extend that to checked ones.”

View Post

Fidelity·Software Engineer·Technical Phone Screen

Jun 2026
Technical phone screen for a software engineer role at Fidelity, pretty much a single deep-dive question on Spring vs Spring Boot. Not a lot of small talk, they just wanted to see how well you understood the framework ecosystem.
  • What are the key differences between Spring Framework and Spring Boot? Walk through things like configuration, auto-configuration, embedded servers, opinionated defaults, dependency management, startup behavior, and when you'd use one over the other.

“This question is broader than it looks.”

View Post

Fidelity·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Fidelity for a full-stack role. Just the one question about dealing with setbacks during an internship, which felt pretty standard but still tripped me up a bit.
  • Tell me about a time you faced frustration or a setback during an internship. What happened, how did you handle it, and what did you take away from it?

“I had a story ready but fumbled the 'what did you learn' part.”

View Post

Fidelity·Software Engineer·Technical Phone Screen

Jun 2026
Fidelity software engineer interview that leaned heavily into testing philosophy. Felt more like a fundamentals check than a coding round, which I wasn't fully expecting.
  • What separates a good test from a bad one?
  • How would you define and distinguish unit, integration, and end-to-end tests?
  • What is the purpose of integration testing and how do you think about its scope?
  • How do you think about isolation versus realism in tests, and what are test fixtures?
  • What does test determinism mean and what are common causes of flaky tests?

“I started rambling about coverage percentages and could tell that wasn't landing.”

View Post

Fidelity·Software Engineer·Recruiter / HR Screen

Jun 2026
Fidelity full-stack screen, basically just one question about why I wanted to work there. Pretty standard stuff but I fumbled it more than I expected.
  • Why do you want to work at Fidelity specifically? What draws you to their products, engineering culture, or scale, and how does it connect to what you're looking for next?

“I went in thinking this was just a warmup and kind of winged it.”

View Post

Fidelity·Software Engineer·Technical Phone Screen

May 2026
Fidelity software engineer interview with a string algorithm problem that looked approachable at first but had some real depth once you got into the tradeoffs.
  • Given a list of strings, find the longest substring that appears in every string in the list. For example, given ['disgraceful', 'grace', 'gracefully', 'graceful'], the answer is 'grace'.

“I went straight for the brute force: take the shortest string, iterate over all its substrings, check each one against the rest.”

View Post