Me postulé a través de una facultad o universidad. El proceso tomó 3 meses. Acudí a una entrevista en Apple (Cambridge, East of England, England) en ene 2019
Entrevista
I was told to schedule an on-site interview after the initial coding task that they gave me. It took 3 attempts to schedule this day of interviews with the recruiter, spread over 2 weeks. I had to repeatedly free my schedule for the day and then find out I did that for nothing, because yet another one of the engineers that were going to interview me decided that he is busy that day.
But worry not, the day of my interview did finally come. I was there at 11 and left at 18. At lunch I was rushed into a group that went out to get food, and I had to buy my own lunch (am I entitled to hope for at least my lunch being subsidised when other people get flown across the Atlantic and get accommodation for several days when they have their interviews?).
By interviews waaay overran, I left at a staggering 18:30pm, and happily went home, because at least the people who I had the chance to talk to were nice to me and seemed happy with my responses.
Anyway, I had to wait another 39 days to get my result back, which was a rejection. 39 days.
Preguntas de entrevista [1]
Pregunta 1
I only did whiteboard coding in my 5th interview, which was already at 5 in the afternoon. It was a medium difficulty exercise, nothing to worry about if you interviewed for other big companies before. But I was quite disappointed to see that for a Software Developer position, 4 interviews would solely consist of behavioural questions...
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.
Acudí a una entrevista en 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
Preguntas de entrevista [1]
Pregunta 1
Why driver makes all pages that commands in command buffer will work with present in memory before submission?
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.