Time to start looking
29 Oct 2023The layoffs season is upon us or has it been a layoff year? Hard to keep track of. TechCrunch seems to have tried to come up with a comprehensive list but of course this is not even close to a complete list as it doesn’t contain the innumerable startups that sprung up during the covid era and disappeared soon after leaving scores of jobless engineers in their wake. Layoffs can of course be excruciatingly hard irrespective of whether you are a novice engineer or a seasoned veteran. Being laid off can have significant financial impact as well as cause a fair amount of emotional damage and loss of self confidence as having been part of a failed venture.
Of course this instability makes engineers very hesitant to work for startups which is bad for progress in society in general. We all need talented engineers working on new ventures to move the needle on technological progress. I regularly get asked by novice engineers on how to decide to work for a startup and how to hedge against the risks that come with working at a startup. Two cardinal rules that I follow while picking/working for a startup are:
Make sure you really want to work there
One of the main questions facing engineers while picking a startup is: Is this the right place? Engineers get drawn to startups for a myriad of reasons
- Competitive pay: Startups(of course funded ones) tend to pay a lot to hire the best talent
- Equity: If they can’t afford the cash, the main incentive to work at a startup is the equity which comes with the dream of hitting it big. Silicon Valley lore is rich with stories of early employees turned multi-millionaires
- Cutting Edge Tech: Generally startups are trying to solve problems with unique solutions that are only possible with the latest technologies for e.g: LLMs, GenAI etc or they are trying to revamp existing solutions built on old slow Technology. Both of these offer engineers the opportunity to work on the latest and greatest tech which is definitely alluring
Given there are a plethora of startups out there offering talented engineers some combination of the above, how do you go about choosing the right belle to the ball? Having worked for a few startups of varying degree of success, there are a few criteria I stick to while deciding to work for one:
- Mission statement: Make sure you really believe in the company’s mission statement, I mean really believe it. One easy way to tell if you really understand it is try to explain it to a friend and make them understand why the business is useful. This doesn’t necessarily mean the company will be successful and profitable, but you will be committed to the mission and startups with limited headcount need their employees to be completely committed to have any shot at succeeding. Weed away all the fluff about disrupting a billion dollar industry that all of them claim to do and boil it down to a very basic question: What do they do and why are they useful?
- Revenue: Dig into how profitable the company is or how close to profitability they are or if they even have a solid path to profitability. Companies might not be completely honest about this during the interview but you will get a sense of if there is a realistic chance of the business being profitable and if the current employees understand the path to it. Profitability is of course critical to long term employment.
- Overhead: This is the amount of non payroll expenditure the company spends in order to run their business. Higher the overhead, harder it is for a business to scale and become profitable and inability to scale is a death knell for a tech startup. To understand better what overheads are, take a look at Uber’s expense breakdown here. Insurance expenses, credit card processing fees, data center expenses etc. are large overheads for Uber. Of course a company is not going to divulge detailed revenue statements during an interview, but its still illuminating to ask the question: What is your largest non payroll overhead?
- Funding: Funding is a complicated topic. A lot of companies raise multiple rounds (Series A, B, C, D E etc) to be able to grow and expand their business. While this is necessary in a lot of cases, every additional funding round dilutes the value of equity held by an employee. And if the company is sold, the shareholders are paid off first before the employees which often results in the employees getting very little payout in the end. Of course a lot of companies go an alternate route of funding which can be a boon for employees:
- IPO: Working for a publicly traded company is one of the best possible solutions for an employee of a startup. Usually this means the company is valued more than when you joined it and so now your equity is worth more. Not only that, now you have a public platform to sell the equity and profit. However getting to an IPO is a long and twisted path and trying to IPO too early can be disastrous. So a good question to ask is, whether the company will be looking to go public or is the best result a sale to a larger organization which can also be a good result, but keep in mind the point about funding above.
Know when to leave
This is the million dollar question. Say you have joined a startup but you reach a point where you start questioning the viability of said startup, but you have put in a lot of effort into the work there, have made some deep connections and are vested both emotionally and … in options so understandably do not want to leave but yet don’t want to be blindsided by layoffs. Due to the vicissitudes that nearly every startup goes through, this is a pretty normal situation that most engineers find themselves in. Of course in almost every case if after spending some time at a startup an engineer is ambivalent about it’s chances of succeeding, it probably won’t happen. They have already subconsciously picked up on indicators of this throughout their time there and the next step is to consciously acknowledge it. There are a few signs of things not working out that I have observed over the years that would be useful for younger engineers to be aware of:
- Not having enough work: Of all the things in an employee’s control, this is one of the main indicators of the coming doom. This can take many forms including teams not having enough work and just doing startup-y things like playing ping pong all the time(or darts in a place I worked at), teams building things with no clear direction but never actually delivering it to customers, teams doing a lot of busy work to existing products without anything new being built etc. If this goes on for a while, it’s time to get out. Engineering is usually the most expensive part of any Tech startup and if engineers do not have enough to do, they would be the first to get laid off.
- Lack of updates: Most tech companies love doing all hands where the CEO or department heads provide updates around customers, sales, projects, upcoming quarter targets etc. If you as an engineer receiving these updates start feeling like everyone’s going through the motion that is a definitive sign of slowdown. When things are slow or stagnant the CEO/Head of sales etc either repeat the same updates using different verbiage or you will start hearing a lot of updates to the “pipeline”. There will be a lot of “we are in early stages of discussions” etc. which is meaningless till a contract is signed. There is no magic threshold of when these kind of updates become problematic, but if you as an employee start feeling the doldrums, start looking.
- Lack of transparency: Not every startup will open their books up to their employees like Netflix famously does, but lack of transparency around runway or revenue is definitely a red flag. You as an employee don’t need to be able to read the P&L disclosures but if you have no idea about what your company’s ARR is and roughly what runway it has, then you have no control over your destiny. If you see perks being cut and organizational heads not being transparent about layoffs, its time to start putting feelers out. Now transparency can cause issues in an organization where engineers can quit when faced with slowing growth, but transparency helps breed loyalty and the ones that remain are truly committed to the cause.
This is not meant to be a definitive guide on how to approach startups, but hopefully it provides some overarching rules that will help engineers have control over their careers and not get caught unawares.