When I did interviews, it had nothing to do with the person. I designed a standard test like for windows admins I would have them dcpromo, setup dns, setup ip a

When I did interviews, it had nothing to do with the person. I designed a standard test like for windows admins I would have them dcpromo, setup dns, setup ip address, install wsus on the alternate port. I only had 5 steps on the sheet. I was even upfront about that they can ask for any help or google it because I want to see their troubleshooting process. The reality is that there's far more steps actually required than that. I want to see if they were going to go through all the details; ask what all the details were, etc. But even more importantly, the entire time I'm talking video games and tv and movies and cars. I'm trying to distract them from actually doing the steps. Even better is that as the steps escalate, the more difficult to steps become until you make it to WSUS and you literally cant install wsus successfully. Ask Microsoft, not me, why wsus is so terrible. The fun thing about this interview process is that it's not trivia bullshit. Like "explain the role of a windows server" or "what is a windows domain" or "How do you backup active directory" this is all ridiculous questions that dont gauge if someone knows anything about anything.