Getting an Interview
Getting an Interview
Interviews for Top Jobs at FactSet
- Consultant (161)
- Software Engineer (121)
- Graduate Consultant (19)
- Research Analyst (16)
- Financial Consultant (8)
- Financial Engineer (8)
- Software Engineer I (7)
- Senior Software Engineer (7)
- Software Developer (6)
- Product Developer (4)
- Equity Research Analyst (4)
- Research Specialist (3)
- Software Engineer Intern (3)
- Research Associate (3)
- QA Analyst (2)
- Quality Assurance Analyst (2)
- Systems Engineer (2)
- Database Administrator (2)
- Associate Content Manager (2)
- Intern (2)
- Product Specialist (2)
- Sales Specialist (2)
- Senior Consultant (2)
- Fixed Income Consultant (1)
- Graphic Designer (1)
- Content Analyst (1)
- Content Manager (1)
- Content Specialist (1)
- Product Consultant (1)
- Team Leader (1)
Software Engineer Intern Interview
I applied online. The process took 2 weeks – interviewed at FactSet in April 2013.
Met with a company recruiter at a school career fair, handed in my resume, and also applied online. Soon, was contacted via e-mail to setup a phone interview. Was asked to describe stack vs. heap allocated memory, the usefulness and time-complexities of various arraylist operations, and the applications of hashmaps. Finally, was asked to implement a program that determined if a given integer array was a palindrome.
- For the final question, the interviewer asked me to hand-write the code and explain it to him over the phone. Moreover, he wanted verbatim code, not pseudocode. This felt pretty peculiar, but not impossible. Answer Question
Other Interview Reviews for FactSet
Software Engineering Intern InterviewApplication Details
I applied through an employee referral. The process took 6 weeks – interviewed at FactSet in January 2013.Interview Details
I had an initial phone screening which was quick and was asked some simple java questions such as the differences between an interface and an abstract class....very simple stuff. We also went through some of my previous experiences from my resume.
I was flown to their Norwalk office for an on site interview. There were four rounds where the first one was a Code Review. I was given code in C and I had to search for memory leaks and other optimizations. I had a data structures round where the question was regarding linked lists. My third interviews was regarding object oriented programming and how I would design a Chess game in java. My last interview was more casual with a senior director and had some behavioral questions.
The recruiter was very prompt and made all the traveling a seamless experienceInterview Questions
Accepted OfferPositive ExperienceAverage Interview
- design a chess game in an obejct oriented fashion Answer Question
Software Engineer Intern InterviewApplication Details
The process took a day – interviewed at FactSet in November 2010.Interview Details
I first got a phone interview through a connection at the company. I spoke with a senior developer. They asked me to send a "short sample of code" which is always scary. I chose one that I did for a class assignment as it was pretty short and it showed a few good design decisions. A word of warning, the phone interview was extremely technical. I think we spoke nearly double the 30 minute estimate and it was pretty much 90% technical. We started by going over my code, talking about decisions I made in designing it and how I could change some things in order to make it more versatile. After a long discussion, he asked the typical data structures/complexity of operations questions. Pretty standard stuff you should be ready for for any interview. He had some other questions, like how to find if a linked list has cycles, and a real-world problem of keeping track of the highest 1000 quotes as prices come in constantly. Finally we briefly discussed my previous internship and what I did, followed by him asking what I really want to do. He gave me some more information and then I got an offer to interview on-site within an hour.
The on-site interview started in the morning with a demo of the software. This was mostly just for my benefit and not really "part of" the interview (although you always have to assume people you talk to can have an influence on the people making the decision).
My first technical interview was to write out a poker function to calculate which 5 card hand wins. I had to describe basic data structures I would use for shuffling the deck and dealing cards, but the function was the main focus. I spent a good amount of time working out some issues, and made some changes as I went. I almost ran out of time and just had to explain some of the end of the code. Overall, it went well, but I only had a short time to ask questions.
The second technical interview was the "code review" interview. I was given a print out of a class. I was asked to find errors and then afterward, give it a "grade". I was also asked about some improvements I could see beyond the errors.
The final technical interview started with a short program where I was asked to write the output. It was a simple class with a derived class and it illustrated pointers/desctructors/virtual functions and determining which gets called and in what order. Pretty simple, just make sure you know things like virtual methods in C++. I was also asked to design a game like The Sims, basically just define some classes and public interfaces. We really just talked through some issues and features and how I would implement them.
Before I finished the day, I was taken out to lunch by two developers.
I finally had an interview with a director. He asked more of the basic, tell me about yourself, and how did you get interested in software development, type questions. This part was pretty relaxed and I was almost done.
I ended the day with the hiring manager, who gave me some feedback (he was pretty positive and seemed to imply that I had an offer)Interview QuestionsReasons for Declining
Received another offer in a location I wanted more. Two very similar jobs. I would have taken this one in isolation.Declined OfferPositive ExperienceAverage Interview
Software Engineer Intern Interview