Whiteboard Coding Interviews
Debate on the merits, criticisms, and alternatives to whiteboard coding exercises in software engineering job interviews, highlighting issues like stress, irrelevance to real work, and their value for assessing problem-solving and communication skills.
Activity Over Time
Top Contributors
Keywords
Sample Comments
unless the job requires whiteboard coding, you are not testing for the job.an advice to candidate: when you've been asked to do whiteboard coding - run away. this is a negative signal.
I can empathize with your problem. Was just talking to a friend an hour ago about this.I am wondering whether you have considered companies that don't white board.[1][1]https://github.com/poteto/hiring-without-whiteboards
I don't understand why people are forced to write on whiteboard. Some get very stressed and lose their ability to think, some can't multitask (paint on whiteboard, think and talk to the interviewer at the same time). Just give them the task, give them a computer, give them 30 minutes of privacy and then let them explain the complete, working and tested solution - you get better results as this situation is more like regular coder's daily routine.
So you don't do whiteboarding for interviews, then?
Sorry, you don't see the intention behind asking people to write code on a whiteboard? Being able to lay out ideas, code, and architecture on a whiteboard is a useful skill in and of itself for communicating with coworkers, let alone using it as a way to get insight into how an interviewee codes.
Whiteboard interviews DO work - if done right. Don't ask computer science questions. Instead give the interviewee real world problems to solve. And find out how he/she attacks the problem. What he/she would look at to solve the problem. What tools he/she would use and why. The key thing is to learn how the interviewee thinks through a problem. And how well the interviewee explains his/her thinking. I have interviewed and hired people for 10+ years and can testify
Whiteboard is a medium to showcase your skill. People who can think in terms of pictures and demonstrate their thinking on white board are pretty good problem solvers. Not all companies and job roles need whiteboard coding. Companies have whiteboards and engineers use it to communicate with each other. It is a very effective tool. Interviewing is an art and bad interviewers make the process dehumanizing and boring. Do not hate the whiteboard. Some of the ideas programmers have are pretty complex
Asking people to write code on a whiteboard in the pressure of the interview environment doesn't seem very reflective of how they work day to day to me. Perhaps judging them on previous projects or open source work they have contributed to would be a better approach. If someone gave me a pen and a whiteboard and asked me to draw code I think I would likely say thanks but no thanks and walk out of the interview.
If they give you a whiteboard instead of a computer, writing correct code with minimal editing is part of the interview process. You should direct your hate to the interviewers, not to the tool.
It is a sniff test to determine if you lied on your CV.I personally suck at "whiteboard" coding too. I'd prefer they leave me in an empty room with a text editor and no internet connection for 10 minutes. But part of the exercise is discussing the problem and or showing your interpersonal skills.Hopefully you'll find a different employer who interviews in a way better suited to you.