FactSet software engineer candidates report an online coding assessment, DSA-focused technical interviews, and an HR or managerial conversation. Some also describe system design, a take-home project, or project deep dives.
$115K
Avg. Base Comp
$134K
Avg. Total Comp
3-5 rounds
Typical Rounds
3-4 weeks
Process Length
FactSet software engineer candidates describe a process that is mostly practical coding, with the exact shape varying by team and location. The most common opener is a HackerRank-style assessment: candidates report two to three problems, including greedy and sliding-window questions, and one candidate saw hidden test cases that rewarded optimized solutions over brute force. Live technical rounds then lean on arrays, strings, linked lists, trees, graph traversal, and time-complexity explanations, with some reports of Python, Java, OOP, SQL, and database fundamentals.
Not every candidate saw the same format. One reported a 90-minute machine-coding round followed by DSA and a combined behavioral and Ticketmaster-style design round that probed double-booking and consistency. Another received a Node.js and MongoDB take-home, then discussed schema design and queries in two interviews and received an offer. Others described system design and detailed resume project walkthroughs, where high-level summaries were not enough.
Prepare to explain your reasoning aloud, state complexity, and defend design choices. Interviewers are often described as friendly and willing to give hints. Final conversations are reported as HR, managerial, or hiring-manager rounds covering teamwork, motivation for FactSet, and logistics such as location or schedule. Outcomes were mixed, so treat the technical bar as real even when the tone is collaborative.
Synthesized from 13 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Factset process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Factset
Given an integer N, write a function that returns all of the prime numbers up to N
| Question | |
|---|---|
| Find the Missing Number | |
| Rectangle Overlap | |
| String Subsequence | |
| Triplet Counting | |
| Nearest Common Ancestor | |
| Groups of Anagrams | |
| Radix Addition | |
| Dijkstra implementation | |
| Find Duplicate Numbers in a List | |
| Hurdles In Data Projects | |
| Target Indices | |
| Messenger Service Design | |
| Filling Supermarket Bag | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Binary Tree Validation | |
| Ticket Reservation Locking | |
| String Palindromes | |
| NxN Grid Traversal | |
| Data Stream Median | |
| Rearranging Digits | |
| Impossibly Iterative Fibonacci | |
| Processing Large CSV | |
| LRU Cache 1 | |
| Singly Linked List | |
| Design Poker Schema | |
| Length Of Longest Palindrome | |
| Google Docs Autosave System | |
| 2nd Highest Salary | |
| Merge Sorted Lists |
Synthesized from candidate reports. Individual experiences may vary.
Candidates commonly report starting with an online assessment, often on HackerRank. Reports mention two to three problems, including greedy and sliding-window questions, and one candidate noted hidden test cases that required optimized solutions. Some reports also mention CS fundamentals or an Excel test in internship flows.
Not every candidate reports this step. One described a 90-minute machine-coding round where requirements had to become working code. Another reported a several-day Node.js and MongoDB backend take-home, which was later discussed in interviews. It may depend on team, so confirm with your recruiter.
Candidates report one to three technical interviews, in person, virtual, or phone depending on the account. Topics include arrays, strings, linked lists, trees, graph traversal, rotated-array search, complexity analysis, Python or Java, OOP, SQL, and database concepts. Interviewers are often described as supportive and some offered hints.
Several candidates describe design or project depth. Reports include a Ticketmaster-style design with consistency and double-booking questions, a Kafka-like system mentioned by one candidate, and resume project walkthroughs covering architecture, trade-offs, and personal contribution. Prepare to defend decisions rather than only list technologies.
The final stage is typically reported as an HR, managerial, or hiring-manager conversation. Candidates mention teamwork, overcoming challenges, why FactSet, availability or schedule flexibility, and relocation. One candidate who took a different path found the hiring-manager questions misaligned with the job description.
