Fidelity Investments India Interview Experience 2026

The on-campus story: what actually happened in the Fidelity India drive

Fidelity Investments' India centre, based in Bengaluru and functioning as a technology hub supporting the US brokerage and asset-management business, ran a 3-round on-campus fresher hiring process, per a GeeksforGeeks account titled "Fidelity Investments Interview Experience | Set 1 (On-Campus)". The drive reportedly started with about 100 applicants, narrowed down to roughly 48 candidates after the online test, and ended with 9 students selected from the cohort.

The first thing that stands out is the structure: Fidelity did not front-load a coding round in the reported on-campus cycle. Round 1 was purely verbal and aptitude, which is unusual compared with most product-company fresher drives in India that open with an automated coding test on platforms like HackerRank, CoCubes, or HirePro. This matters for your prep sequencing. If you are targeting Fidelity on-campus, your first 7 to 10 days should go into speed-maths, data interpretation, logical reasoning, and verbal ability, not LeetCode medium problems.

Round 2, the technical interview, is where the real filtering happened. The interviewer covered a wide surface area in a single round: web-services basics (REST vs SOAP), time complexity and Big-O notation, sorting-algorithm complexities, a live coding task to check whether two strings are anagrams, finding the nth-largest element in an unsorted array, spotting errors in given recursive code, a graph-based word-transformation puzzle framed as "minimum swaps to convert one string to another", multithreading and OS fundamentals (threads vs processes), Java collections, and OOP concepts. There was also a classic sock-pairing logic puzzle thrown in.

Round 3 was an HR interview focused on behavioral and culture-fit questions: motivation for joining Fidelity, awareness of competing offers, technical preferences, and preferred joining location. No deep technical grilling here, but the HR round at Fidelity is not a formality. The company places heavy emphasis on long-term retention, so answers that sound like "I will leave in 18 months for a higher package" can sink you even after a strong technical round.

Treat this as one candidate's reported on-campus cycle for a specific drive, not a universal Fidelity template. Eligibility, test pattern, and number of rounds can and do vary by campus, year, and whether the drive is on-campus or off-campus. For authoritative, current fresher-hiring details, check Fidelity's official India careers page.

Round-by-round breakdown and question map

The table below maps the 3 reported rounds, what each round tested, and the outcome at each stage. All numbers are candidate-reported, drawn from the GeeksforGeeks on-campus account, and apply to that specific drive only.

Topic frequency in the technical round

If you cluster the reported Round 2 questions by topic, a clear prep priority emerges.

The graph-based minimum-swaps question is the hardest single item in this list. It is essentially a cycle-detection problem on a permutation, and it shows up across multiple company drives, not just Fidelity. If you can code the minimum-swaps-to-sort-an-array pattern and adapt it to string conversion, you cover a large class of follow-up puzzles.

The 2026 playbook: how to prep for a Fidelity India on-campus drive

If your campus is expecting a Fidelity Investments India visit in the 2026 placement season, here is a concrete, week-by-week prep plan grounded in the reported question set.

Week 1 to 2: Aptitude and verbal speed

Since Round 1 in the reported cycle was aptitude-only with no coding, allocate the first two weeks to quantitative aptitude, logical reasoning, and verbal ability. Use standard prep books or free online question banks. Target 30 to 40 questions in 30 minutes with 85 percent accuracy. This is the gate. If you do not clear Round 1, your DSA skills never get tested.

Week 3 to 5: DSA core and complexity analysis

Pick the exact topics that showed up in the reported technical round:

• String problems: anagram check, palindrome variants, minimum swaps to convert one string to another.
• Array problems: nth-largest element, kth-largest using quickselect, sorting-based approaches.
• Graph problems: cycle detection for the minimum-swaps pattern, BFS for word-transformation puzzles.
• Complexity: Big-O for all major sorting algorithms, best and worst cases, space complexity trade-offs.

Practice each pattern on LeetCode or GeeksforGeeks until you can code it in under 15 minutes without referring to editorial.

Week 6: Core CS and Java

The reported round asked multithreading fundamentals, threads vs processes, recursion debugging, Java collections, and OOP concepts. You do not need OS textbook depth, but you should be able to explain:

• Process vs thread, context switching cost, when to use multithreading.
• Java Collections Framework: HashMap internals, ArrayList vs LinkedList, HashSet vs TreeSet.
• OOP pillars with real examples: encapsulation, inheritance, polymorphism, abstraction.
• Common recursion bugs: missing base case, off-by-one in recursive call, stack overflow.

Week 7: HR round and mock interviews

Prepare 5 to 7 STAR-format stories: a project you owned, a team conflict you resolved, a bug that took 3 days to fix, a time you learned a new tool fast, and why Fidelity specifically. Research Fidelity's business model: it is a privately held US financial services corporation, and the India centre works on brokerage and asset-management technology. Saying "I want to work in fintech" is generic. Saying "I want to build systems that serve Fidelity's retail brokerage platform at scale" is specific and scores higher.

Week 8: Full mock cycle

Run a full 3-round mock with a peer or senior. Round 1: 30-minute aptitude set. Round 2: 45-minute technical with the exact question types listed above. Round 3: 15-minute HR. Record yourself, review where you stalled, and re-run the weak round.

Common mistakes and red flags to avoid

• Ignoring aptitude because you are strong at DSA. In the reported cycle, Round 1 was aptitude-only. Brilliant coders who skip aptitude practice get filtered before the technical round.
• Memorising REST vs SOAP definitions without context. Interviewers follow up with "when would you pick SOAP over REST in a real Fidelity system?" Have a use-case ready, not just a textbook line.
• Saying you have no competing offers when you do. The HR round explicitly asked about competing offers. Lying here can cost you the offer if background checks or later conversations surface the truth.
• Treating the HR round as a formality. Fidelity is known for long tenures. Answers signalling quick departure for a higher package are a red flag for the panel.
• Not knowing what Fidelity actually does. Calling it "a bank" or "a generic IT company" in the HR round signals zero research. It is a brokerage and asset-management firm, and the India centre supports that US business.
• Conflating eligibility across drives. A separate off-campus Fidelity drive reportedly used a 7 CGPA plus 65 percent in 10th and 12th bar. Do not assume that applies to your on-campus cycle. Confirm on the official careers page.

Real-world data points

• 3 rounds in the reported on-campus Fidelity India drive, per the GeeksforGeeks account.
• About 100 applicants at the start of the process.
• Roughly 48 candidates advanced past the Round 1 online aptitude test.
• 9 students were finally selected from the cohort.
• Round 1 had zero coding questions, verbal and aptitude only, candidate-reported.
• Round 2 covered at least 12 distinct technical topics in a single interview.
• A separate off-campus Fidelity drive reportedly used a 7 CGPA plus 65 percent in 10th and 12th eligibility bar, but this is a different cycle and should not be conflated.
• No package figure or CGPA cutoff was disclosed in the on-campus account, as posted on GeeksforGeeks.

Sources & credits

• https://www.geeksforgeeks.org/fidelity-investments-interview-experience-set-1-on-campus/