Taro Logo

Build Engineer Interview Experience - Cupertino, California

January 1, 2016
Positive ExperienceGot Offer

Process

Step 1: Apply online.

Step 2: Call from recruiter.

Step 3: Call with hiring manager (regular stuff about resume and my interest in this position).

Step 4: Two back-to-back 45-minute calls with engineers at Apple.

  • Call 1 was SSHing into one of their remote Linux machines and testing my Linux usability. Different commands, kill process, create symlinks, check CPU usage, and other normal UNIX administration stuff.
  • Call 2 was a check of OS knowledge, compiler concepts (high-level), and UNIX file system details.

Step 5: Seven back-to-back onsite interviews, 1-2 people each.

Step 6: Call with the VP.

Step 7: Offer.

Questions

Tell me how the compiler works.

Tell me what happens when you open the computer (in detail).

Turn a recursive algorithm into a DP solution.

How would you implement chmod?

What happens when you do chmod 000 chmod?

UNIX Administration commands.

Behavioral questions.

Was this helpful?

Interview Statistics

The following metrics were computed from 2 interview experiences for the Apple Build Engineer role in Cupertino, California.

Success Rate

50%
Pass Rate

Apple's interview process for their Build Engineer roles in Cupertino, California is fairly selective, failing a large portion of engineers who go through it.

Experience Rating

Positive100%
Neutral0%
Negative0%

Candidates reported having very good feelings for Apple's Build Engineer interview process in Cupertino, California.

Apple Work Experiences