I applied online. I interviewed at Apple (Cupertino, CA) in Mar 2019
Interview
I was contacted by a recruiter, pre-screened etc. After a couple of weeks the recruiter called and set up a phone interview with an Apple manager for the next day. A few minutes after the scheduled time I received a call from an Apple employee, not the manager. He asked me to describe my experience. I began describing my first job since some of the skills I acquired were relevant to the job at Apple. I was interrupted after 10 Sec. He asked if I knew how to program in C. I said yes, I have been writing firmware in C for several years. Then I started describing a firmware project I developed in C. After about 10 Sec. he interrupted me again, asking if I knew C++. I answered yes and that I also knew C#, and Python. I tried to continue with the description of the work I have done that is related to this job but was interrupted again, almost as soon as I began. This time he wanted to know if I knew Matlab. Neither Matlab nor C++ were mentioned in the job description. That concluded the first part of the interview. He asked me some basic questions about RTOS and version control programs. "What is a semaphore?" "What is a mutex?". Then the interview shifted to a website I could edit. There were several tricky puzzle book type problems. These do not test a person's ability to design or debug software. If someone had to solve them he/she would just write a short program or evaluate it with a script. But none were real world problems. And I doubt the interviewer would be able to solve them without himself. After that the interview ended. The interviewer was impersonal and didn't ask if I had any questions.
I applied online. I interviewed at Apple (Cupertino, CA) in Feb 2026
Interview
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,
Interview questions [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.
I applied online. I interviewed at Apple in Jan 2026
Interview
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.
Interview questions [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
Interview questions [1]
Question 1
code interview
using C++ and solving 2 problems
and explain about the fundamental knowledge about electrical engineering