I'm not sure how asking an engineer 95 rapid fire questions spanning six different technical domains without any prior context or preparation is an effective way to assess whether someone is a qualified candidate. Additionally, the vague line of questioning such as "what do you do when a network port goes down" without providing any specific error types or context feels counterproductive. Even senior level engineers don’t walk around memorizing CRC error definitions or the exact port number for iSCSI. They rely on documentation, past experience, and proper troubleshooting methods. Expecting candidates to recite every protocol detail or command from memory doesn’t reflect how engineers actually solve problems in real environments.