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

      Unity

      ¿Esta es tu empresa?

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Unity | Empleos en Unity | Sueldos en Unity | Prestaciones en Unity
      Entrevistas en UnityEntrevistas para el cargo de Senior Software Engineer en UnityEntrevista en Unity


      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 Senior Software Engineer

      10 dic 2021
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia negativa
      Entrevista promedio

      Solicitud

      Me postulé a través de un reclutador. El proceso tomó 3 semanas. Acudí a una entrevista en Unity en nov 2021

      Entrevista

      As a foreword, I'd like to thank the people who I talked to during the process: Technical Sourcer, Principal Technical Recruiter, and one of the software engineers. I did enjoy speaking to all of you and I appreciate the fact that I got the feedback with the interviewer's remarks. This was extremely helpful. First, I had a call with a "Technical Sourcer". He briefly described the position details, answered my questions, and requested a CV. Then, I had a technical interview with one of the engineers. I went through my experience, asked a couple of questions about the technologies and tasks. The third stage is a take-home task. The fourth is a call with a hiring manager, but I never reached it. Let me please describe the reason I marked my experience 'negative'. The main reason is the assessment of the take-home task. The take-home quiz contained 9 tasks. The first 7 are theoretical questions with examples. The last two are coding tasks. I enjoyed the quiz very much. It was quite interesting. However, I got 0 marks for 4 theoretical questions out of 7. I was very curious, how could I have a 0/3 mark for a question, especially as I didn't have any difficulties answering it. The quiz header contained general rules for the answers: "Answer with bullet points; Single sentence per bullet point; Max 4 per question". As this was a separate requirement in the header of the document, my thought was that they intentionally don't want to see a candidate dive too deep or something like that. I followed the rules strictly. In addition to that, all the questions had "list" or "name" issues you see, but none of the questions had "describe the ways to mitigate". Thus, my answers were 1-sentence not-more-than 4 per question and did name the issues only, not touching on ways to correct the mistakes. As a result, the reviewer commented on two of the questions that "explanation here is quite generic and does not propose a solution". This way, I got 0/3 and 0/2. The other two questions I got 0 marks for were codereview samples. There were flaws there so I admitted them and moved on. Strangely, the rest of the questions were marked excellent and no one asked for more details. At the same time, they mentioned, they liked my coding and they liked one of my answers on the db-related theoretical question. I contacted them trying to reasonably explain myself and my vision of the situation. However, they didn't see any controversies in task requirements and reviewer's comments. The final answer was "We have candidates who have passed this stage and we know the assignment works well". None of my arguments worked. I do not know the future, however, right now I am not considering to re-apply later. In my opinion, the company is interested in candidates. At the same time, I consider all that happened to me as a some kind of bureaucratic act or lack of flexibility. Or maybe I am not reasonable, it's up to you to decide.

      Preguntas de entrevista [1]

      Pregunta 1

      I don't recall any specific questions before the quiz. There were generic questions about my experience in one of my previous companies. I prefer not spoiling the quiz, however, as I don't think this is fair. My apologies.
      1 respuesta
      2

      Otras evaluaciones sobre las entrevistas para el cargo de Senior Software Engineer en Unity

      Entrevista para Senior Software Engineer

      21 abr 2026
      Empleado anónimo
      Mountain View, CA
      Oferta aceptada
      Experiencia positiva
      Entrevista promedio

      Solicitud

      Me postulé a través de un reclutador. El proceso tomó 4 semanas. Acudí a una entrevista en Unity (Mountain View, CA) en mar 2026

      Entrevista

      Overall, I had a very positive experience. The process was a bit long (a little over a month), but it also included the Easter holiday period in Europe/Montreal. The process was: HR phone screen, hiring manager interview, take-home assignment, technical round, and three virtual onsite rounds (Product, Behavioral, and ML knowledge), followed by the final decision. There was only one coding assessment, in take-home format. The algorithm/design pattern/GitHub parts were quite basic. There was also some web development content (CSS/HTML layout), which was more challenging for me since that is not my primary area. I then had a technical round that focused mostly on past experience rather than the take-home assignment itself. In the virtual onsite rounds, the last ML round covered many ML topics. I prepared a lot and was able to answer many of them, though not all. The interviewer was very helpful and willing to share knowledge, which I appreciated.

      Entrevista para Senior Software Engineer

      22 ago 2025
      Candidato de entrevista anónimo
      Israel
      Sin ofertas
      Experiencia positiva
      Entrevista promedio

      Solicitud

      Acudí a una entrevista en Unity (Israel)

      Entrevista

      The interview process began with a phone call with a recruiter, followed by a Zoom technical interview with the team leader, who asked about my experience. After that, I had two system design interviews, and finally an HR and senior manager interview.

      Preguntas de entrevista [1]

      Pregunta 1

      Design Bitly – URL shortening service. Design recommendation server – you receive a list of campaigns and filter them based on business logic.
      Responder pregunta

      Entrevista para Senior Software Engineer

      14 ago 2025
      Empleado anónimo
      Copenhague, Hovedstaden
      Oferta aceptada
      Experiencia positiva
      Entrevista promedio

      Solicitud

      Me postulé en línea. El proceso tomó 4 semanas. Acudí a una entrevista en Unity (Copenhague, Hovedstaden) en jul 2025

      Entrevista

      I started with an initial conversation with Recruiter team, where the process was clearly explained to me. After that, I quickly moved to a high-level discussion with the hiring managers about the team’s architecture and specific needs. I was then guided into several technical interview rounds — about four sessions, each lasting around 45 minutes. These included both team members and experienced professionals from outside the team, with diverse backgrounds. Almost every stage included a coding assignment component, as well as high-level discussions and deep dives into relevant parts of my background. The entire process took around four weeks in total: about two weeks for the interview stages to be scheduled and completed, and another two weeks before I received the official result. Throughout the process, interviewers were intelligent, collaborative, and supportive. I enjoyed the experience and gained a clear understanding of what the role involves. The challenges were fair and engaging, without feeling overwhelming. I was very happy with the outcome.

      Preguntas de entrevista [1]

      Pregunta 1

      focus on solving algorithmic problems in the style of common online coding platforms, particularly involving data structures and graph-related challenge
      Responder pregunta