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

      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

      CTC Group

      ¿Esta es tu empresa?

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre CTC Group | Ofertas de empleos en CTC Group | Sueldos en CTC Group | Beneficios en CTC Group
      Entrevistas de CTC GroupEntrevistas para el puesto de Senior Software Developer en CTC GroupEntrevista de CTC Group


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empresas

      • Cuenta gratuita de empresa
      • Centro de empresas

      Información

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

      Trabaja con nosotros

      • Anunciantes
      • Empleo
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Indeed, Inc. «Glassdoor», «Worklife Pro», «Bowls» y sus logotipos son marcas comerciales registradas de Indeed, Inc.

      Empresas seguidas

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

      Búsquedas de empleo

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

      Entrevista de Senior Software Developer

      30 oct 2024
      Empleado anónimo
      Oferta aceptada
      Experiencia positiva
      Entrevista fácil

      Solicitud

      El proceso duró 2 meses. Acudí a una entrevista en CTC Group en ene 2021

      Entrevista

      he interview process was pretty comprehensive, and I’d say it covered a lot of important areas. First, there was an initial screening, which was more about checking my basic qualifications and seeing if I matched their requirements. After that, I had a technical interview. They really went into depth about my skills and past experiences, especially focusing on the technologies and frameworks I’d worked with, like .NET and backend systems. They asked a few coding questions too, to get a feel for how I approach problem-solving. Then there was a practical assessment where I had to solve a real-world problem. This was challenging but also rewarding because it let me showcase how I’d handle tasks I’d actually face in the role. After the technical rounds, I had a more personal, cultural interview. They wanted to understand if I’d be a good fit for their team and company culture. I talked about my experiences working with cross-functional teams and how I approach collaboration, which is crucial in engineering roles. In the end, it felt like a well-rounded process where they got a good picture of both my technical skills and who I am as a person. I appreciated that they took the time to really understand me and my capabilities.

      Preguntas de entrevista [6]

      Pregunta 1

      Describe the architecture of one of your previous projects. How did you decide on the components and interactions?
      Responder pregunta

      Pregunta 2

      What is your process for identifying the root cause of a performance issue in a distributed system?
      Responder pregunta

      Pregunta 3

      How do you support junior developers on your team? Can you share an example of a time you helped a team member grow?
      Responder pregunta

      Pregunta 4

      Describe a time when a project didn’t go as planned. What did you learn from it, and how did you apply that lesson in future projects?
      Responder pregunta

      Pregunta 5

      How do you handle last-minute changes to project requirements or scope? Share an example.
      Responder pregunta

      Pregunta 6

      What’s your approach to documenting code and processes? How do you balance between too much and too little documentation?
      Responder pregunta