Whiteboard-Pairing | When doing this exercise as the interviewee

Whiteboard-Pairing is a Python library. Whiteboard-Pairing has no bugs, it has no vulnerabilities and it has low support. However Whiteboard-Pairing build file is not available. You can download it from GitHub.

When doing this exercise as the interviewee, you should record yourself answering the interviewers question. This must be uploaded on youtube and the link is one of the components of your development journal. If you prefer, you may make the video private and invite your PM. This will be of great use when working with your career coach!. In order to get you guys more practice whiteboarding, we're going to have you pair up with a partner once a week and have you both swap between being an interviewer and an interviewee. This ensures that each student gets in at least one live whiteboard practice session a week. This is how it's going to work. Everyone will be a assigned a problem. This will be the problem that you will pose to your interviewee when it's your turn to be interviewer. You're being assigned the problem at the beginning because it's very important that you get familiar with your assigned problem. In order to be an effective interviewer, you need to know the problem you're asking inside and out. A working reference solution will be given to you, but you should figure out other ways to solve the problem because everyone thinks about problems differently. What's important here for you as an interviewer is be familiar with multiple approaches to solving your given problem, as well as the tradeoffs between working solutions. Your interviewee may very well come up with a solution to the problem that is very different from the reference solution or your own preferred solution, but that doesn't mean they are wrong. At that point, it will be your job as their interviewer to discuss with them the tradeoffs between their solution and yours. Additionally, the working reference solution you've been provided with will be in JavaScript, but we don't want to limit interviewees to having to whiteboard in JavaScript. Some of them may wish to go with Python (or even C if they're really brave). You should be able to effectively act as their interviewer regardless of the language they choose to implement their solution in. This will give you the chance to discuss problems in multiple languages, or in pseudocode.