3 ms·
I imagine they're complaining about the technical interview. For the record, when I did the technical interview I didn't find it too onerous -- mostly a more ad
by Qub3d 5y ago
I imagine they're complaining about the technical interview. For the record, when I did the technical interview I didn't find it too onerous -- mostly a more advanced sort of FizzBuzz to check you could do some intermediate math and handle basic data structures and logic flow.
My understanding is that at Apple this can vary quite a lot in difficulty or depth depending on what team you're looking at, and who is interviewing you.
- AlotOfReading 5y agoIndeed. My last onsite with apple concluded with a couple hours of grilling on how to write performant synchronization primitives on various real architectures. I was not interviewing for the relevant teams.
- Qub3d 5y agoYikes! I would sort of wonder if it was a test to see if you know scope. But for two hours? I know its Apple but I'd definitely be prepared to walk out. In that situation that gives you the freedom to clarify the job description -- if they say it is in the description, I'd save everyone time and say I don't have that knowledge, thank them for their time, and wish them luck on their next n months of searching for their unicorn. If it isn't, I'd probably go full stick-in-the-mud and explain that I could find the answers to those questions but it would be a waste of everyone's time: I'm an A player and I don't focus on irrelevant things that dilute abilities and ultimately the product (basically throw Steve Jobs at them).
- runnerup 5y agoI have a chemical engineering degree from a "Division 2" university and part of a computer science degree from a fairly low-ranked research university. Your strategy would be an epic failure for me. Granted, nearly any strategy would be.