I initially applied for a job through a friend and didn't get a callback. After a few months another position opened and I applied again through the friend. A few weeks went by and they called back. First I was contacted by a recruiter, then I had a phone interview, then I came in for an in-person interview.
The in-person was a whole day. It started with a presentation of their product, then a code review, two design reviews, a lunch, and finally an interview with the director of the department.
Several days later I received a phone call with an offer.
The most difficult question presented to me was a C++ code sample that I had to review. It contained numerous logical and syntax errors, as well as poor coding. I had to debug the sample by hand and explain how I would fix the code or re-implement it. The difficulty was doing so on pen and paper and catching all of the problems, including several very subtle ones.
The following metrics were computed from 49 interview experiences for the FactSet Software Engineer role in Norwalk, Connecticut.
FactSet's interview process for their Software Engineer roles in Norwalk, Connecticut is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for FactSet's Software Engineer interview process in Norwalk, Connecticut.