Ir para o conteúdoIr para a pasta
  • Vagas
  • Empresas
  • Salários
  • Para empresas

      Avance em sua carreira

      Descubra qual pode ser seu salário, conquiste a vaga dos seus sonhos e compartilhe insights de qualidade de vida com sigilo.

      employer cover photo
      employer logo
      employer logo

      Apple

      Empresa engajada

      Sobre
      Avaliações
      Remuneração e benefícios
      Vagas
      Entrevistas
      Entrevistas
      Buscas relacionadas: Avaliações da empresa Apple | Vagas da empresa Apple | Salários da empresa Apple | Benefícios da empresa Apple
      Entrevistas da empresa AppleEntrevistas do cargo de Software Engineer da empresa AppleEntrevista da empresa Apple


      Glassdoor

      • Sobre
      • Prêmios
      • Blog
      • Fale conosco

      Empresas

      • Conta gratuita de empresa
      • Área da empresa
      • Blog para empresas

      Informações

      • Ajuda
      • Regras da Comunidade
      • Termos de Uso
      • Privacidade e opções de anúncios
      • Não venda nem compartilhe minhas informações
      • Ferramenta de consentimento de uso de cookies

      Trabalhe conosco

      • Anunciantes
      • Carreiras
      Baixe o aplicativo:

      • Busque por:
      • Empresas
      • Vagas
      • Localizações

      Copyright © 2008-2026. Glassdoor LLC. “Glassdoor”, “Worklife Pro”, “Bowls” e o logotipo do Glassdoor são marcas comerciais pertencentes à Glassdoor LLC.

      Empresas seguidas

      Fique por dentro de todas as oportunidades e dicas internas seguindo as empresas de seus sonhos.

      Buscas de vagas

      Comece a buscar vagas para receber atualizações e recomendações personalizadas.

      Entrevista para Software Engineer

      21 de out. de 2024
      Candidato(a) sigiloso(a) à entrevista
      Washington, DC
      Nenhuma oferta
      Experiência positiva
      Entrevista difícil

      Candidatura

      Candidatei-me online. O processo levou 4 semanas. Fui entrevistado pela Apple (Washington, DC) em out. de 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

      Perguntas de entrevista [1]

      Pergunta 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 à pergunta
      11

      Outras avaliações de entrevista de vagas de Software Engineer da empresa Apple

      Entrevista para Software Engineer

      9 de jan. de 2015
      Funcionário(a) sigiloso(a)
      Oferta aceita
      Entrevista difícil

      Candidatura

      Fiz uma entrevista na empresa 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

      10 de jun. de 2026
      Funcionário(a) sigiloso(a)
      Londres, Inglaterra
      Oferta aceita
      Experiência positiva
      Entrevista fácil

      Candidatura

      Fiz uma entrevista na empresa Apple (Londres, Inglaterra).

      Entrevista

      The interview was easy, we talked about technical stuff in-depth: os, drivers. If they think you know something, they would ask you till they find where your knowledge ends. So be ready

      Perguntas de entrevista [1]

      Pergunta 1

      Why driver makes all pages that commands in command buffer will work with present in memory before submission?
      Responder à pergunta

      Entrevista para Software Engineer

      3 de jun. de 2026
      Candidato(a) sigiloso(a) à entrevista
      Nenhuma oferta
      Experiência neutra
      Entrevista difícil

      Candidatura

      Fiz uma entrevista na empresa 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.

      Perguntas de entrevista [1]

      Pergunta 1

      LC Mediums and mentorship based behavioral questions.
      Responder à pergunta