Taro Logo

Software Engineer Interview Experience - Cupertino, California

January 17, 2014
Negative ExperienceNo Offer

Process

I had to write many hours of code just for the phone interview.

I went to the onsite and spoke with about five to six individuals, mostly managers. The questions required lengthy whiteboard coding.

To be fair, I did not get the answer to one of these in a timely manner, and this is likely why I did not receive an offer. I did formulate an answer while waiting for my plane later and forwarded it to the manager.

The general feel I got was that I was not a potentially valued asset, but a new cog for their machine. There was a pervasive lack of respect in most of the interviewers' demeanor. I think it's an Apple culture thing, based on other posts I've read on Glassdoor.

As soon as I left the building, I knew I could not work there. On the upside, it indicates extreme confidence in the company's ability to attract talent if they can speak to applicants this way.

Questions

Writing 8-9 hours of code for the phone interview assignment was a bit much. It probably took longer because I wanted to polish it, but it was not a simple problem by any means. I worked all night to have it ready.

The onsite interviewers didn't seem particularly impressed with these efforts, and it gave me insight into how I'd be treated full-time.

Was this helpful?

Interview Statistics

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

Success Rate

22%
Pass Rate

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

Experience Rating

Positive57%
Neutral23%
Negative20%

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

Apple Work Experiences