Autocoder

Fidelity Investments interview questions with answers (engineers)

Last updated 2026-11-19

Fidelity Investments runs a global capability centre in India with sites in Bengaluru and Chennai, and an early-career programme for graduates. Candidates commonly describe interviews that cover core programming, Spring and database behaviour, cloud basics and Agile practice, followed by behavioural questions about customer focus and teamwork.

The thirteen questions below are practice in that style, with worked answers. They are not past questions. For the online assessment, see Fidelity Investments coding round questions.

Typical rolesAssociate software engineer and early-career roles (Bengaluru, Chennai)
Rounds, as commonly reportedOnline assessment, technical interviews, HR or managerial round
Heavy topicsJava, Spring, SQL, AWS basics, Agile, testing
Hiring newsSee Hiring status below

Rounds as commonly reported

Candidates commonly report an online assessment with aptitude and coding, then technical interviews and an HR or managerial conversation. The format depends on the role, campus and year, so rely on your own invitation.

Technical interviews usually follow your resume: a Java and Spring project invites questions on transactions and design principles, and a cloud or front-end project invites AWS or React questions. Prepare to explain trade-offs and the reason behind each technology choice.

What to prepare

Hiring status

There is no Fidelity Investments hiring-news page on this site, and this page quotes no hiring numbers, dates or packages because none are sourced here. There is no hiring-news page for Fidelity on this site, and no dates, openings or packages are quoted here. Use the India careers site, including its Early Career section, for current roles and eligibility.

There is no hiring-news page for Fidelity on this site, and no dates, openings or packages are quoted here. Use the India careers site, including its Early Career section, for current roles and eligibility.

