J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Apple (Cupertino, CA) en janv. 2017
Entretien
I've been dragged through this process a few times. In two cases I got a lot of enthusiasm from the recruiter and promised interviews with specific hiring managers. Then... nothing. No updates, no replies to my emails. In another instance I was brought in to interview and offered a job the next day. I had a job so I said I would put in my 2 weeks notice when I got the official offer. Then I waited, and waited,the recruiter kept shrugging at what was taking so long. Two weeks later the offer was rescinded to move the req to a different department. The recruiter assured me that they would follow up with the manager to let them know I was already chosen for the role. Then silence. I never got replies to my emails and just had to assume the process had stopped. They've jerked me around so many times I can't believe they hire anyone.
J'ai passé un entretien chez Apple (San Francisco, CA)
Entretien
The process involved multiple online interviews across six to eight rounds, stretching over several months, making it an unusually long and prolonged hiring experience with significant waiting periods between stages.
J'ai passé un entretien chez Apple (Los Angeles, CA)
Entretien
The interview process at Apple typically starts with a recruiter screening, followed by multiple rounds of interviews—including portfolio reviews, technical and design challenges, and behavioral/cultural fit discussions with team members and hiring managers. It’s known for being rigorous, collaborative, and focused on both creative problem-solving and alignment with Apple’s design principles and values.
Questions d'entretien [1]
Question 1
Walk us through your portfolio. What’s the story behind [specific project]?
Tell us about a time you collaborated with a cross-functional team. What was your role?
J'ai passé un entretien chez Apple (Bangalore Rural)
Entretien
Your past projects
• Your problem-solving style
• How you handle ambiguity and ownership
• For technical roles: basic technical questions or a light coding/system discussion.
• For non-tech roles: scenario or behaviour-based questions.