A first startup offer is a different kind of document from a graduate scheme offer, and the questions you ask before signing should reflect that. The ones that matter most cover runway (how long the company can pay you), equity (what your options are really worth), role scope (what you'll actually be doing) and expectations (what "success" means after six months). Ask them politely, in writing where you can, and treat a vague answer as an answer.
What a startup offer actually is
A startup offer is a salary, a bundle of share options and a set of unwritten assumptions about how you'll spend your days. The salary is the only part that's guaranteed. The options might be worth something in five years or nothing at all, and the assumptions are where most first-timers get caught out.
I spent eight years writing code at a London fintech before moving into hiring, and I now run engineering recruitment for a scaling SaaS company. So I've been the junior who said yes too fast, and I've been the person on the other side of the table watching candidates do the same. The pattern is consistent. People ask about the tech stack and the office snacks. They don't ask about money in the bank.
Beyond Tick Boxes: Diversity Recruitment Strategies That Actually Transform UK Workplaces
Master the Virtual Hot Seat: 7 Video Interview Techniques Recruiters Don't Tell You
AI Governance Careers Surge in 2026: Why This Role Will Define the Next Decade
Why it matters in 2026
Funding has been tighter for a few years now, and a lot of early-stage companies are still running leaner than the ones people remember from the boom. That's not a reason to avoid startups. Some of the best engineering experience I've seen came from small teams where one junior ended up owning a whole service. But it does mean the gap between a well-run young company and a shaky one is wider than it was, and the offer letter won't tell you which one you're looking at.
The UK government publishes plain guidance on what an employer must put in writing, including your written statement of employment particulars. Read it. Then read your own contract against it, because small companies sometimes work from templates nobody has looked at in years.
Questions about runway
Runway is how many months the company can keep paying people at the current rate of spending. It's the single most useful thing to understand, and the one juniors feel least able to ask about.
You're not being rude. A founder who's raised money recently will usually tell you straight, because they're proud of it. So ask when the last funding round closed, roughly how long it's expected to last, and whether the company is aiming for another raise or for profitability. Then listen to how they answer, not just what they say.
A few follow-ups that don't sound like an interrogation:
- Is the company profitable, or does it depend on the next round?
- What happens to hiring plans if that round slips by a few months?
- Has the team shrunk at any point in the last year, and why?
That last one is useful because founders who've done layoffs tend to be more candid than founders who haven't. And a team that's lost a lot of people quietly is telling you something, even if nobody mentions it in the interview.
One thing I'd add. If the answer is "we don't really share that", you can still decide to join. Plenty of people do and it works out. But go in knowing you're making a bet with incomplete information, and keep your savings sensible.
Questions about equity
Share options are the part of a startup package that sounds exciting and gets explained worst. An option is the right to buy shares at a fixed price later. It's not shares in your account today, and it's not money.
So what do you ask? Start with the basics: how many options, what percentage of the company that represents, and what the strike price is. If they can't tell you the percentage, you can't judge the offer, because ten thousand options means something completely different in a company with a million shares than in one with a hundred million.
Then the terms that decide whether you ever see a penny:
- The vesting schedule (a four year schedule with a one year cliff is common, meaning nothing vests if you leave before twelve months)
- What happens to unvested options if the company is acquired
- How long you have to exercise after you leave, because some companies give you ninety days and some give years
That exercise window catches people constantly. You can leave a company having earned options, then find you'd need to pay thousands out of your own pocket within three months to keep them. Most people can't. So the options lapse.
HMRC has guidance on the tax-advantaged option schemes UK startups often use, including Enterprise Management Incentives. Ask whether your options sit under one. It changes the tax treatment, and it's a fair question to put to the founder or whoever handles people operations.
My own view, for what it's worth: treat equity as a lottery ticket you've been handed for free. Don't take a lower salary on the strength of it unless you've done real homework on the company. I've watched juniors accept a meaningful pay cut for options that never became anything.
Questions about role scope
This is where "software engineer" on the offer can mean almost anything. In a team of six, you might be writing React in the morning, debugging a flaky pipeline after lunch and answering a customer's support ticket by five. That can be a brilliant way to learn. It can also be a mess.
So find out how work really arrives. Is there a product manager writing tickets in Linear or Jira, or does a founder message you on Slack with a screenshot and a vague idea? Who reviews your pull requests? If the honest answer is "nobody, we're all busy", that's a problem for a first job, because code review is where juniors learn most of what they know.
Questions worth asking:
- Who will I report to, and how much of their week do they spend on engineering rather than management or fundraising?
- Is there a staging environment, and does anyone else look at my code before it ships?
- Is anyone on call, and will I be?
- How is work prioritised when two people want different things at once?
On-call deserves a straight answer. At a big company it's usually a rota with compensation attached. At a startup it can mean you're the person who gets the alert at 2am because you're the person who knows the service. Neither is automatically bad, but you should hear it before you sign and not in week three.
I'd also ask what the stack really looks like, not the version in the job advert. Adverts list everything the founders wish they used.
Questions about expectations
This is the softest category and the one I'd most like juniors to push on. What does a good first six months look like here? If the manager can't describe it, that tells you something, and not something comforting.
Ask how performance is judged and when the first review happens. Ask whether there's any structure for progression, even loose, because "we'll figure it out" is common and sometimes fine, but sometimes it means a promotion cycle that depends on who shouts loudest. Ask about working hours too. A culture of staying late "when needed" can quietly become the default.
And ask about mentoring. Is there a senior engineer who'll genuinely have time for you? Early-career people underestimate how much a good senior colleague is worth compared with a slightly higher salary. I'd take the better mentor every time. I didn't, once, and I paid for it in a year of slow learning.
For a sense of what a well-run offer conversation looks like in another field, this piece on marketing job offer questions covers similar ground from a different angle.
Who a first startup job suits
It suits people who learn fast by being thrown in, who can live with a bit of mess, and who don't need a rigid structure around them. If you like seeing your work in production within days, a small company will give you that far sooner than a bank's engineering department would.
It suits you less if you need clear process, formal training or a stable salary because you've got rent and debt to cover. That's not weakness. Some of the strongest engineers I've hired started at large employers with proper graduate programmes and then moved to smaller firms once they knew what good looked like.
Salary matters here too. Early-stage companies often can't match what larger firms pay, and the gap is easy to underestimate. Check what comparable roles pay before you accept, and look at engineering and developer vacancies on OHUB to see what employers are advertising for similar levels. Pay at startups varies enormously, so benchmark rather than guess.
How to get started
Write your questions down before the final interview, not after the offer lands, because you'll feel more pressure to be agreeable once there's a number on the table. Send the equity and contract questions by email so you've got the answers in writing. A decent founder won't mind. One who gets defensive about basic questions has shown you something about how they'll handle harder ones.
If you're still looking and want to see how different employers present themselves, OHUB's employer pages give a feel for how companies describe their teams and what they say about working there. And if you want a second pair of eyes on an offer, ask someone a few years ahead of you in the industry. Most will say yes.
What would you do if every answer you got was friendly, enthusiastic and completely empty?