Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empleadores

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      FactSet

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de FactSet | Empleos en FactSet | Sueldos en FactSet | Prestaciones en FactSet
      Entrevistas en FactSetEntrevistas para el cargo de Software Engineer Intern en FactSetEntrevista en FactSet


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empleadores

      • Cuenta de empleador gratuita
      • Centro de empleador

      Información

      • Ayuda
      • Pautas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de autorización de cookies

      Trabaja con nosotros

      • Anunciantes
      • Oportunidades laborales
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor", "Worklife Pro", "Bowls" y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información desde adentro.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista para Software Engineer Intern

      3 mar 2011
      Candidato de entrevista anónimo
      Norfolk, CT
      Oferta rechazada
      Experiencia positiva
      Entrevista promedio

      Solicitud

      El proceso tomó 1 día. Acudí a una entrevista en FactSet (Norfolk, CT) en nov 2010

      Entrevista

      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)

      Preguntas de entrevista [2]

      Pregunta 1

      Receive 1000 bids/second for a stock. Want to store the top X bids and calculate the mean. How?
      Responder pregunta

      Pregunta 2

      Explain how "virtual" works in c++
      Responder pregunta
      1

      Otras evaluaciones sobre las entrevistas para el cargo de Software Engineer Intern en FactSet

      Entrevista para Software Engineer Intern

      9 abr 2025
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia positiva
      Entrevista promedio

      Solicitud

      Me postulé en línea. Acudí a una entrevista en FactSet

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 1

      Explain how you handle conflicting deadlines.
      Responder pregunta

      Entrevista para Software Engineer Intern

      1 jun 2024
      Candidato de entrevista anónimo
      Manila,
      Sin ofertas
      Experiencia positiva
      Entrevista promedio

      Solicitud

      Me postulé en línea. Acudí a una entrevista en FactSet (Manila, )

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 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
      Responder pregunta

      Entrevista para Software Engineer Intern

      9 dic 2023
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia positiva
      Entrevista promedio

      Solicitud

      Me postulé en línea. El proceso tomó 1 semana. Acudí a una entrevista en FactSet en ene 2023

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 1

      how do you think of relational database vs nodal
      Responder pregunta