← Back to Directory

Fidelity interview notes, page 1 of 2

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·Backend Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Fidelity for a backend role, pretty deep dive into caching consistency. One main topic but they really wanted you to go wide on it, not just recite patterns but actually reason through the trade-offs for different workloads.
  • How do you handle data inconsistency between Redis and the underlying database? Walk through the patterns you know and their trade-offs.

“This question is wider than it looks.”

View Post

Fidelity·Backend Engineer·Technical Phone Screen

Apr 2026
Technical screen at Fidelity for a backend role, pretty deep on Spring Boot internals. The multi-datasource question was the centerpiece and they clearly wanted more than surface-level answers.
  • Walk me through how you'd configure two separate databases in a single Spring Boot application, including transaction management and repository scoping.
  • What are the common pitfalls when mixing JdbcTemplate and JPA across two datasources in the same application?
  • When would you actually need JTA or distributed transactions instead of just managing two separate transaction managers?

“This is the kind of question where you can start confidently and then slowly realize how many layers there are.”

View Post

Fidelity·Software Engineer·Technical Phone Screen

Apr 2026
SQL-heavy technical screen for a software engineer role at Fidelity. The main focus was a classic ranking problem but they pushed pretty hard on edge cases and generalizing the solution, which I wasn't fully prepared for.
  • Given an Employee table with id and salary columns, write a SQL query to return the third highest distinct salary. If fewer than three distinct salaries exist, return NULL. Be prepared to discuss multiple approaches and generalize to the Nth highest.

“Started with the DENSE_RANK() approach because it felt cleanest, wrapping it in a CTE and filtering where rank = 3.”

View Post

Fidelity·Software Engineer·Technical Phone Screen

Apr 2026
Fidelity technical screen for a software engineer role, heavy on Java concurrency. The whole conversation basically revolved around one big topic but they went deep enough that it felt like multiple questions rolled into one.
  • Walk me through how you handle concurrency in Java, covering threads, the Executor framework, synchronized blocks, explicit locks, atomic variables, concurrent collections, and futures including CompletableFuture.
  • How do you avoid race conditions, deadlocks, and starvation in a concurrent Java application? Give concrete examples.

“This is a lot to hold in your head at once.”

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

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

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·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
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·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