Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      FactSet

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur FactSet | Offres d’emploi chez FactSet | Salaires chez FactSet | Avantages sociaux chez FactSet
      Entretiens chez FactSetEntretiens d’embauche pour Software Engineer Intern chez FactSetEntretien chez FactSet


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Software Engineer Intern

      3 mars 2011
      Candidat à l'entretien anonyme
      Norfolk, CT
      Offre refusée
      Expérience positive
      Entretien moyen

      Candidature

      Le processus a pris 1 jour. J'ai passé un entretien chez FactSet (Norfolk, CT) en nov. 2010

      Entretien

      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)

      Questions d'entretien [2]

      Question 1

      Receive 1000 bids/second for a stock. Want to store the top X bids and calculate the mean. How?
      Répondre à cette question

      Question 2

      Explain how "virtual" works in c++
      Répondre à cette question
      1

      Autres retours d’entretien d’embauche pour un poste comme Software Engineer Intern chez FactSet

      Entretien pour Software Engineer Intern

      9 avr. 2025
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez FactSet

      Entretien

      It started with a recruiter call, then technical and behavioral in following weeks. It was very typical compared to most technical role interviews, everyone was super friendly and communication was very open.

      Questions d'entretien [1]

      Question 1

      Explain how you handle conflicting deadlines.
      Répondre à cette question

      Entretien pour Software Engineer Intern

      1 juin 2024
      Candidat à l'entretien anonyme
      Manille,
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez FactSet (Manille, )

      Entretien

      After you passed the initial assessment/exam, they will send you an invitation for an initial interview, then if you passed it you will then continue to the technical interview where you will be interviewed by a software engineer and ask you a bunch of problems that analyzes your problem solving abilities as well as your knowledge when it comes to algorithms.

      Questions d'entretien [1]

      Question 1

      For the initial interview they will just ask basic questions to get to know you better such as: - tell me about yourself - your past experiences - why did you apply - what do you know about the company - do you have other pending applications to other companies
      Répondre à cette question

      Entretien pour Software Engineer Intern

      9 déc. 2023
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez FactSet en janv. 2023

      Entretien

      1. 30min OA, leetcode easy to medium. 2. 30min vedio call, asked some behavior question and tech questions about oop, database and network. and talked about projects listed on resume.

      Questions d'entretien [1]

      Question 1

      how do you think of relational database vs nodal
      Répondre à cette question