| > Google, McKinsey, and other companies have responded by reintroducing in-person interviews for some candidates, a meaningful step backward in efficiency (due to travel time and costs) that signals how seriously they are treating this problem. Maybe the relentless pursuit of "efficiency" at all costs has broken the world? I remember when I applied for my first job. I got dressed up and my mom drove me to the interview because I didn't have a driver's license or car at the time. It wasn't "efficient" for me and I suppose it wasn't "efficient" for the company but much to my surprise, I got an offer and that was my first "tech job"...before tech jobs were cool. It's very strange that the authors talk about how "making a bad hire is terribly expensive" but then call out "travel time and costs". Well, if B < A for each role filled, is it really so bad? And yeah, I get that huge companies like Google and Facebook hire from around the world and not everyone is located in close proximity to Mountain View and Palo Alto, but that speaks more to the oligopolistic world we're living in than anything else. If a small number of companies weren't distorting the labor markets, this might matter less. |
The cost of a bad hire they're referring to includes things like opportunity cost of not having a good hire in that position, damage they've done to the product (codebase, design, etc.), and second-order effects like demoralizing the rest of the team.
The actual hiring costs of a bad hire are a rounding error compared to the damage they can do.
Have you ever been on a team that was great until they hired one wrong person who made every work week a miserable slog? Attrition goes up as the good employees start to leave. The codebase starts accumulating a lot of tech debt. Even after they're gone it can take a long time to recover.
This is why it's so important to be able to fire fast, but that's another topic rife with difficulties.