J'ai postulé via la recommandation d'un employé. Le processus a pris 4 semaines. J'ai passé un entretien chez Apple (Santa Clara, CA) en avr. 2018
Entretien
First had an initial phone call with the team manager. Talked about general embedded concepts, semaphores, mutexes, Real-time OS experience I had. Pleasant conversation overall, he said to refresh on basic C concepts for the in person interview.
In person was overall a rushed experience. No overview for number of interviewers but first person just dove in and started asking questions. Difficult to understand many of the interviewers. The next interviewer would come in and interrupt the current question then just start the next problem. No sense of any personality fit for the group - basically felt I could have been at home and doing programming while they watched not sure why they had a face to face since they just wanted to look at code..
Questions d'entretien [6]
Question 1
Make a bitmask that takes as input a width and position
J'ai postulé en ligne. J'ai passé un entretien chez Apple (Cupertino, CA) en févr. 2026
Entretien
Technical screening was directly and only coding. Didn't ask intro or anything. Try to explain theory concepts in between coding, they seem to like it. Basic C question, pointer arithmatic, bit manipuation etc,
Questions d'entretien [1]
Question 1
Aligned & Free Malloc, pointer arithmatic, Bit manipulation and Array Question. Overall it was easy, I didn't perform well due to nervousness.
J'ai postulé en ligne. J'ai passé un entretien chez Apple en janv. 2026
Entretien
The role description was pretty vague, listing only desiring a number of years of C++ experience, an embedded systems background, and strong programming/debugging skills. The recruiter moved me onto the first technical screen with the hiring manager. I was told that the main objective of this screen was to assess my coding ability.
During the technical screen, which was friendly and professional to be fair, I was able to pass the coding question and come up with the correct solution. I was also asked technical questions. I knew the answers to some, but others were, imo, extremely niche and domain specific, and my current experience didn't cover those.
I was then ghosted for three weeks. I had to ask for an update from the recruiter, who finally informed me that the team didn't find me to be the right fit. It's clear that the recruiter and hiring manager don't actually agree on what they want. The process ended up feeling like a huge waste of time.
Questions d'entretien [1]
Question 1
Live coding question: move raw data stored in packed 12-bit integers and 64-byte rows, with padding, into an NxM matrix of 16-bit integers.
code interview
using C++ and solving 2 problems
and explain about the fundamental knowledge about electrical engineering
code interview
using C++ and solving 2 problems
and explain about the fundamental knowledge about electrical engineering
Questions d'entretien [1]
Question 1
code interview
using C++ and solving 2 problems
and explain about the fundamental knowledge about electrical engineering