Fidelity Investments interview questions with answers (engineers): questions with worked answers

  1. 1

    Explain the SOLID principles with a short example for each.

    medium

    Single responsibility: a class has one reason to change, so keep invoice calculation separate from invoice printing. Open/closed: extend behaviour by adding classes, not editing tested ones, for example new fee rules as new implementations of a FeeRule interface. Liskov substitution: a subclass must work wherever its parent is expected, so a ReadOnlyAccount that throws on deposit breaks it. Interface segregation: prefer several small interfaces to one large one. Dependency inversion: depend on abstractions and inject implementations, which is what Spring does. Be ready to name a violation you have seen in your own code.

  2. 2

    What does @Transactional do in Spring, and what are propagation and rollback rules?

    hard

    It wraps a method in a database transaction through a proxy: the transaction begins before the method, commits on success and rolls back on failure. By default it rolls back for unchecked exceptions but not for checked ones unless you set rollbackFor. Propagation controls what happens when a transactional method calls another: REQUIRED joins the existing transaction (the default), REQUIRES_NEW suspends it and starts a separate one, which is useful for audit logging that must survive a rollback. Because it is proxy-based, calling a @Transactional method from within the same class bypasses the proxy and the annotation has no effect.

  3. 3

    Explain S3, EC2 and Lambda in AWS, and what least privilege means in IAM.

    medium

    S3 is object storage for files of any size, accessed by key and highly durable. EC2 gives virtual machines you configure and manage, billed while they run. Lambda runs functions in response to events without managing servers, billed per execution, with limits on duration and memory. IAM controls who can do what: least privilege means granting only the permissions needed for a task, scoping them to specific resources, and preferring roles with temporary credentials to long-lived access keys. Give the example of a service that may read one bucket and nothing else.

  4. 4

    How does React update the page when state changes, and what is the virtual DOM?

    medium

    A component re-renders when its state or props change and returns a description of the UI. React compares the new description (the virtual DOM) with the previous one, works out the minimal set of changes and applies only those to the real DOM, since touching the DOM is the expensive part. Keys on list items let React match items across renders; using the array index as a key can cause wrong behaviour when the list is reordered. Updates to state are batched and asynchronous, so use the functional form when the new state depends on the old one.

    javascript
    import { useState } from "react";
    export function Counter() {
      const [n, setN] = useState(0);
      return <button onClick={() => setN(c => c + 1)}>Clicked {n} times</button>;
    }
  5. 5

    SQL: find customers who have bought from every product category.

    hard

    This is relational division. Group each customer's purchases, count the distinct categories they bought from, and keep those whose count equals the total number of categories. COUNT(DISTINCT category) matters, since repeat purchases in one category should count once. The alternative is a double NOT EXISTS, which reads like the definition but is harder to write correctly. Handle the case of a category table with no products by deciding what 'every' means.

    sql
    SELECT p.customer_id
    FROM Purchases p
    JOIN Products pr ON pr.id = p.product_id
    GROUP BY p.customer_id
    HAVING COUNT(DISTINCT pr.category_id) = (SELECT COUNT(*) FROM Categories);
  6. 6

    How can a hash table resolve collisions, and how does the load factor matter?

    medium

    With chaining each bucket holds a list or tree of entries that hash to it; with open addressing a colliding key probes other slots in the array (linear probing, quadratic probing or double hashing). Chaining degrades gracefully as the table fills, while open addressing is cache-friendly but slows sharply at high load and needs tombstones for deletion. The load factor, entries divided by buckets, controls the trade-off: when it passes a threshold (0.75 in Java's HashMap) the table grows and rehashes, keeping average operations O(1). A poor hash function that clusters keys ruins both schemes.

  7. 7

    Describe the Scrum events and what a definition of done is.

    easy

    A sprint is a fixed period, typically two weeks. Sprint planning decides what to build; the daily stand-up synchronises the team and surfaces blockers; the sprint review shows working software to stakeholders; the retrospective improves the way of working. The product owner orders the backlog and the team commits to what it can finish. A definition of done is the shared checklist an item must meet to count as finished, such as code reviewed, tests passing, documentation updated and deployed to a test environment. Without it, 'done' means different things to different people.

  8. 8

    What makes a good unit test, and what does code coverage tell you?

    easy

    A good unit test is fast, isolated, deterministic and checks one behaviour, with a name that says what is expected. Use JUnit with arrange, act, assert, and test boundaries and failure paths as well as the happy path. Coverage reports which lines or branches ran during tests. High coverage does not prove the tests assert anything useful, but low coverage proves some code is untested. Use it to find gaps, not as a target to game.

  9. 9

    Design a service that emails monthly statements to millions of customers.

    hard

    Treat it as a batch pipeline. A scheduler enqueues one job per customer or per chunk of customers onto a queue; a pool of workers generates each statement, stores the PDF, and sends the email through a provider, with each step idempotent so a retry does not send twice (track a sent flag per customer and month). Control the rate to respect provider limits, add retries with backoff and a dead-letter queue for failures, and monitor progress and bounce rates. Protect personal data with encryption and short-lived download links rather than attaching sensitive files.

  10. 10

    Compare API keys, basic authentication and OAuth 2.0 for securing an API.

    medium

    An API key is a static secret identifying the caller, simple but weak: if it leaks it works until revoked and it says nothing about a user. Basic authentication sends a username and password with every request, acceptable only over TLS and rarely appropriate for new systems. OAuth 2.0 issues short-lived access tokens with scopes after the user or client authenticates, so access can be limited and revoked, and passwords are not shared with the API. Use OAuth for user-delegated access, and API keys, ideally with rate limits and rotation, only for low-risk service identification.

  11. 11

    Why Fidelity, and what do you know about the technology work done there?

    easy

    Base the answer on what the careers site says about its India centres and early-career programme, rather than on assumed details. Explain what interests you: technology for savings and investing, and work that serves millions of retail customers where reliability and trust matter. Link it to a project of yours that served real users, even a small one. End with what you hope to learn in the first year.

  12. 12

    Tell me about a time you went out of your way to help someone using something you built.

    medium

    Pick a real example: a classmate who used your tool, a club that needed a small website, or a junior you mentored. Explain what the person needed, how you found out (you asked, you watched them use it), what you changed and what happened. Customer focus is about understanding needs, so show that you listened before building.

  13. 13

    What motivates you at work?

    easy

    Give an honest answer linked to examples: solving a hard problem, seeing users benefit from something you built, learning a new area, or working well in a team. Support it with one story from a project in which that motivation showed. Avoid answers that are only about pay or title, and avoid claiming to love everything. Link it to what the role offers.

Frequently asked questions

Does Fidelity hire freshers in India?

Its India careers site has an Early Career section. Check it for current programmes and eligibility, since this page quotes no dates or numbers.

Which technologies come up in Fidelity interviews?

Commonly Java, Spring, SQL, cloud basics and front-end frameworks, depending on the team and your resume.

How should I prepare for the HR round?

Prepare stories on customer focus, teamwork and motivation, each with a concrete example and outcome.

Where can I see current openings?

Use the Fidelity India careers site. The facts above come from that site and are cited in the hiring section.

Sources

Related guides

More in Company Interview Questions

See all in this section