Fidelity HackerRank & Codility Assessment: What to Expect (2026)

Last updated: October 2026

Quick Answer

Fidelity technology candidates report an early online assessment on HackerRank or Codility, usually one or two data structures problems plus a SQL question, and the reported length ranges from about one hour to two hours depending on the team and year. Fidelity does not publish the format, so confirm vendor and time limit with your recruiter. Drill the problem types in OphyAI Coding Interview as practice, and rehearse the follow-up conversation in OphyAI Interview Practice.

Part	What candidates report
Platform	HackerRank or Codility; one guide also mentions HirePro
Length	60-90 minutes in one guide, 90-120 minutes in another, 1 hour with 3 coding questions in a 2019 report
Coding	One or two standard data structures problems: arrays, strings, stacks, queues
SQL	A query using joins or aggregation
Next step	A technical conversation, often with a behavioral half

What Fidelity Is Testing in This Round

The assessment is a filter for fundamentals, not a competition. Candidate reports describe moderate problems, so interviewers are checking that you can write correct, readable code on a clock.

• Correctness on edge cases. Empty inputs, duplicates and single elements are where partial credit is lost.
• Readable code. The fuller Fidelity interview guide notes that live rounds ask about real implementation details, so write code as you would submit it for review.
• SQL fluency. A join or group-by you can write without looking anything up.
• Time management. Finishing the easy parts first.

What to Expect

Invitation. The link usually arrives by email after the recruiter screen. Read the instructions page for the time limit, allowed languages and whether the camera, copy-paste or tab switching are monitored. Proctoring settings vary by employer, so rely on the instructions you receive.

Format. Reports describe a timed session with a couple of coding problems and a SQL question. One guide describes multiple-choice technical questions alongside coding on HirePro or HackerRank. Another says Java is common in later rounds.

Language. Choose the language you are fastest in, unless the invitation restricts it.

Timeline. Glassdoor reports put software engineering hiring at about 17 days overall (self-reported), so the assessment is typically in the first one or two weeks.

Example Questions and How to Answer Them

These are representative of the problem types candidates describe, not actual Fidelity questions.

1. Array: find duplicates or the two numbers that sum to a target. Start with a hash map, state the time and space cost, then handle empty and single-item inputs.
2. String: check whether two strings are anagrams or reverse words. Use a counter or sort, and mention case and whitespace assumptions.
3. Stack or queue: validate brackets or implement a queue with two stacks. Narrate the invariant you maintain.
4. SQL join: list customers with no orders. Use a LEFT JOIN with a null filter and explain why an INNER JOIN would drop them. The SQL interview questions pillar has more patterns.
5. SQL aggregation: top three accounts by balance per region. Use GROUP BY with a window function or a filtered subquery.

How to Prepare in 3 Days

Day 1. Solve four array and string problems with a timer, and write the brute force first. Day 2. Do two stack or queue problems and five SQL queries covering joins, GROUP BY and HAVING. Day 3. Take one full timed mock with the same platform editor if you can, then review mistakes.

Use OphyAI Coding Interview to practice problem walkthroughs, and start practicing → the follow-up technical conversation in Interview Practice. Do not use live AI help during the assessment: automated platforms are often proctored, and you should follow the rules in the invitation. The tracker of employers and their AI rules lists what employers have published.

Common Mistakes

Skipping edge cases. Test empty and single-element inputs before submitting.

Over-engineering. A clear O(n) with a hash map beats a clever trick you cannot explain.

Weak SQL. Many candidates prepare only algorithms. Practice joins until they are automatic.

Ignoring the clock. Submit working partial solutions rather than one perfect answer late.

Forgetting the follow-up. Be ready to explain every line you wrote in the next interview.

Related Guides

• Fidelity interview guide (hub)
• Vanguard interview guide
• BlackRock interview guide
• Affirm HackerRank online assessment

Frequently Asked Questions

Does Fidelity use HackerRank or Codility?

Candidate reports describe both, depending on the team. A typical technology assessment has one or two data structures problems plus a SQL question. Fidelity has not published the vendor or format, so ask your recruiter which platform you will use and how long you will have before you start preparing.

How long is the Fidelity online assessment?

Reports conflict. One guide says about 90 to 120 minutes with multiple-choice and coding questions, the hub guide’s sources suggest 60 to 90 minutes, and a 2019 candidate described one hour with three coding questions. Your invitation shows the exact limit, so read it on arrival and plan your time per question.

What difficulty are the Fidelity coding questions?

Candidates describe simple to moderate problems such as joins, arrays, stacks and queues rather than hard graph or dynamic programming questions. Readable code and edge-case handling are reported to matter more than clever tricks. Prepare the fundamentals thoroughly, especially arrays, strings, hash maps and SQL joins, and time yourself on each practice problem.

Is the Fidelity assessment proctored?

Fidelity has not published proctoring rules that this guide could verify. Platforms like HackerRank and Codility offer optional monitoring that employers can switch on, so read the instructions in your invitation and follow them. Do not rely on any tool that breaks the stated rules.

What happens after the Fidelity assessment?

Candidates describe a technical conversation, often a one-hour slot split between behavioral and technical questions, followed by a manager or panel round. One candidate described a manager round with a coding segment in Python and SQL. Expect questions about the code you wrote and about projects on your resume.

Sources and verification notes

Sources checked October 2026 through search summaries; the pages could not be opened from the publishing environment. Fidelity has not published its assessment format, so everything here is candidate-reported or third-party. Confirm with your recruiter.

• Interview Query, Fidelity software engineer guide: HackerRank or Codility, data structures plus SQL. Third-party, checked October 2026.
• TechPrep, Fidelity interview process: the 90-120 minute length, HirePro mention and 17 and 28 day timeline estimates. Third-party, checked October 2026.
• Glassdoor, Fidelity Investments interview report (Chennai, August 2021): a HackerRank test as the first round. Self-reported, checked October 2026.
• Glassdoor, Fidelity Investments interview report (older): an older report of a one-hour test with three coding questions (the search summary dated it 2019). Self-reported, checked October 2026.