After meeting a FactSet engineer on the floor of a career fair and having a brief chat and 2 technical questions right there, I had a phone interview in a few weeks with more chatting and technical questions. All the questions were relatively easy, and the phone screener was an engineer that went down the rabbit hole with increasingly complex topics based off of what we were talking about, which was an interesting discussion method.
Unfortunately, I took too long on some questions even though I arrived at viable answers. I didn't know when to stop because the interviewer seemed apathetic and wasn't willing to say "That's enough" even when I checked with him whether that was what he wanted. I think this led to me being rejected.
Even so, it was a fun technical discussion during the interview.
Apply amortized cost analysis to Arrays versus Vectors.
Go onto collabedit.com/ and write a fibonacci function returning the nth fibonacci number.
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.