Before Founding Konamoxt, my last gig was the Chief Technology Officer for a local Seattle Startup. I have the classic resume for a CTO of a Startup company… if you’re trying to hire a CTO, I’m sure your recruiter has called me… I get those calls all the time. Mr. Startup CEO, I’m here to tell you, you can’t afford to hire a CTO.
[Note to tech managers and wannabe CTOs out there: Oh, don't worry guys my next post will be why you can't afford to not hire a CTO.]
Today, one of the many things I do as an entrepreneur is help advise other Startup companies. I’m on the Board of Advisers of several other startup companies in the Seattle area. One of the common requests I get as an adviser is the help interview and vet potential development leadership candidates.
Inevitably someone on the management team will say “What we need is a CTO! Can you help us make sure this candidate would make a good CTO?”
Whenever I hear this, my alarm bells go off. Do they really need a CTO? What is happening in the organization that causes them to think they need a CTO? And maybe more importantly what do you think you get when you hire a CTO?
Most of the time, a startup CEO (or more likely the Board of Directors) will decide he or she needs a CTO because the organization is feeling pressure about the product. Maybe the schedule has slipped, maybe the product is buggy, maybe they just have this feeling that something isn’t working right. This usually happens in the case where the CEO is not technical themselves. That CEO/Founder was very likely the product visionary, but they don’t know how to build a product, write code, or lead an engineering organization to build the product.
Another very common situation is when outsiders, often the Board, is frustrated with the overall performance of the business, and they begin looking for “problems”. Unless one of the founders has a past track record of being a CTO or VP Engineering in a larger organizations, this lack of experience will often be blamed for the frustration without much analysis at all of the actual facts on the ground.
Sometimes, this “gut reaction” is correct. Sometimes the engineering organization is indeed rudderless, and the right solution is a new technology leader joining the team. But more often then not, I’ve seen the non-technical leadership jump to the conclusion that new “experienced” blood is what’s needed. When in many cases, that move can actually be counter productive.
The common euphemism seems to be “We need some adult supervision in here!”
But if you’re looking to hire a CTO, you probably already have your engineering team in place, you may already have a team of engineers that are building and have built something. How have they gotten as far as they have without this “technical leadership” you’re so convinced is missing? Nine times out of ten, the CEO has become convinced that the existing team is just lacking that leadership.
That search inevitably begins like this… “Let’s find someone with years of experience. And since this company is gonna be huge, we need someone who’s managed big teams, someone who can take us all the way to going public! We’re going to be a $100m/year business with hundreds of developers in different divisions. We need the kind of leader who’s been there and done that.” Sounds like a job for a CTO, right?
Hiring that CTO, will be the biggest mistake you make. You’ll alienate your engineering team, you’ll waste your money, you won’t be satisfied with the results, and in all likelihood that CTO won’t last in your organization anyway.
Here’s the problem… 99% of the time “that guy” you think matches your wish list, hasn’t written code in years. He might have managed a 1,000 developer organization, but he hasn’t directly managed engineers in years. She looks great on paper, managed a 10,000 cpu data center processing billions of transactions a day… but she hasn’t ever done anything with cloud computing.
When ever I’m confronted with this dilemma as an adviser I’m reminded of a great quote I once heard about NASCAR, I believe it was the late great Dale Earnhardt that said…
“If you see a wreck in front of you, drive toward it, because by the time you get there, it won’t be there!”
This philosophy can apply to a lot of things about startups. The key to applying this quote is to recognize that things are always changing… and if you continue to move forward, then in the future you’re guaranteed to be someplace other than where you are right now. What looks like a disaster in front of you if you stay on course, may in fact be the best, safest, fastest, game winning decision by the time you actually get there.
How does this apply to searching for a CTO? Well, it may be the case that you already have your CTO on your team. You don’t recoginze them yet, because they haven’t yet managed that 100 person development team. That doesn’t mean they won’t be ready when the time comes. You probably only have 3 to 6 developers right now. And even though you don’t think you have a development manager, doesn’t mean that team doesn’t have a leader.
Sure, it’s possible your team has gotten as far as they have with no leadership… maybe as the CEO you’ve been guiding that product vision and you’ve been managing those developers. But unless you speak their language, because you’ve sat in their chair before… then I’d be willing to bet you that one of your developers is actually leading the team while you’re not there. Maybe it’s the most senior developer, or maybe its just the most passionate and sharpest developer.
Instead of hiring an outside CTO, you probably need to take a close look at your team and try to determine if you already have a CTO working for you… but under a different title.
Next post… Why Your Startup Can’t Afford To NOT Hire a CTO