During our session you mentioned that you changed the format of the interview. To aid your own A/B testing and to support giving every candidate the same experience, I recommend creating a markdown file for the instructor that includes:

1. The initial class spec the interviewer should give to the candidate

   • class methods
   • instancing example, game.move() example

2. Quick reference FAQs that candidates usually ask at outset of session

   • "How should I handle cheating attempts?"

3. Common early self-sabotage that the interviewer may want to sway candidate away from

   • Not using a 2D array

I can create PR for this if you'd like, but since it's closer to interview methodology than actual code, wanted to float idea first.