3 ms·
Except it's pretty much standard. If there isn't a github link, I'm still going to tailor the programming questions to a context that I infer from the past expe
by eschneider 3y ago
Except it's pretty much standard. If there isn't a github link, I'm still going to tailor the programming questions to a context that I infer from the past experience on their resume (as in, they said they did X, so they should know about Y) but with a bit less accuracy.
Most of the interview is getting the candidate to show me that they know _something_ in depth and I'm not super concerned with exactly what it is. (If they've learned something in depth, I expect they can also learn the details of what we do. :) So the exact same questions to every candidate serves no one's interests.
- blindhippo 3y agoI think the nuance here is if you tailor ALL interviews for a specific job based on each candidate to the point where the interviews are no longer directly comparable, that could constitute a hiring practice that would run afoul of some laws in various places. However, what you're describing sounds reasonable to me - you're offering the same overall interview structure, just tailoring the question to delve more into someone's bespoke experience. That's a hell of a lot more work than a one size fits all (ala leetcoding style) question - kudos to you.