4 ms·
15 extra hours * N candidates per opening * M people onboarded per additional marginal employee discovered. Picking numbers from a hat say 15 * 7 * 20 = 2,100
by Retric 5y ago
15 extra hours * N candidates per opening * M people onboarded per additional marginal employee discovered.
Picking numbers from a hat say 15 * 7 * 20 = 2,100 unproductive hours to avoid a subpar employee that still actually gets something done in the ~3,000 hours before being fired. That could easily be a net loss depending on how much onboarding time is needed and how unproductive they are on average.
Honestly, I think those numbers may be overly generous to long onboarding processes.
- sgtnoodle 5y agoshrug hiring the wrong person into an engineering role is incredibly expensive and painful for organizations with a long term outlook. It cancels out the productivity of at least one good engineer, and stresses out at least 3 people. I've been a hiring manager before, and hiring good people is a huge time investment. The reality is that something like 99% of applicants aren't qualified, and the majority seemingly lack enough self-awareness to know it. The really good people also tend to be bad at marketing themselves. I don't think of interviews as a waste of time, though, even when it's a no-hire.
- mr_toad 5y ago> 2,100 unproductive hours to avoid a subpar employee You also need to factor in the odds of this whole process working. There’s not a whole lot of empirical research that measures the correlation between the interview process and employee performance. And of course, employee performance measurement is as dubiously effective as ever.
- nostrebored 5y agoThere is a lot of empirical research, but it’s internal to companies. I know multiple FAANG companies that track this data.
- shagie 5y agoI am still fixing up the code of a developer from five years ago who was there for two years prior to me. He had ideas about how things should work and completely disagreed with the conventions of every framework. And so, every time I go in a section of code to fix a bug or adjust a feature and I see his name in git blame... I spend another few hours to make sure that I'm not breaking some of the twisted framework code that he had and possibly fix it up a bit and adding a unit test for the functionality before I touch anything to assure myself that I know what it is doing. An unproductive poor employee is bad... a productive bad employee is where the real problems are for years and years to follow.
- Retric 5y agoThe question is how likely a longer interview process with avoid such employees not that they have a cost. In your case code reviews could have caught the issue early before it became such a problem. Though obviously they also have a cost.
- sgtnoodle 5y agoI don't think a longer interview process is strictly necessary to avoid hiring unqualified people. Rather, a longer interview process helps to hire more people while maintaining high standards. Individual interview sessions go poorly all the time for silly reasons. If a candidate only had one interview session and botched it, they're probably done. If they had several sessions and botched one but showed excellence in another, they would still have a good chance of getting an offer.