> If each portion takes an hour, that's a minimum of 55 hours of Engineering time that's being pulled away from doing their core competency to make 1 hire. Onc

> If each portion takes an hour, that's a minimum of 55 hours of Engineering time that's being pulled away from doing their core competency to make 1 hire. Once you have a new hire on site, there's additional engineering time spent to on board the new hire, depending on: how organised the team & the company is, how simple or complex the work is, how standard or weirdly proprietary the company tech is, how much experience the new hire is working in such a setting. Suppose you can drive down the cost of hiring a new engineer to zero, there are still going to be costs on the order of engineer-weeks or engineer-months to on board them after they join before their net impact to the business is positive. What am I trying to argue? I don't disagree that hiring burns a lot of engineering time, but on boarding also burns a lot of engineering time, so there might not be too much value in hyper optimising one phase the process without looking at the whole system.