Taro Logo

Engineer Interview Experience

November 1, 2010
Neutral ExperienceNo Offer

Process

I was told to have the interview on campus after a career fair. I had interviews with two people from different teams.

The first person asked me many questions about my previous experiences, like what things I had done in the past. Then he asked me several easy technical questions. An example question is what to consider when doing object-oriented programming. I said loose coupling is important. It went pretty well, but it didn't get into deeper questions.

The second person I met asked me some UI questions. Obviously, he's looking for engineers that are willing to do front-end work and have a good design sense. I showed him some of my designs. Later, he switched gears to lower-level problems relating to the OS. Some of the questions he asked include:

  • "Tell me about the difference between a process and a thread?"
  • "How to prevent deadlocks?"
  • "What's the difference between stack and heap? Which one is faster?"

I was not so prepared for some of the OS questions, so it didn't go so well.

Both interviews went for about half an hour. I appreciate both of them being very patient and nice during the process.

Questions

Tell me which is faster, a stack or a heap? Why?

Was this helpful?

Interview Statistics

The following metrics were computed from 70 interview experiences for the Apple Engineer role.

Success Rate

20%
Pass Rate

Apple's interview process for their Engineer roles is very selective, failing most engineers who go through it.

Experience Rating

Positive47%
Neutral44%
Negative9%

Candidates reported having very good feelings for Apple's Engineer interview process.

Apple Work Experiences