Me postulé a través de un reclutador. Acudí a una entrevista en Apple en jun 2017
Entrevista
First, there was a recruiter discussion (screening effort), followed by a call with a peer role. The call was about 40 minutes long, and focused mainly on my experience and a description of the position being applied for (all pretty straight forward). Feedback was tailored towards communication and thinking methodologies. The next call (committed to during the first call) was with the position's direct supervisor, and was structured much differently. It was more conversational, discussing in detail a technical challenge in my experience. The interviewer asked many probing and curiosity based questions, which seemed to be a conversational test of my knowledge and thinking strategy, as well as a performance of my communication skills. This call concluded with an invitation to visit the campus.
Preguntas de entrevista [1]
Pregunta 1
"Tell me about a technical challenge you've encountered, and how you overcame it."
First starts with a recruiter call
Then to a EPM peer, where you have a conversation on background and standard questions as well as a prioritization question.
Then if you pass, then you would move onto a loop with 5 other stakeholders.
Me postulé en línea. Acudí a una entrevista en Apple (Austin, TX) en ene 2026
Entrevista
Behavior based questions and based on background. No technically complex questions. But need to be technically knowledgeable and have the relevant experience in both engineering and program management. Pretty standard questions asked from all interviewers. Recruiter screen, HM call, panel with presentation
Me postulé en línea. Acudí a una entrevista en Apple (Cupertino, CA)
Entrevista
The overall interview process is long. It starts with general recruiter call followed by 2-3 one on one calls with hiring manager and recruiting teams, followed by a technical presentation and a day of panel interviews.
Preguntas de entrevista [1]
Pregunta 1
Behavioral questions (Tell me about a time...)
- You learnt something new technically
- handled conflict
- worked cross functionally
- worked in a tight timeline etc.