Taro Logo

Software Engineer Interview Experience - United States

May 22, 2015
Positive ExperienceGot Offer

Process

I got a call from someone in HR, and we talked about my classwork and school projects. A few weeks later, I got an email telling me that there were some openings, and we scheduled a technical phone interview.

The phone interview was very straightforward. They asked me about basic OOP questions (ex. polymorphism, generics, access modifiers). I was notified the next day that I had passed this round and we scheduled on onsite interview.

There were seven sessions: product demo, three technical interviews, HR interview, lunch, and interview with the director.

Technical interview one: They gave me C++ code for a linked list, and asked me to determine the output and to suggest improvements for the code. Even though I don't know C++, I was still able to follow the code based on my Java skills.

Technical interview two: Code a stack with push(), pop(), and getMin() at O(1).

Technical interview three: Class diagrams for a car rental service and corresponding database tables.

HR interview: We went over the previous interviews, and then there were some behavioral questions.

Director interview: Array based question - no coding here, just discussed approach to solving the problem.

They said that I would hear back in two weeks, but I got a call just two days later with an offer.

Questions

  1. Linked List code review.
  2. Code a stack.
  3. Design question.

Was this helpful?

Interview Statistics

The following metrics were computed from 215 interview experiences for the FactSet Software Engineer role in United States.

Success Rate

26%
Pass Rate

FactSet's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive62%
Neutral22%
Negative16%

Candidates reported having very good feelings for FactSet's Software Engineer interview process in United States.

FactSet Work Experiences