Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      Apple

      Azienda coinvolta

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Apple | Offerte di lavoro di Apple | Stipendi di Apple | Benefit di Apple
      Colloqui di AppleColloqui per Software Engineer presso AppleColloquio di Apple


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Software Engineer

      21 ott 2024
      Candidato anonimo a colloquio
      Washington, DC
      Nessuna offerta
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Apple (Washington, DC) nel mese di ott 2024

      Colloquio

      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

      Domande di colloquio [1]

      Domanda 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.
      Rispondi alla domanda
      11

      Altre recensioni di colloqui per Software Engineer presso Apple

      Colloquio per Software Engineer

      9 gen 2015
      Dipendente anonimo
      Offerta accettata
      Colloquio difficile

      Candidatura

      Ho sostenuto un colloquio presso Apple

      Colloquio

      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

      Colloquio per Software Engineer

      3 giu 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza neutra
      Colloquio difficile

      Candidatura

      Ho sostenuto un colloquio presso Apple

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 1

      LC Mediums and mentorship based behavioral questions.
      Rispondi alla domanda

      Colloquio per Software Engineer

      19 mag 2026
      Candidato anonimo a colloquio
      Seattle, WA
      Offerta rifiutata
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho sostenuto un colloquio presso Apple (Seattle, WA)

      Colloquio

      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