None of the questions were particularly out of the ordinary for systems administration work, except for one. And quite honestly, if I spoiled it here, it would ruin its usefulness. If you interview for this team, you'll run into it, and how you answer it is just as important as the technical knowledge you show while answering it.
Apple technical people are sharp and they understand their stuff or the market products very well. One of the interviewers actually asked why my company's (at that time) product is designed in that way. The question is pretty open-ended and I had given it a hard thought and explained in the technical way. At last, I asked back what did he (the interviewer) think and he said that he wasn't sure as well but it seemed my answer technically makes sense.
This was my first interview with an engineering team within IS&T at Apple and felt like the 3 interviewers were overly harsh. Don't be surprised if they say "write a shell script on the board", or ask subnetting questions (e.g. IP address to binary) or get heavy into networking questions for a Systems Admin job. I was surprised, and didn't really find a lot of the questions fair for the job classification. I was not impressed that I was left alone and forgotten.
They test your knowledge on hardware and ask a lot of questions on virtualization technologies like Hyper-V and XenServer.
Describe different virtualization technologies and how to best utilize them.
What do you do if your salesperson mis-speaks
What is your approach to designing a mission-critical system to ensure maximum uptime?
They asked me to describe my thought process for looking at a conference telephone as a system; explain how different levels of requirements would be defined, how the various levels interact, and possible risks associated with the system. They also asked me how I view the difference between verification and validation.
Many questions related to DMARC, DKIM, SharePoint, and Azure.
How to trouble shoot a unreachbal host
Viewing 2611 - 2620 interview questions