Whiteboard interviews are becoming an increasingly popular part of the process when companies look to hire software engineers.

The reason for their growth in popularity is because companies find it assesses desirable traits in an engineer which may not be apparent from a more traditional technical interviewing format.

There are three key areas:

Firstly, an engineer’s capability within architecture and solution design. A technical interview asks how you do something; where a whiteboard interview explores why.

Secondly a candidate’s thought process and how they approach a problem.

Finally, the candidates communication skills, and most importantly how they interact with other people and take on feedback to work through a problem pragmatically. 

Once you know what Whiteboard interviews look to assess, we can better prepare for them, and ultimately progress through that stage of the assessment.

Practice and Prepare:

The key to performing well in a Whiteboard interview is to practice.

Most Whiteboard interviews look at solution design and architecture as the main component, so your answers should relate back to SOLID design principles, good system architecture, suitable design patterns and so forth. They are looking to see you understand modern concepts and best practice. 

Some Whiteboard interviews will ask you to solve a coding challenge. You can prepare for this by practicing coding problems on a whiteboard or a piece of paper at home, and make sure you practice explaining your thought process out loud. This will help you become more comfortable with the format of the interview and allow you to work on your communication skills.

Listen carefully to the interviewer:

During a whiteboard interview, it is crucial to listen carefully to the interviewer's questions and feedback. Make sure you understand the problem statement and any constraints or requirements. Repeating it back to them is a great way to check what you're being asked to do.

If the interviewer provides feedback or asks questions, make sure you address them and incorporate them into your solution. If any part of the instructions are unclear, ask questions until you understand. It is better to ask questions then to start solving the wrong problem.

Communicate effectively:

Communication is a crucial skill in a whiteboard interview. Make sure you explain your thought process clearly and concisely, and use proper terminology when describing your solution. If you are asked to write code, make sure you write it neatly and legibly, and comment on any sections that may be unclear.

Break down the problem:

When faced with a problem in a whiteboard interview, it can be helpful to break it down into smaller parts. This will help you identify the key components of the problem and come up with a more efficient solution. Make sure you explain your thought process as you go, and ask for feedback from the interviewer if necessary.

All systems go?:

If you're doing it online, make sure you have all the links you need and that they work. Also that your computer, camera and microphone all work at least a day before the interview, not 30-seconds before you join the call.

If you're attending an office in person, leave plenty of time so you're not rushing or flustered when you arrive.