4 ms·

Writing code on whiteboards is hard, writing code on an unfamiliar computer in an unfamiliar room while a stranger watches on is hard, writing code in the middl

Writing code on whiteboards is hard, writing code on an unfamiliar computer in an unfamiliar room while a stranger watches on is hard, writing code in the middle of a job interview is hard (and unrealistic since we never do that during the course of normal work). So maybe you should stop making candidates do it. Give them a coding test they can work on in their own time, or whatever works for your situation.

jasonmp85 11y ago
And how many employees doing these interviews can actually write code on a board? Not to sound too wimpy, but holding your arms up like this is physically taxing for the unpracticed. Unless you're pulling in a lecturer for an interview, it's just not natural for an actual programmer. And why would you want to disadvantage actual programmers when you're hiring one? It just makes no sense. Whiteboards are for argumentation during design discussions. They're great for high-level block diagrams and all that. They're NOT great for long runs of text, and especially bad for code. If you're in-person, pair program. If you're remote, find a good online code-friendy (syntax-highlighting, monospace) scratchpad and use it with a voice or video chat solution. And if you can't schedule time with them, ask them to submit a repository with a solution to a harder problem. If they need to explain why they did something, that's what commit messages and READMEs are for. If they don't understand that, that's a mark against them. It's already enough of a conceit to ask someone to e.g. reverse a linked list when they're practically never going to be doing that in their day job. To ask them to do so using a dry-erase marker writing with 4" lettering on a whiteboard while standing is crossing into the ludicrous.
- lfowles 11y ago
  If there's one thing I'm thankful for, it's my fourth grade teacher telling me to write with my elbow, not my wrist, on the blackboard.
- serve_yay 11y ago
  Well, part of my point is that the whiteboard isn't really the issue, it's just the most egregious aspect of the situation. You say if you're in person, pair program. But where, on what computer, doing what, in what editor, etc? All these things plus the inherent pressure of the situation make the experience unpleasant enough, and the results unreliable enough, that you just shouldn't do it in my opinion.
  - crucini 11y ago
    I take your point, but I have been interviewed with the "pair programming" concept and found it much easier. It also tells the interviewer how you really interact with a computer. I find the whiteboard stressful. I'm tempted to use short variable and function names to save writing. I can't easily insert more lines of code. The code tends to get cramped and illegible. In a text editor I'm more likely to make huge changes as the concept evolves. A significant proportion of good programmers use vi or emacs. I realize there are outliers who just have to have Sublime Text set up the right way.
robotkilla 11y ago
Most places do a coding test, whiteboard test, 5 phone interviews and 1 to 3 in person interviews with various members of various teams. Oh and you get shoved in what is essentially a giant playpen with other socially retarded "adults" in what is called an "open floor plan" and made to feel like shit for a few weeks or months based on your newness status, and made to feel like you're going to get fired always by the people above you, and paid like shit, and told when you get a holiday. Awesome life.

jasonmp85 11y ago

And how many employees doing these interviews can actually write code on a board? Not to sound too wimpy, but holding your arms up like this is physically taxing for the unpracticed. Unless you're pulling in a lecturer for an interview, it's just not natural for an actual programmer. And why would you want to disadvantage actual programmers when you're hiring one? It just makes no sense. Whiteboards are for argumentation during design discussions. They're great for high-level block diagrams and all that. They're NOT great for long runs of text, and especially bad for code. If you're in-person, pair program. If you're remote, find a good online code-friendy (syntax-highlighting, monospace) scratchpad and use it with a voice or video chat solution. And if you can't schedule time with them, ask them to submit a repository with a solution to a harder problem. If they need to explain why they did something, that's what commit messages and READMEs are for. If they don't understand that, that's a mark against them. It's already enough of a conceit to ask someone to e.g. reverse a linked list when they're practically never going to be doing that in their day job. To ask them to do so using a dry-erase marker writing with 4" lettering on a whiteboard while standing is crossing into the ludicrous.

lfowles 11y ago
If there's one thing I'm thankful for, it's my fourth grade teacher telling me to write with my elbow, not my wrist, on the blackboard.
serve_yay 11y ago
Well, part of my point is that the whiteboard isn't really the issue, it's just the most egregious aspect of the situation. You say if you're in person, pair program. But where, on what computer, doing what, in what editor, etc? All these things plus the inherent pressure of the situation make the experience unpleasant enough, and the results unreliable enough, that you just shouldn't do it in my opinion.
- crucini 11y ago
  I take your point, but I have been interviewed with the "pair programming" concept and found it much easier. It also tells the interviewer how you really interact with a computer. I find the whiteboard stressful. I'm tempted to use short variable and function names to save writing. I can't easily insert more lines of code. The code tends to get cramped and illegible. In a text editor I'm more likely to make huge changes as the concept evolves. A significant proportion of good programmers use vi or emacs. I realize there are outliers who just have to have Sublime Text set up the right way.

robotkilla 11y ago

Most places do a coding test, whiteboard test, 5 phone interviews and 1 to 3 in person interviews with various members of various teams. Oh and you get shoved in what is essentially a giant playpen with other socially retarded "adults" in what is called an "open floor plan" and made to feel like shit for a few weeks or months based on your newness status, and made to feel like you're going to get fired always by the people above you, and paid like shit, and told when you get a holiday. Awesome life.