I interviewed for the NYC office. The entire process took about 2 weeks, with the longest gap being after I completed Stage 1. Stages 2-4 were all only a couple of days apart.
Stage 1: 45-minute HackerRank OA (easy-medium recursion problem) Stage 2: 45-minute HackerRank CodePair (easy-medium hashmap problem) Stage 3: 15-minute HR Phone Screen ("how did your tech interview go? when would you be able to start? do you need a visa/sponsorship to work? what salary are you looking for?") Stage 4: 3-hour "Super Day" Final Rounds Round 1: Data structures and algorithms ("define polymorphism", "tell me what an interface is", linked lists and manipulating linked lists, time complexity, space complexity) Round 2: Design ("design a continuous integration workflow/entity diagram, and then code it up") Round 3: HR ("why FactSet? why did you go into CS? who's your favorite computer scientist? what do you like/dislike about functional vs. object-oriented programming? what about strongly typed vs weakly typed languages?")
I do want to note that I put difficulty as "Easy" which may sound weird because I didn't get an offer, but it's because I just imploded due to anxiety in the final rounds. They give the impression that you're very likely to get an offer if you make it past the first three stages.
The following metrics were computed from 215 interview experiences for the FactSet Software Engineer role in United States.
FactSet's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for FactSet's Software Engineer interview process in United States.