3 ms·
"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,
by 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 agoI'm not proposing this as if it's the magical solution to all interviewing problems. Bad interviewers and bad interviewees will still exist. I'm trying to address a particular problem... if you, as an interviewee, do not like coding on whiteboards, and you're concerned that your skills will be reflected poorly, well... try to solve the problem then. If an interviewer won't let you solve this well-known and acknowledged problem, well, you certainly learned something about the interviewer, too. But if you didn't even try to solve the problem, don't come whining to me (on the internet). That said, I would also recommend just dodging all these other technical problems. Maybe spend 30 seconds trying to get the projector going, but if it goes beyond that, just say "Let's just look at the screen here on my laptop". Unless you've being interviewed by more than 3 people, it can be managed. Come equipped with a full battery. Etc. But this is all manageable stuff... I manage to get this right for trips to the airport, surely one can manage for a job interview.
- robotkilla 11y agoI did that in my last interview. Brought a computer, told them I hate whiteboard tests. They were pretty skeptical from that point on and I didn't get the job. I also bombed the interview for various other reasons that didn't help... but busting out my own computer got a lot of dirty looks.
- gknoy 11y agoPerhaps there is a way to introduce the idea without inducing such skepticism. Our meeting rooms have a large TV in each, so one could plug in and mirror your display, but you could also likely bring your own projector. (OK, that's probably outside anyone's budget, especially mine.) You might pitch it as something like, "I tend to sketch it roughly at first, and refactor heavily while I'm making an initial solution. Since refactoring is so much easier in a programmer's editor, I'd like to write in vim/emacs/pycharm, and project it on the tv/wall so we can discuss it." ... I'm not sure how that would work if they didn't already have conference rooms wired with monitors, though. If your solution would fit in a screen without scrolling, it probably would work similarly well as a whiteboard.
- falcolas 11y agoWhat would you recommend to someone who don't own a laptop capable of acting as a development machine? Or what if you're allowed to use your laptop, but aren't allowed network access to reference Google, SO, or even documentation?
- jerf 11y ago"What would you recommend to someone who don't own a laptop capable of acting as a development machine?" Twenty year ago, this was an important question. Today it's much less important, because machines are very cheap, relative to developer salaries. If you can't, well, it's the whiteboard for you then. "Or what if you're allowed to use your laptop, but aren't allowed network access to reference Google, SO, or even documentation?" This would fall under "if this concerns you, fix it then". Granted you can't get arbitrary SO searches, but almost everything has offline/local docs. I prefer them anyhow; the web's latency has not gotten better anywhere near as fast as it should be.
- dragonwriter 11y ago> What would you recommend to someone who don't own a laptop capable of acting as a development machine? If you want to be a developer, buy one. While building very large projects on low-end devices is still problematic, almost any laptop today can be used for basic development tasks.
- ericlippert 11y agoThe problems I ask are not amenable to solution by searching Google, and frankly, I am not actually interested in the solution. The problems I give are so easy that someone who cannot solve them by writing the code from top to bottom in one go is unlikely to be successful. The problem is a starting point for a larger conversation about modern software development. For example, I used to give a question where the solution was literally: take two pairs of numbers, find their differences, add the differences together. (The problem involves computing the difference between two times represented in an unusual format.) A candidate who is unable to take the differences of two pairs of numbers and add them together is going to be unsuccessful -- and I have had candidates show up in my office claiming to be "9 out of 10" C++ programmers who could not write correct code that added and subtracted four numbers. The vast majority of programmers will solve the problem correctly, and that is step one; I want to know how are you going to test it, can you prove that it is correct, if the times were in different time zones how would you change the signature of the method, should the method return an error for invalid inputs... I want to know if the candidate can actually reason about code.