Which questions should a candidate save for a startup founder rather than a peer engineer?

## Why this conversation is different In a startup loop you usually get one slot with a founder or a senior executive. The engineers you meet own the work; the founder owns the bet. Joining an early-stage company is closer to an investment than a job change — a share of your compensation and several years of your career ride on whether the company still exists and is growing when you get there. That makes the founder slot your **diligence window on the business**, and the questions that belong in it are the ones only an owner can answer. ## The diligence checklist Carry four items and know why each one is on the list: | Item | What you are testing | Who else could answer it | |---|---|---| | Funding stage and runway | How long the current plan is funded for, and what has to be true to raise again | Nobody in the loop, reliably | | Path to revenue | Who pays today, what they pay for, who is expected to pay next | Sometimes a sales leader; usually the founder | | Moat | Why a better-funded competitor cannot copy this in a quarter | The founder | | Key-person risk | Which handful of people the product or the customer relationships depend on | Partly engineers; the founder sees the whole shape | Everything outside those four rows has a better owner. How a change reaches production, what on-call feels like, how review works — those belong to the engineers you meet, and they will give you a truer answer than a founder can. ## A worked example Imagine an early-stage company selling demand-forecasting models to operations teams. Across the table is a co-founder who still writes code. You open with 'What keeps you up at night about this business?' The answer: the models work, but every new customer needs bespoke data plumbing before the first forecast is useful, so onboarding drags. That one answer moves three checklist rows at once. Revenue path: the sales cycle is longer than the pitch implies. Moat: the defensible asset may be the integration work rather than the modelling, which is a very different company to join. Key-person risk: someone is doing that plumbing by hand, and you should ask who. Follow the thread the founder opens rather than marching down your list — the checklist is there so you notice which rows got answered, not so you read it aloud. ## Equity context, kept to shape The founder slot is also a reasonable place to understand what an equity offer *means* in context — roughly what fraction of the company a grant represents, and how founders expect later financing rounds to affect early employees. Keep it to shape rather than terms. Plan mechanics differ from company to company, and the tax and legal treatment of equity varies by country and by personal circumstance, so treat anything said in an interview as background and get independent advice on your own documents before you rely on it. Detailed negotiation of the grant belongs with whoever owns the offer, not here. ## How founders read these questions Direct business questions usually read as seriousness — a candidate who asks about runway is a candidate imagining themselves there in two years. Two caveats. First, tone: this is a conversation, not a cross-examination, so ask, listen, and follow up on what they actually said. Second, calibration: founders differ widely in what they will share, and some are constrained by agreements with their investors, so a partial answer is not automatically a bad sign. The common failure is the opposite of over-asking. Candidates enjoy the founder chat, talk about mission and culture for the whole slot, and walk out without knowing whether the company is funded for the coming year. That is the one mistake this leaf exists to prevent.