How to evaluate startup risk before you join
Startup risk is not one number. It is seven inputs you can mostly check yourself in an afternoon: runway, burn, market, team, traction, the funding signal, and your own fallback.
By the roles.cc team··10 min read
Startup risk is not a feeling. It is roughly seven inputs you can check in an afternoon: how much runway the company has, how fast it burns, how big and reachable the market is, who is on the team, whether anything is working yet, how recently someone priced the company, and what your own fallback looks like if it folds. Most engineers fixate on one of these (usually the product idea) and ignore the other six. The point of a framework is to stop you from over-weighting the part that is easiest to have an opinion about.
None of this tells you the company will succeed. It tells you whether the bet is priced honestly and whether you can afford to lose it. That is the only question you actually control. The roles.cc board sorts every role by funding recency precisely because that one signal compresses several of these inputs at once, but recency alone is not a full read. Here is the rest of it.
What are the inputs to startup risk?
Think of risk as a grid, not a score. Each cell is a question with a checkable answer. You want most cells green before you sign, and you want to know exactly which ones are red so you can ask about them directly in the interview.
- Runway. How many months of cash before the company needs to raise again or hit profitability. This is the single most load-bearing number.
- Burn. How fast that cash leaves, and whether headcount is about to make it leave faster.
- Market. Is the thing they sell something a real budget already pays for, or are they betting a budget appears.
- Team. Have the founders shipped before, can they recruit, and is the eng org someone you would learn from.
- Traction. Is anything working: revenue, usage, retention, a waitlist that converts. Even a small real number beats a big imaginary one.
- Funding signal. How recently a round closed and who led it. We cover this in depth in should you join a startup that just raised.
- Your fallback. How fast you could get re-employed and how much runway you personally have. Risk is relative to what you can absorb.
How much runway is enough?
Runway is months of cash at the current burn. You compute it as cash in bank divided by net monthly burn. A fresh seed round of $3,000,000 spending $150,000 a month has 20 months of runway (illustrative, not advice). A Series A of $12,000,000 burning $600,000 a month has the same 20 months despite being four times the size. The dollar figure on the press release tells you almost nothing. Months tell you everything.
The danger zone is not low runway in the abstract. It is low runway with no plan to extend it. Twelve months of runway is fine if the company has a credible path to a new round or to break-even inside that window. Twelve months with flat revenue and a fundraising market that has cooled is a different bet. Ask the question plainly in your loop: how many months of runway, and what has to be true to raise the next round. A founder who answers crisply is a good sign. A founder who dodges is the answer.
18 to 24 mo
typical seed runway
planned, not guaranteed
about 24 mo
typical Series A runway
more cash, also more burn
6 to 9 mo
the zone to ask hard questions
raise-or-die territory
How do I read burn and headcount together?
Burn is not just today's number. It is today's number plus the hiring plan you are part of. A company at $200,000 a month burn that just closed a round and plans to hire ten people is really a $400,000 a month company two quarters from now. Run the math forward, not backward. Take the cash, subtract the planned hires at a loaded cost of roughly 1.3 times salary, and see how the runway shrinks (illustrative, not advice).
This is why a fresh raise is reassuring and also why it is the moment burn accelerates the most. The round refills the account and the headcount plan immediately starts draining it. You want to join a company that is spending deliberately against a thesis, not one that raised and then went on a hiring spree with no revenue to show for the last one. If the company has raised twice and the revenue line is still flat, that is the cell to mark red.
How do I judge the market and traction without inside data?
You will not get the data room. You can still triangulate. For market, ask whether the company is selling into a budget that already exists (replacing a tool people pay for) or trying to create a new budget. Replacing an existing spend is lower risk because the buyer is already convinced they should pay for the category. Creating a new category is higher reward and much slower, which eats runway. Neither is wrong. They are just different risk profiles you should price into your equity expectations, covered in is startup equity worth it in a down market.
For traction, push for one real number in the interview. Monthly recurring revenue, weekly active users, week-four retention, design partners who have signed, anything concrete. A founder who shares a real, modest number is more trustworthy than one who only talks about the size of the market. A $40,000 a month revenue line that doubled in two quarters is a stronger signal than a $5,000,000,000 total addressable market with no customers (illustrative, not advice). When you research before the loop, the methods in how to research a startup before you interview get you most of what you need.
How much should the funding signal count?
A recent round from a known lead does three things at once: someone with real information just priced the company, the bank account is full, and the role you are interviewing for was budgeted weeks ago. That is why it is the best single hiring signal and why our board leads with it. You can watch fresh rounds land on the recent raises page. But recency is a lagging proxy for the other inputs, not a substitute. A company can raise a strong round and still burn it badly.
Weight it like this: the funding signal is your fastest filter for which companies to interview at, and the other six inputs are how you decide which offer to sign. Use the raise to build your shortlist. Use runway, burn, market, team, and traction to pick within it. We unpack the timing logic further in why funding recency is the best hiring signal.
Use the raise to decide where to interview. Use the other six inputs to decide where to sign.
How do I weight the inputs against each other?
There is no universal formula, but there is a sane default. Runway and burn are gating: if those are red, nothing else matters much because the company may not be around long enough for the upside to land. Team and traction are the upside drivers: they decide whether the bet pays off if the company survives. Market sets the ceiling. The funding signal is your speed filter. Your personal fallback is the multiplier on all of it, because the same company is a reasonable bet for someone with savings and a fast re-employment path, and a reckless one for someone with neither.
| Input | Weight | Red flag | Green flag |
|---|---|---|---|
| Runway | Gating | Under 9 months, no raise plan | 18+ months or near break-even |
| Burn | Gating | Accelerating, flat revenue | Deliberate, tied to a thesis |
| Market | Ceiling | New budget, slow to prove | Replacing an existing spend |
| Team | Upside | First-time, cannot recruit | Shipped before, hires well |
| Traction | Upside | Only talks about market size | One real, growing number |
| Funding signal | Filter | Stale round, unknown lead | Recent round, known lead |
| Your fallback | Multiplier | No savings, slow re-employ | Runway plus a fast network |
Weights are a starting point. Adjust to your own situation, not the other way around.
A worked example
Two offers, both Series A, both in San Francisco, both around $180,000 base (illustrative, not advice). Company A raised $15,000,000 nine months ago, burns $700,000 a month, has flat revenue around $50,000 a month, and a founder who deflects the runway question. That is roughly 12 months of runway with no traction and a tell. Company B raised $9,000,000 two months ago, burns $350,000 a month, has revenue at $120,000 a month that grew from $60,000 over six months, and a founder who tells you the runway number without being asked twice. That is over 25 months of runway with a real growth line.
Company A has more cash on the press release and is the worse bet on six of seven inputs. The raise was bigger and older, the burn is faster against flat revenue, and the founder's non-answer is its own data point. This is exactly the inversion the framework is built to catch. The bigger headline number masked the worse risk profile. Once you have an offer like B in hand, the mechanics in how to evaluate a startup job offer help you turn the read into a decision.
What if most cells are red but the upside is huge?
Then you are making a real bet, and the right move is to be honest that it is one. High-risk, high-reward is a legitimate choice when your personal fallback is strong: you have savings, your skills are in demand, and you could land a new role in weeks. It is a bad choice when a few months without income would be a genuine problem. The company's risk does not change. Your ability to absorb it does. Size the bet to what you can lose, and weight your offer toward base salary over options when the cells are red, since options are the part that goes to zero first.
Questions people ask
How do you calculate a startup's runway?
Runway is cash in the bank divided by net monthly burn, expressed in months. A company with $3,000,000 in the bank spending a net $150,000 a month has 20 months of runway. The dollar size of the round matters far less than the months it buys, so always convert to months before comparing two companies.
How much runway should a startup have before I join?
As a rough guide, 18 months or more is comfortable, 9 to 12 months is fine only if there is a credible plan to raise again or reach break-even in that window, and under 9 months with flat revenue is raise-or-die territory. The number matters less than the plan behind it. Ask the founder directly how many months of runway they have and what has to be true to raise the next round.
Is joining a startup that just raised less risky?
It lowers some risks and raises others. A fresh round means full cash, 18 to 24 months of runway, and a budgeted role, which is why it is the best single signal. But a raise also accelerates burn through new hiring, and it does not prove the product works. Use the raise to decide where to interview, then check runway, burn, market, team, and traction to decide where to sign.
What is the biggest mistake engineers make when evaluating startup risk?
Over-weighting the product idea, which is the input they have the easiest time forming an opinion about, and under-weighting runway, burn, and traction, which are the inputs that actually determine survival. A company with a brilliant idea and nine months of cash against flat revenue is riskier than a company with a boring idea and 25 months of runway with growing revenue. Treat risk as roughly seven inputs and check all of them.
How do I assess a startup's traction without seeing internal data?
Ask for one concrete number in the interview: monthly recurring revenue, weekly active users, week-four retention, or signed design partners. A founder who shares a modest real number is more trustworthy than one who only cites the size of the market. A small revenue line that is growing beats a large total addressable market with no customers.
Should I take a riskier startup if the equity upside is large?
Only if your personal fallback can absorb the downside. High-risk, high-reward is reasonable when you have savings and could find a new role quickly, and unwise when a few months without income would be a real problem. The company's risk does not change with your situation, but your ability to survive it does. When the inputs are mostly red, weight your offer toward base salary over options.
The data is live roles
Every number in this post comes from live US engineering roles we track daily, sorted by funding recency.
About roles.cc. roles.cc is a recruiting agency for software engineers at venture-backed startups in San Francisco, New York, and other major US hubs. The public board lists engineering roles pulled straight from each company's own job site, sorted by how recently the company raised. It is free for engineers. Start by sending your resume or reading what we do.