3 ms·
i 1000% agree with this. there is no good way to really know whether a candidate is good or not, but their ability to express their thoughts, in code, on a whit
by nunez 9y ago
i 1000% agree with this. there is no good way to really know whether a candidate is good or not, but their ability to express their thoughts, in code, on a whiteboard is a really strong indicator that they can think through a problem and (more importantly) communicate a solution as a software engineer.
the next best approach --- a take home assignment --- is also good at this (or better, IMO, since you're free to implement that solution however you damn well please and it more closely translates into the work they'll actually be doing), but people complain that this is too invasive of their time and that they are doing free work. which is it?
I have to imagine that what most people want is to be asked about their experience, talk through it, and expect that to be enough. which is a very solid first pass filter. it's just not strong enough of a filter to extend an offer with confidence in many situations; it's too easy to bullshit and most of us engineers are damn expensive. (it's not just salary; we want dedicated offices and sit stand desks and super comfy chairs and free food and drinks and games and cadillac health insurance and 401ks and so on and so on)
i also never understood why whiteboarding was hard. if you know how to code and know your language passably well, then why can't you write code on something that isn't a computer?