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

      Apple

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Apple | Empleos en Apple | Sueldos en Apple | Prestaciones en Apple
      Entrevistas en AppleEntrevistas para el cargo de Software Engineer en AppleEntrevista en Apple


      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

      21 de oct de 2024
      Candidato de entrevista anónimo
      Washington, DC
      Sin ofertas
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Me postulé en línea. El proceso tomó 4 semanas. Acudí a una entrevista en Apple (Washington, DC) en oct 2024

      Entrevista

      Applied on- Sept 19th Got mail for screening Call - Sept 25th Screening Call - Sept 30th Before this call, the recruiter asked on mail questions regarding relocation, visa and projects. During the call, he told me more about the role, team and the entire interview process. He then told me that the scheduling team will reach out to schedule a 30-min call with the hiring manager. Call with Hiring Manager- Oct 2nd The hiring manager was very kind and friendly. He first introduced himself and then asked me the following questions. Instead of interview, it was an open discussion and he also shared some of his stories: Tell me about a project you’re most proud of. How did you choose that topic? How did you decide the user requirements? What was the biggest challenge you faced while working on this project? What resources did you use when you were stuck? Stackoverflow. How did you decide if the user requirements were right? Tell me about a time when you regretted something you did? What would you do differently if you could go back in time? Imagine you are working with a new team. How would you catch up with speed? Imagine you’re given a new feature to work with, imagine you have no idea at all or have multiple ideas to implement it. What would you do? How will you present your problem to the rest of the team? Tell me about a time when you had a difference of opinion with a team member and how you resolved it. By the end of the interview, he took time to answer all my questions. It was overall a very good experience. Oct 7th - Got an email from the recruiter saying I was selected for the next round. Oct 17th - Coding Round After a week of preparation, the day was finally here. The interviewer was kind and helpful. The interview was on Coderpad. She mentioned that she will ask one coding que, and if time permits she will move on to another. She then pasted the ques: Given two integer arrays nums1 and nums2, return an array of their intersection. I took time and read the que and walked through the example to make sure I’m understanding it correctly. I then asked her a few questions like is the array sorted, she said let’s assume it’s not. Then we discussed an approach. Then she said how can you optimize this. And then she asked what if both the array has repeated elements and you also want to return the repeating numbers as well. Then she asked what if one array is small and one is extremely large, How will you handle that? Then she asked what if instead of two arrays, you’re given N arrays. How would you solve that? I was just refining my approach after each question. I would say it was an open end discussion rather than an interview. Then, in the last 10 mins she asked me to code the approach I mentioned. I coded it along with explaining each line of the code. After the code was complete, she asked me to run it. There were few issues with running the solution as we were short on time. So, she had to end the interview leaving some time for me to ask questions. Overall, the interview went very well, and it was an open-end discussion which I liked very much. I really am grateful for this experience. I got an email a day after saying that I wasn’t selected. I am disappointed but still I’m grateful for this learning experience

      Preguntas de entrevista [1]

      Pregunta 1

      Tell me about a project you’re most proud of. How did you choose that topic? How did you decide the user requirements? What was the biggest challenge you faced while working on this project? What resources did you use when you were stuck? Stackoverflow. How did you decide if the user requirements were right? Tell me about a time when you regretted something you did? What would you do differently if you could go back in time? Imagine you are working with a new team. How would you catch up with speed? Imagine you’re given a new feature to work with, imagine you have no idea at all or have multiple ideas to implement it. What would you do? How will you present your problem to the rest of the team? Tell me about a time when you had a difference of opinion with a team member and how you resolved it.
      Responder pregunta
      11

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

      Entrevista para Software Engineer

      9 de ene de 2015
      Empleado anónimo
      Oferta aceptada
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Apple

      Entrevista

      Around 2 months after I submitted my resume for Apple software engineer position, I got a call from the hiring manager. He asked me what was the good day for the interview. It took half day for meeting 5 people. It was long hour interview for me. Each interviewer spent ~ 30 minutes and asked ~ 4 questions. Each interviewer asked questions in the different areas.
      2583

      Entrevista para Software Engineer

      3 de jun de 2026
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia neutra
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Apple

      Entrevista

      6 rounds. 1 Technical Screening. Then onsite loop consisted of 4 rounds of behavioral, 2 technicals, and 1 sys design. Had an additional Hiring Manager round since I was borderline.

      Preguntas de entrevista [1]

      Pregunta 1

      LC Mediums and mentorship based behavioral questions.
      Responder pregunta

      Entrevista para Software Engineer

      19 de may de 2026
      Candidato de entrevista anónimo
      Seattle, WA
      Oferta rechazada
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Apple (Seattle, WA)

      Entrevista

      6 rounds. Started with phone screen with HM about past projects. Onsite rounds 1: OOD 2. Multi threading 3. Java design pattern and Immutable classes 4. HM All the rounds were heavily focused on Java