I've worked at 7-8 startups in the last 12 years, learning along the way that I love the freedom and flexibility that a small company affords. You pay a good price for that freedom though in the form of risk: your job will be measured in terms of months and years, not decades. My parents spent decades at their jobs working for large corporations; that kind of job security does not exist at a startup.
Risk is something that you either purposefully manage or you roll the dice with your life, sometimes literally. I ride/race a motorcycle as my main hobby away from the computer. Riding a moto is a risky activity and I do several things to manage that risk:
- Always wear a helmet, gloves and jacket
- Ride a relatively low power bike
- Taken every MSF training course available
- Refuse to ride in groups
Do these guarantee I won't crash? Certainly not but I hope they will lessen the odds and minimize any damage if I do.
As engineers, what are the risks of working at a startup? The main risk is the company failing and going bankrupt. A second, related risk is being laid off. In both cases, your job and paycheck are at risk. How do we manage those risks? I have three tactics to manage the risk of working at a startup.
1) Make it as easy as possible to find a job
You could make yourself essential to the operation of the company; that helps with layoffs but does not help with bankruptcy and has the drawback that you will start from square one at the next startup. My strategy has been to make myself a valuable developer, independent of any one startup, by working on open source software and maintaining a high quality blog that evangelizes myself and my work. This is a last resort strategy: if anything happens to make my job disappear, ideally I can interview and find another job within days. This recently proved successful when I announced my upcoming move to San Francisco and had 20-30 inquiries over the next few days.
2) Exercise common sense and your math skills
Do you know your startup's monthly burn rate, cash reserves and revenue? I'd bet that the majority of people at startups do not. Get those numbers and figure out how many months the company has before it has no money. Just a few months left? Would it be difficult to raise more money? Are you part of a "layer of fat" that could be laid off to cut the burn rate? Is revenue rising or dropping? Are you getting more customers? These are questions you should be asking yourself every month to evaluate the health of your startup. At some point you will need to leave on your own terms, before you are forced out by bankruptcy or layoffs. I left FiveRuns last year when these questions made bankruptcy look unavoidable. Leaving on my own terms meant I could take a few weeks to interview around to find the right job.
3) Stick with Success
They say failure is the best way to learn but in my experience nothing breeds success more than previous success. I try to stick with entrepreneurs that have past successes. As developers, we want to work with smart developers, yes, but you also want to work with great business guys who have a network of contacts, know how to raise funding and can navigate the company to a successful exit. I can interview a person to learn if they are a good developer but I can't interview a CEO to learn if they are a good CEO. I have only two metrics:
- do they have a reasonable business plan with a way to make money?
- have they had previous startup successes?
The "halo" effect is very real. VCs are more willing to talk to someone who has previous success and knows the funding process. People are more willing to work at a company run by someone with previous success. Press is easier to get and customers are easier to talk to if they already know the company as the latest effort by a successful entrepreneur.
4) Educate yo'self (Extra bonus tip!)
You may know computer science but how much do you know about management or finance? Read a management book. I recommend anything by Peter Drucker -- he literally invented the science of management and his writing really opened my eyes. Read a book on business finance. You're not trying to become an expert in these fields but when you learn a little bit about the other major roles in a startup, you'll be able to evaluate your startup's current situation more accurately.
Even with all this, you will fail often. I've been part of two moderately successful exits and several bankruptcies. I've only been caught flat-footed once and tried to learn as much as I could from that experience. No matter what happens the startup experience is rewarding but with a little foresight you can minimize the inevitable risk to yourself and your livelihood.comments powered by Disqus