Fidelity Backend Engineer interview questions

3 Backend Engineers have shared notes from their Fidelity interviews, with the questions they were asked in each round. That is 43% of the 7 Fidelity interview notes on Screna AI.

3 Backend Engineer interview notes

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