6 ms·
So why are you having candidates use a whiteboard? I don't understand why this approach is so popular for interviewing. If you want to give the candidate a pra
by mikeash 11y ago
So why are you having candidates use a whiteboard?
I don't understand why this approach is so popular for interviewing. If you want to give the candidate a practical programming test (and why not? seems wise to me) why not have him actually write some code on an actual computer, in a normal programming environment?
Personally, I have no problem with whiteboard programming. I think it's fun and it doesn't stress me. But I don't understand why we do it instead of letting people use an actual freakin' keyboard.
Imagine if you were interviewing a car mechanic and you said, OK, on this whiteboard here, draw out how you would change an oil filter. You'd have to be completely mad! If you want to test his ability to change an oil filter (and why not? that's something they should be able to do) then get a car and say, show me.
I can't see any advantage to the whiteboard, so why do we do it? The only thing I can see is that it would have saved on capital costs back in the ancient days of yore when computer hardware was expensive and quantities were limited and getting every candidate in front of a computer wasn't practical. Thankfully that's not remotely true now.
- robotkilla 11y agoHe gives a bunch of reasons for what he's actually looking for (the way you problem solve etc) which is the first time I've heard an interviewer give a reason for the whiteboard test. Ultimately the author is after the candidates thinking process and he misguidedly (in my opinion) thinks a whiteboard test will help him get that information. But instead, it will help him find people who are good at whiteboard coding under pressure. People who have practiced for that particular activity which they will not be getting paid to perform on a daily basis... just like asking brain teasers help you find people to hire that are really good at solving brain teasers (but may suck at their actual day to day job). Edit I'm going to use this opportunity to point out that I have been freelancing as a python / node.js / php / front-end (js, html, less etc) for about 4 years full time, 12 years total. I worked for a number of companies (small and large) for around 7 years. I get almost all of my current work through word of mouth and reputation. The interview process is pretty much me telling them what I can do, telling them what I have done, who I know and that's it I'm hired within the same phone call and I make a hell of a lot more money solo than I did when I worked fulltime (I'm getting ready to scale back to 20 hours per week to work on a project of my own). Yet, when I attempt a whiteboard test, a brainteaser or just about any other interview question for a full time position, unless I'm able to get past my crushing depression, social anxiety, interview anxiety etc. I will fail spectacularly. The entire standard interview process (and tech job for that matter) is total bullshit.
- mikeash 11y agoHe gives reasons for a coding test, but he gives no reasons for preferring a whiteboard over a computer. The idea of using a computer barely gets mentioned and is never really compared, except for a brief bit where he says of course I won't ding you for forgetting a semicolon or whatever. I really don't see any justification for his use of a whiteboard. He just says it's normal, and that he does it too.
- robotkilla 11y agoAh thanks - i actually skimmed pretty fast through the article because I'm busy and thought his reasons were for whiteboard testing. I still think on site code tests are garbage too... and working in offices when we can easily work from our homes. I like how most of build all this great technology to connect ourselves through the internet and then think its somehow more productive to work in an office setting.
- lkrubner 11y ago>social anxiety, interview anxiety I deal with that too, a circumstance I tried to communicate in my blog post "Embarrassing code I wrote under stress at a job interview". http://www.smashcompany.com/technology/embarrassing-code-i-wrote-under-stress-at-a-job-interview http://www.smashcompany.com/technology/embarrassing-code-i-w...
- wil421 11y agoI suffer from the same problem. Interviews are probably the most stressful experiences of my adult life (similar to going in front of a Judge). Compared to most I am a decent enough programmer but when faced with a whiteboard problem or quick interview coding problem I just clam up and under perform. My normal thought process is thrown out the door when I interview. Most people who know me would never guess I had social anxiety problems. Put me in a room with people I dont know and I am completely different. Add the stresses of an interview and I underperform every time. I hope one day I will have an employer ask me to a quick project related to web dev. Chances are I will shine brighter than figuring out a prisoner's dilemma or some random programming question the interviewer felt was important at the time.
- mtviewdave 11y ago>The only thing I can see is that it would have saved on capital costs back in the ancient days of yore when computer hardware was expensive and quantities were limited and getting every candidate in front of a computer wasn't practical. This is part of it, but also, before about 10-15 years ago, the standard workplace computer was a large tower with a large and heavy tube monitor. Moving a setup like that into and out of a conference room for an interview is cumbersome. But leaving it in a conference room all the time means that a big chunk of the conference room table is continuously occupied by an unused computer.
- jerf 11y ago"If you want to give the candidate a practical programming test (and why not? seems wise to me) why not have him actually write some code on an actual computer, in a normal programming environment?" I've been arguing for years that if you don't want to code on a whiteboard in an interview, bring your own computer. To every justification as to why that's a bad idea on the interviewee side, my answer is to fix that before you walk in the door, and to every rationalization about why this is a bad idea for the interviewer, I say they're all pretty easy to fix. (You can tell how well someone thinks on a whiteboard, but if you see them use Intellisense you're suddenly clueless about how they operate? Then ask better or more questions.) After years of being essentially shouted down, I metaphorically throw up my hands at all of you and say, fine. Insist on programming on the whiteboard in an interview. But stop whining about it. The power to fix this is in your hands and for some reason you all refuse to take it.
- mikeash 11y agoI'd try that if I cared. (Like I said, I personally enjoy the whiteboard, but I understand that others don't.) However, would it really help? I imagine most interviewers would just say, no, put your computer away and grab this marker. It's ultimately the interviewer's choice how to run the interview. We can try to nudge it and we can walk away, but it's ultimately up to them.
- waterlesscloud 11y agoThat's cool. But the interviewer thereby forfeits the right to complain about not being able to find good candidates.
- genericuser 11y agoAnd how they run the interview may influence whether people accept an offer should they make one. While the power is definitely heavily weighted in the interviewer's favor, it is important for them to remember they are trying to find someone they want to work with, and who will want to work with them.
- jerf 11y ago
- vdnkh 11y agoIn the same interview I wrote about in this thread, I also had a computer question. Had an hour to complete it. I knew the answer from the outset, and just had to work out a few details (was working in Mono for the first time). And you know what? It took took me the whole hour. My solution worked great, but it wasn't my best code. I didn't leverage OOP enough and made it too procedural. On a whiteboard this would be fine; logic is really the only grading factor. But on the computer, you don't really have much more time but your answer has to be so much better. And the way it was done for me, I was alone on the computer, not able to give any rationale for my code. And when they reviewed it, they probably ripped it a new one without knowing why I did what I did. I could have easily explained why I made each choice and how to make it better. In the best case, a computer question would be much better. But done sloppily, it's pretty unfair. Reminds me of this Dilbert http://dilbert.com/strip/2013-02-24 http://dilbert.com/strip/2013-02-24
- mikeash 11y agoYou say that the result on a computer has to be so much better. Why? Why not apply the exact same standards as you would for a whiteboard question, but do it on a computer? It's not like typing out pseudocode is some crazy idea.
- vdnkh 11y agoThere's many more grading points to a computer solution. You're not graded for code style on the whiteboard; from what I've gathered, having an algorithm + code to implement is sufficient (not counting the verbal part). On the computer, however, you bet they're going to grade you on style, syntax, leverage of oop. etc. It's not something I realized when I did it which is why it probably (they never actually told me the result) failed. I just did an easy solution- I had good seperation of functions, leveraged access modifiers, etc but I didn't wow them. Right, I can't speak for my interviewers but I was given several whiteboard questions and a computer question. They probably wanted to see what my code was actually like on the computer, while they tested my problem solving skills on the whiteboard. I guess if you chose just the computer as an exam you'd treat it more like a whiteboard.
- VLM 11y ago"I don’t remember that stuff either. I don’t care if you forget semis or make other syntactical gaffes. I’m not looking for people who can spit out syntactically perfect code at the drop of a hat; that’s not the point of the coding exercise at all. I’m trying to find out how you solve problems." I don't really know how I'd do flowcharts and data flow diagrams and data structures and walk thru algos with a keyboard, although on paper or whiteboard its pretty easy. List of questions that need to be answered. Lists of good test to be run in the integrated testing system. Lists of "important points" to be put in to the docs or comments. I mean it can technically be done with ASCII art and comments or maybe a cad program or good ole visio, but I'd rather just scribble some stuff down. The part that trips me out is I haven't done ultra low level stuff since school. In industry nobody writes their own NIH stack or NIH rational number library, that would be completely insane and get you fired so you never think about it anymore. Some of the little brain teasers do look kind of like fun, by "shuffle an array" you mean implementing a physical vegas style card shuffle with cutting the deck and everything, that sounds awesome fun, I'm sure you could do it "the boring, right, way" but implementing a little vegas dealer robot that cuts and shuffles exactly X times sounds like fun. Maybe some times the perfect alternating shuffle isn't. And the cut needs sensible limits to be kinda in the middle third-ish not the extremes. Imagine the unit tests to verify enough random-ness. Here's one thats simple and fun and more interesting than the provided array example for stats. You're allowed private variables BTW. Implement an object that can be streamed any arbitrary quantity of incoming numbers while streaming out the min max and avg at any time so far. Thats a classic where you keep the running subtotal and count in private variables in addition to the obvious min and max. You could use that as the back end to the question in the article, just strip elements off the array one at a time and feed them to the super duper streaming calculator. In "the old days" this algorithm was how cheap scientific calculators did arbitrary statistics without holding all data points and calculating the whole thing ab inito every step.
- genericuser 11y agoWhy not do the parts suited best for paper and a whiteboard on that and the parts suited best for a computer on that. You know give the person both sets of tools and see how they make use of their tools, like they actually will when employed...
- asabjorn 11y agoWhen people started testing programmer candidates on whiteboards people actually did program on paper as part of their normal workflow because computers were expensive: http://programmers.stackexchange.com/questions/51286/how-did-programmers-work-back-when-a-computer-was-very-expensive-rare-as-big-a http://programmers.stackexchange.com/questions/51286/how-did... However, it is strange that the practice is still so widespread long after people stopped programming on paper. In our company we do not test candidates on whiteboards as part of our hiring process since I find it rather ridiculous and do not want to communicate to our candidates that we follow conventions even when they are obviously stupid.
- deleted 11y ago[deleted]
- deleted 11y ago[deleted]
- namelezz 11y ago> I don't understand why this approach is so popular for interviewing. Some skills are probably transferable. Like swimming https://www.youtube.com/watch?v=MnKoQbFXemE https://www.youtube.com/watch?v=MnKoQbFXemE.