← Back to Directory

Fidelity

Large Enterprises

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

7 interview notes · updated Jun 2026

Fidelity·Software Engineer·Technical Phone Screen

Jun 2026
Fidelity software engineer interview with a string algorithm problem that looked approachable until you had to actually defend your approach. The interviewer wanted to talk through tradeoffs, not just get an answer.
  • Given a list of strings, find the longest substring that appears in all of them. For example, given ['disgraceful', 'grace', 'gracefully', 'graceful'], the answer is 'grace'.

“I went with the simpler approach: find the shortest string in the list, binary search on substring length, then check each candidate against the rest.”

View Post

Fidelity·Backend Engineer·Onsite - System Design / Architecture

May 2026
Fidelity backend interview that went deep on Redis cache consistency patterns. One question but they really wanted to see if you could reason through trade-offs on the fly, not just recite patterns.
  • How do you handle data inconsistency between Redis and the underlying database? Walk through the patterns you'd consider and their trade-offs.

“I started with cache-aside since that's the most common, but they pushed back pretty fast asking about race conditions.”

View Post

Fidelity·Software Engineer·Technical Phone Screen

May 2026
SQL-heavy technical screen for a software engineer role at Fidelity. The whole session basically orbited one query problem but they pushed pretty hard on variations and edge cases, so it felt meatier than a typical single-question round.
  • Given an Employee table with id and salary columns, write a SQL query that returns the third highest distinct salary. If fewer than three distinct salaries exist, the query should return NULL. Walk through multiple approaches and be ready to generalize to the Nth highest.

“Started with the OFFSET approach because it felt cleanest: pull distinct salaries, order descending, LIMIT 1 OFFSET 2.”

View Post

Fidelity·Software Engineer·Recruiter / HR Screen

May 2026
Fidelity full-stack engineer screen with what seemed like a standard motivational question about the company. Short and focused, nothing too surprising.
  • Why do you want to work at Fidelity specifically? What about their products, engineering culture, or mission connects to what you're looking for next?

“I fumbled this a bit because I went too generic at first, said something about scale and fintech and the interviewer kind of waited for more.”

View Post

Fidelity·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Fidelity for a full-stack role. Just the one question about dealing with setbacks during an internship, so it was pretty short.
  • Tell me about a time you hit a wall or ran into frustration during an internship. What happened, how did you handle it, and what did you take away from it?

“Pretty standard behavioral prompt but I fumbled the landing a bit.”

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 whole conversation basically lived in multi-datasource JPA territory, which I hadn't fully reviewed.
  • How would you configure two separate datasources in a single Spring Boot application?
  • Walk me through setting up separate EntityManagerFactory and TransactionManager beans for each datasource.
  • How do you scope JPA repositories so each one uses the correct datasource and transaction manager?
  • What are common pitfalls when running two datasources alongside Spring Boot's auto-configuration?
  • When would you need distributed transactions across two datasources, and how would you handle that in Spring?

“I started okay, talked about defining two DataSource beans and using @ConfigurationProperties to bind each one from separate property prefixes.”

View Post

Fidelity·Backend Engineer·Technical Phone Screen

Apr 2026
Technical phone screen for a backend role at Fidelity, focused pretty heavily on Spring internals. One question, but it had a lot of layers and I definitely didn't cover all of them cleanly.
  • How do @Transactional's rollbackFor and noRollbackFor attributes work, including their default behavior, how they interact when both are set, and what common pitfalls exist around them?

“I knew the basics: Spring only rolls back on RuntimeException and Error by default, checked exceptions slip through unless you explicitly add them via rollbackFor.”

View Post