The first step was a phone screen with the recruiter for the team I applied to, which deals with storage QA. It was a casual conversation about my education and experience, and we talked a bit more about the position and team.
I was then invited to an on-site interview, which lasted a day and a half (one full day plus the morning after). It was a very tiring and thorough interview, composed of multiple one-hour one-on-one sessions. The interview continued even during lunch.
There were many technical and coding questions asked on the whiteboard, as well as a few brain teasers, which I felt didn't add much to the interview. Overall, everyone was extremely nice and offered tips if needed during the technical questions.
I applied knowing I was underqualified and had no experience in storage or QA, and I was not surprised not to receive an offer in the end. I still really enjoyed the experience and the people I talked to; it seems like a great place to work!
62 - 63 = 1. Changing only one element (either digit or operand), make this statement true.
How to find the nth-to-last element in a linked list?
An interviewer gave me a pen and asked, "How would you test this pen?"
On a Unix shell, how to find the list of files with a size greater than X MB.
The following metrics were computed from 1 interview experience for the Apple Software Development Test Engineer role in Cupertino, California.
Apple's interview process for their Software Development Test Engineer roles in Cupertino, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Apple's Software Development Test Engineer interview process in Cupertino, California.