1–10 of 16 posts
This would IMO be a better gauge of technical quality over white-board interviews.
This might suffice to see if the candidate is able to write decent code, but what about their ability to communicate their ideas with other developers, their approach to tech in general, or how they'd mesh with the team on a technical level?
What if a friend of the candidate is the actual person who contributed the code patch? You can't be too careful these days.
People game the system because a system exists to be gamed.
Most people have zero professional training on how to do them properly. So don't.
Using the technical interview approach, Einstein wouldn't get a job as a physicist because he had trouble doing simple math problems. That's not Einstein's fault. That's your fault.
Use methods of interviewing that are time-honored and aren't cargo cult. Conversational interviewing comes to mind.
Whiteboard interviews are as useless as baptizing a rattlesnake... but that doesn't mean contributed code is relevant indicator of future performance. It might be ... but as always "it just depends"
Says someone who clearly doesn't have to worry about the threat of demonic rattlesnakes.
You should waive technical interviews, full stop. Most people have zero professional training on how to do them properly. So don't. Using the technical interview approach, Einstein wouldn't get a job as a physicist because he had trouble doing simple math problems. That's not Einstein's fault. That's your fault. Use methods of interviewing that are time-honored and aren't cargo cult. Conversational interviewing comes…
Most people have zero professional training on how to do them properly. So don't.
/s
This might suffice to see if the candidate is able to write decent code, but what about their ability to communicate their ideas with other developers, their approach to tech in general, or how they'd mesh with the team on a technical level?
Those aren't part of the technical interview, possibly except for the "approach to tech" item depending on context.
How could a developer get a 'hire' or 'strong hire' rating without communicating their ideas clearly to the interviewer?