It was very, very, very, very good.
It can be sort of stressful.
I had a phone call with a recruiter, followed by two in-person screenings and a full on-site loop. From the first call to the on-site, it took about a month and a half. The on-site consisted of 7 interviews with lots of behavioral questions (someone
I interviewed with Apple for a college position. The technical interview went well; there were no trick questions. One question involved writing C code for string manipulation. The interviewer also asked if I used Mac OS and what I found annoying ab
I was told to schedule an on-site interview after the initial coding task they gave me. It took three attempts to schedule this day of interviews with the recruiter, spread over two weeks. I had to repeatedly free my schedule for the day, only to fi
I had a phone call with a recruiter, followed by two in-person screenings and a full on-site loop. From the first call to the on-site, it took about a month and a half. The on-site consisted of 7 interviews with lots of behavioral questions (someone
I interviewed with Apple for a college position. The technical interview went well; there were no trick questions. One question involved writing C code for string manipulation. The interviewer also asked if I used Mac OS and what I found annoying ab
I was told to schedule an on-site interview after the initial coding task they gave me. It took three attempts to schedule this day of interviews with the recruiter, spread over two weeks. I had to repeatedly free my schedule for the day, only to fi