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.” The rest of the author's notes on Backend Engineer interview at Fidelity, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post