3 ms·
It sounds like you're working in some specific (and enviable) circumstance where people can get productive right away, and where job success is fully defined by
by evrydayhustling 8y ago
It sounds like you're working in some specific (and enviable) circumstance where people can get productive right away, and where job success is fully defined by meeting your expectations. False positives get more expensive when there is training or provisioning effort required to get someone onboarded, or when you expect your teams to satisfy multiple stakeholders or to grow beyond initial job requirements.
- malvosenior 8y agoWhen you start working with someone day to day you can very quickly find out if they are good or not. You don't have to fully get them up to speed and have them learn all of the domain knowledge of your company. Start small and evaluate quickly. Certainly you can learn more when they start working than you can in the interview process. > when you expect your teams to satisfy multiple stakeholders or to grow beyond initial job requirements This honestly sounds like bad management.
- evrydayhustling 8y agoWat? Bad management to consider how your devs will interact with other roles (PMs, customer support, other dev teams)? I can't figure out if your devs just don't do that, or if you think you can speak for everyone's standards after one conversation with a candidate.
- malvosenior 8y agoThose people should of course be part of the interview process if the developer will be interacting with them. I don't see how that makes a bad hire any more expensive though. Maybe I'm misunderstanding what you're trying to say.
- evrydayhustling 8y agoNah, looks like I misunderstood your "hire based on conversation alone". I thought you meant conversation with just you. My bad.