How should a candidate interpret a founder who answers a runway question without naming months?
answer
- Observation first, conclusion later
- Notice what was offered instead
- Ask once more, narrower, then stop
- Corroborate with hiring pace and departures
- One deflection is weak, a pattern is not
basics
~20 sTreat it as one signal, not a verdict. Note what was offered instead — total raised, investor confidence, a growth story — ask once more for months, then corroborate against hiring pace, recent departures and how the offer is pitched before drawing a conclusion.
solid answer
~50 sA non-answer is information, but weak information on its own. First, notice the substitution: total funds raised, investor quality or a growth story in place of a number of months usually means the founder would rather not state the clock. Second, ask once more, narrowed — 'is the company funded past the point where the work I'd be doing pays off?' — because a bounded answer is often available when a precise one is not. Third, corroborate elsewhere: how fast hiring is moving, whether senior people left recently, whether the pitch leans unusually hard on future upside. Then hold the read privately. Founders vary in what they will share and some are constrained by their investors, so a single deflection is not evidence of trouble — a deflection plus a slowed hiring plan is a pattern worth acting on.
go deeper
Notice and record what you actually heard rather than what you feared. If a founder answers with total funds raised instead of months, write that down and ask someone else in the loop what changed after the last round.
Explain why deflections happen — discomfort, investor constraints, a blanket policy — and how a narrowed second ask separates those causes. Know that you get one follow-up, not three.
Demonstrate triangulation: weigh hiring pace, recent senior departures and how the compensation is pitched, discount the weak signals like a quiet office, and hold the read privately until the decision actually arrives.
Own the risk decision under uncertainty you cannot resolve. Decide in advance what evidence would change your answer, accept that a bounded answer may be the most you get, and judge the company partly by how it handled being asked.
## What a deflection is and is not When you ask an owner how many months of runway the current plan is funded for and get something other than a number, you have learned something — but far less than the sinking feeling suggests. Founders decline for several reasons, and they look identical from the candidate's chair: - The number is uncomfortable and they would rather discuss it after an offer. - They are constrained by agreements with their investors, or by norms and rules about what a private company shares with outsiders, which differ by jurisdiction. - They have a policy of not discussing financials before an offer stage and apply it to everyone. - They genuinely do not think in those terms week to week, which is itself a signal about how the company is run. So the first discipline is to separate the observation from the conclusion. The observation is: *asked for months, received something else.* That belongs in your notes verbatim. ## Read the substitution What gets offered instead is the most informative part. | Instead of months, you hear | Reasonable read | |---|---| | Total raised across all rounds | A cumulative figure that sounds large; time-bought is not being discussed | | Investor names and their enthusiasm | Confidence framed as evidence; still no clock | | 'We're focused on growth, not runway' | Either a deliberate deflection or a genuinely loose grip on burn | | 'We're raising right now' | Often the most honest deflection there is, and worth following gently | | A stage label and nothing more | Policy, most likely, rather than concealment | ## Ask once more, narrowed The second ask should shrink the question rather than repeat it. Precision is what the founder declined; a bound may still be available: *'I understand. Can you tell me whether the company is funded past the horizon where the work I'd be hired for would pay off?'* Or: *'Is the next round something you expect to run on your own schedule, or on a deadline?'* Both are answerable without disclosing a figure, and both distinguish policy from discomfort. Ask once. A third pass converts a candidate doing diligence into a candidate who cannot read a room, and it will be remembered. ## Corroborate outside the conversation A single deflection is weak evidence; a pattern is not. Signals worth weighing, roughly in order of usefulness: - **Hiring pace.** A company that raised recently and has slowed hiring noticeably since is telling you something about burn discipline. Ask an engineer how many people joined recently and how many roles are open in practice, not on the careers page. - **Senior departures.** People with the best information leave first. This is worth noticing and easy to over-read, since people leave for ordinary reasons too. - **How the offer is pitched.** An unusually heavy emphasis on future upside, and reluctance to discuss cash, sometimes tracks a tight plan. It is a soft signal, not a proof. - **What other interviewers say.** Ask an engineer what changed after the last round. Discrepancies between what the founder said and what the team believes are more informative than either answer alone. Weak signals that people over-weight: a quiet office on the day you visited, a tired founder, a long list of open roles on a careers page that nobody has pruned. ## Deciding what to do with the read Hold the conclusion until you have to make a decision, then make it explicitly. Three reasonable outcomes: proceed and accept the risk knowingly; proceed while revisiting the question at the offer stage, where more candour is common; or step back because your own circumstances leave no room for a short clock. What you should not do is either extreme — treat one deflection as proof of collapse, or bury the question because the conversation was pleasant and you liked the founder. One more thing to notice: how a founder handles an uncomfortable question is a preview of how uncomfortable questions go inside the company. A founder who says 'I'd rather give you the full picture at the offer stage, and here is the bound I can give you now' has told you something good about the place, even though they told you no number at all.
- You get a deflection from the founder — what do you ask a peer engineer later in the loop?Ask what changed after the last round: how many people joined since, whether any planned hiring was paused, and whether priorities were reshaped. Engineers answer factually about their own team without realising they are corroborating a financial picture, and the gap between their account and the founder's is the informative part.
- The founder says 'we're raising right now' — is that a good sign or a bad one?Neither by itself; it is the most common state an early-stage company is in. The useful follow-ups are what the round is being raised on and what the plan is if it takes longer than hoped. A founder with a specific answer to the second question is showing you they run the business with a margin.
- What would move you from a private doubt to actually declining on this basis alone?A pattern rather than a moment: a deflection, plus hiring that visibly slowed since the last round, plus senior departures, plus an offer weighted heavily toward future upside. Any one of those has innocent explanations; together they describe a company managing a shorter clock than it wants to state, and it is fair to weigh that against your own circumstances.
saying these in an interview costs you the question
- Reading a single deflection as proof the company is failing
- Pressing the same runway question a third time
- Concluding from a quiet office or a tired founder
- Dropping the question entirely because the founder was likeable
- Never corroborating the answer with anyone else in the loop