I had applied through an employee referral. The recruiter contacted me within a week, to identify what roles I would be suitable for. Within two working days, I was invited for a phone screen. The phone screen was conducted by an engineer. The interviewer asked me about my resume and a simple coding question (sieve of Eratosthenes). I expected them to get back within a week, but to my surprise, the recruiter got back to me within a few hours, inviting me onsite for an interview.
The onsite interview began initially with a demo of the product. This demo is really helpful in formulating questions for the later rounds ;-) Coming to the technical rounds, the first of my technical rounds was a code review. The same Triangle class as the previous posters. This was followed by a coding/algorithms round.
In this round, I was asked a "starter" question, to ease me into the process. The question was to pop the minimum from the stack. This was followed by a question, explained in the next section. To answer the same we required to implement disjoint sets. I told the interviewers that I shall use a height balancing BST (like AVL).
This I said, would reduce the worst case search/insert/delete to O(log n). The interviewers probably misunderstood me, and maintained that the worst case height is O(n) for a BST (can't be denied :-) ). This was followed by a system design question, where I had to design a system for expressions (expr = literal|expr + expr|-expr) without wasting effort on parsing.
I tried to impress them with class diagrams. BIG mistake! Just write your classes and get done with it! This was followed by a round with the hiring manager. This round is essentially a resume review, and multiple technical discussions.
Finally, I was taken out for lunch by a member of the Security Assurance team. Having a background in security, he talked about the team and opportunities in them. Finally, I had a Behavioral interview with the recruiter.
They again promised to get back to me within a week, and to my surprise got back in two days!!! Alas, it was a reject, but overall an enjoyable and quick interview experience.
Given a graph and an online stream of its edges (like a social network, where edges are the friendships built at that given instant), find the first incoming edge at which the graph is fully connected!
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.