3 ms·
Where did I advocate not asking technical questions? In the ideal situation, you've already looked at my code, and know the work I've done from the recommendati
by __mharrison__ 16y ago
Where did I advocate not asking technical questions? In the ideal situation, you've already looked at my code, and know the work I've done from the recommendation. (Note I said "highly recommended").
WRT convincing. Sure you start off in buy, since you're hiring. But you should be open to the thought that a great candidate probably has other great options on the table, and they need to vet those out. Ideally you would provide them that opportunity.
- iam 16y agoRight, as you said the technical question is unnecessary if they've already looked at the code. Which would be pretty hard unless the candidate kept his/her code up somewhere (linked from the resume) or had former coworkers essentially vouch for his/her code quality. And even if the candidate does have the code up, not all interviewers would bother spending the time to look at it. At the end of the day I think it is based off some kind of reputation on whether or not people believe in the technical chops enough to skip asking the candidate the question. And it's really hard to draw the line between belief and sloppy interviewing where they simply forget to ask. I wonder, in your cases where you experienced the ideal interview, which factors do you think contributed to it?