Me postulé a través de una recomendación de un empleado. El proceso tomó 5 semanas. Acudí a una entrevista en Apple (San Diego, CA) en feb 2023
Entrevista
There were 3 interviews in total. The first one is a screening call with the recruiter. They briefly asked about my interest in the position, what I know about it, and what questions to expect in the interview with the engineer. The second one was with the project lead. It was an hr long. He asked me to talk about myself then based on that he started digging into my past work experience and projects. Then asked a couple of technical questions about the area of firmware and what I know about it. it was very chill and surface level. The last one was 6 hrs long with 6 different engineers, the whole team. Each one took 45 mins. The questions were very technical and involved. They would put you in real scenarios and see how you solve problems and complicate the scenario as you answer. You should be ready for analyzing systems, identifying pain points and troubleshooting, writing some codes, and answering behavioral questions. Some of them were nice and would give feedback as you go, and some were very poker face I would not know if I was doing good or not.
Preguntas de entrevista [1]
Pregunta 1
Identify use cases? Write a code in python? troubleshoot a system? Design a system?
Me postulé en línea. Acudí a una entrevista en Apple (Cupertino, CA) en feb 2026
Entrevista
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,
Preguntas de entrevista [1]
Pregunta 1
Aligned & Free Malloc, pointer arithmatic, Bit manipulation and Array Question. Overall it was easy, I didn't perform well due to nervousness.
Me postulé en línea. Acudí a una entrevista en Apple en ene 2026
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 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
Preguntas de entrevista [1]
Pregunta 1
code interview
using C++ and solving 2 problems
and explain about the fundamental knowledge about electrical engineering