3 ms·
I've found that I get a lot more signal out of asking people to actually solve a problem by writing a program than by asking them about past experience. Hence
by CydeWeys 8y ago
I've found that I get a lot more signal out of asking people to actually solve a problem by writing a program than by asking them about past experience. Hence I spend most of the interview time on the former. It's surprisingly common for people to be able to talk about something in a way that sounds impressive, but then after seeing their actual coding skills you realize they were likely not a star performer on the team and were just summarizing the work that others mostly did (which they understood well enough to talk about but likely not to have done). Like, it's easy enough to learn one really kick-ass rock song on guitar, but it's another thing entirely to have written said song.
- rossdavidh 8y agoI have the opposite experience. I get more out of talking to them about past experience, mostly by asking them what they would do differently if they were approaching the problem today. This way, I know they are familiar with the problem space (they've worked on it), and I get to see how they thought about it and what lessons they learned from it. This also gives an opportunity to talk about how they think about software (discussions of failure or at least what could have been better are much more informative that successfully demonstrating some algorithm).
- Aeolun 8y agoI don’t have that impression at all. If someone is talking about something impressive, a few deeper questions generally poke holes in whatever inflation they are doing. Of course there should be some coding question, but I definitely look at their resume and it’s discussion just as much.