Hiring fast is a common Silicon Valley mistake
I once privately remarked, watching how the CEO of a certain Silicon Valley company carried himself, that it felt like watching someone play a game of Jikkyou Powerful Pro Baseball.
The company had just launched at the time, and this CEO, a pure businessman with no engineering background, had secured his first round of investment on nothing but a vision and a pitch deck. Since he couldn’t build the thing himself, he needed to hire engineering staff. So he scooped up nothing but stars. Everyone had degrees from Stanford, MIT, or Harvard, and every one of them had a career at one of Silicon Valley’s famous companies.
Even so, this in itself was a common sight in Silicon Valley.
What caught my attention was the aggressiveness of the hiring: poaching extremely experienced mass-production staff at high salaries even though the prototype wasn’t working properly yet, or a whole row of QA engineers sitting idle with nothing to evaluate.
They just hired, basically. Still, this too was a common sight.
Back to the question at the start, then. First we need to think carefully about what employment means for both sides.
By “both sides” I mean the employer and the employee.
For the employer, the benefit of employment is “raising commitment.” Someone under an employment contract is unlikely to simply stop showing up tomorrow, or to suddenly demand to terminate the contract midway through a project. Shortened working hours have become more common lately, but you can still require “full commitment” — working full-time as someone’s “main job.”
At an early-stage startup especially, it’s completely normal to be working “day and night.” You can easily imagine how troublesome it would be if someone disappeared on you saying, “My contract is for 80 hours a month.”
For the employee, on the other hand, the main benefit of employment is “security.” In Japan especially, once someone is employed, they can’t easily be let go. There’s a process that has to be followed — pointing out performance issues, setting a period for improvement, and only dismissing the person if nothing improves; or repeatedly warning in writing about negative effects on others. The usual pattern is: give proper evaluation, feedback, and opportunity, impose measures like pay cuts where appropriate, and dismiss only as a last resort.
Outside of that, there may have been pressure from HR or a manager, but on paper it will have been treated as voluntary resignation. And this is an American example, but health insurance in America is eye-wateringly expensive (I know this well, having paid for it individually for a time), and companies commonly enroll employees as a group at a discounted rate and cover the cost. Japan has something similar, but benefits like this are a very important part of security.
So, those are the benefits for both sides. Now for the drawbacks.
For the employer, the drawback of employment is “reduced flexibility in management.” In my experience, employment is the highest-risk issue, and the one that calls for the most caution. First, fixed costs rise. And adjusting those fixed costs becomes very difficult. At an early-stage startup especially, major pivots in business strategy aren’t rare. Someone hired as an iOS engineer suddenly having to build for Android tomorrow because of a change in company direction — that’s still a minor case. Engineers having to do sales, accounting staff temporarily getting pulled into the debugging team, someone who can’t speak a word of English becoming the person in charge of overseas business. It’s chaos.
Even so, if things can somehow be made to work through reassignment, there’s still hope. But sometimes people simply become unnecessary. You can’t keep paying wasted salary, so you have to ask them to leave amicably, and that too comes with communication costs. In America, it’s common to offer a package (additional benefits, or short-term pay without work) to those who voluntarily resign at the company’s request. That too is a painful expense.
For the employee, there really aren’t many drawbacks to employment. At a company that allows side work, there’s no problem having a side project, and in Japan too, job-hopping has become fairly common, so there doesn’t seem to be a major issue there. Some people may feel negatively about simply having their time bound for a fixed period, but in practice I think the benefits gained from that commitment far outweigh the cost.
Bringing the focus back to early-stage startups: this is a period when many things are still uncertain, and to keep flexibility, it’s not a great idea to casually increase hiring. And for the person being hired too, it’s lower risk to keep a foothold elsewhere and get involved on a side basis than to commit full-time to a company that might go under at any moment. In the end, it all comes down to the question of “where do you step on the accelerator.” If you never hire anyone at all, it becomes extremely difficult to convince partners and customers that you can keep running the business stably and continuously (at the very least, they’ll doubt you). Conversely, if you hire too aggressively early on and that sunk cost ends up distorting your management decisions, that defeats the purpose.
In the course of running a business, there should always be a point you recognize as “this is where it counts.” (Incidentally, I’m not fond of the idea that “every year is where it counts.”) The ideal is to build the organization from the start with enough planning that you can ramp up hiring and smoothly strengthen the team at that moment.
The content of this post is part of the original text of the following book. If you’re interested, please get a copy.
The Shape of a Happy IoT Startup
The Shape of a Happy IoT Startup
Originally published in Japanese at https://clazytech.com/2022/09/1198/. Translated with LLM assistance and reviewed before publication.