What questions to ask a startup before joining them?
Question
Answer
I got burned once — two unpaid salaries, a panicked Slack message at midnight, and a curt “we’re out of cash” from the founder. Ever since, I keep a mental checklist when talking to early-stage teams, though it didn’t fully fix things. I ran through it with someone on my team last week, who’s considering a small AI startup, and figured I might as well write the questions down while the coffee buzz is still strong.
The Product
Start with the problem, not the pitch deck. Ask the founders to describe, in one sentence, the pain they’re fixing. Then push for a demo — a real one, not a Figma prototype. If they can’t pull up something that works in under five minutes, that’s a yellow flag.
Drill into alternatives. “Who else solves this today, and why do customers still suffer?” When I asked that at a previous gig, the CEO shrugged and said, “Well, nobody likes the incumbents.” Cute, but not strategy. I could be wrong, but unless they can name at least two competitors and articulate a wedge (“cheaper for SMBs,” “10× faster onboarding,” whatever), the moat probably isn’t there.
The value prop should also survive edge cases. If the answer is a hand-wavey “we make businesses grow faster,” pick an obscure segment — cafés that never touched Instagram, for example — and see if the story still holds. (Side note: I love that test because it forces specificity without sounding confrontational.)
The Funding
Everyone asks about runway; few dig into revenue traction. I now open with “What was last month’s net burn and did you hit the revenue target?” The combo tells you whether the CFO has a handle on both sides of the equation. I’m not entirely sure this scales beyond seed stage, but for sub-Series-A teams it’s revealing.
Follow up with cash cadence: how often do they re-forecast? Quarterly is fine; once a year is a gamble. I’ve seen founders miss projections by a significant percentage and still keep the same slide until the board caught it. That’s how you end up with the dreaded Friday email: “Payroll’s delayed, sorry.” Two friends got 48 hours’ notice before the taps shut off — trust me, you don’t want to be the third.
Investors matter too. Ask who holds preferred shares and what rights they negotiated for the next round. If the cap table is a Jenga tower of SAFEs, brace for fireworks when things get tight.
The Equity
Options sound glamorous until you learn about liquidation preferences. In most exits, preferred shareholders (read: VCs) get paid first, sometimes 1.5× or 2× their investment. Common-stock holders — that’s you — split what’s left. I got this wrong for the first 18 months of my career and thought the spreadsheet math was broken.
Questions worth asking:
- What’s the current preference stack?
- Is there a single trigger for accelerated vesting (rare, but ask)?
- Do they plan to refresh grants after dilution?
Then run a sanity check against big-tech compensation. Senior engineers at FAANG pull north of $400 k in RSUs and cash. If the startup’s expected value — probability-weighted, post-liquidation pref — doesn’t come close, you’re essentially buying a lottery ticket with sweat. Sometimes that’s fine, sometimes not.
One more nuance: early teams often swap higher equity for lower salary. That trade improves only if the strike price is friendly and future financing isn’t overly dilutive. I’ve seen founders waive vesting cliffs to sweeten the deal; that’s a positive sign, though it doesn’t fix a messy cap table.
The HR Stuff
Headcount tells a story. A four-person sales team without a single QA engineer? Watch for tech-debt avalanches. Ask who joined in the last three months and who left — churn rate inside year one reveals culture issues faster than any Glassdoor review.
Also poke at founder dynamics. How long have they worked together before raising money? If the answer is “we met at a hackathon three weeks ago,” expect fireworks when stress ramps up. (I’m not judging — some of the best teams formed that way — but correlation with co-founder breakups is real.)
The Working Environment
Duties matter, but so does acoustic reality. Open plans can be a productivity black hole — constant chatter, Zoom overlaps, the guy who treats stand-ups like TED Talks. Ask if there are quiet rooms, whether noise-canceling headsets are expensed, and how often the team works remotely. That last bit shapes culture far more than weekly pizza Fridays.
On workload: “40 hours-ish, but we value ownership” can translate to heroic weekends before every release. Get examples. When was the last crunch? How did leadership handle time-off afterward? I could be wrong, but credible founders will answer with a concrete incident, not abstractions.
Growth paths are another tell. Startups can’t always promise titles, yet they should outline how responsibilities evolve. No plan = likely chaos once the first layer of middle management appears.
Questions for yourself
Finally, turn the lens inward. Are you okay trading predictable comp for swing-for-the-fences upside? Can you thrive without process (well, more like despite the lack of it)? Does the mission still excite you after you’ve poked all the holes above? If any answer feels shaky, sleep on it. Gut checks beat FOMO nine times out of ten.
Conclusion
I love when candidates grill me — it signals they’ve done the homework and won’t bail at the first headwind. So ask. Be curious, borderline annoying if needed, and keep asking until the picture is clear enough for you. Worst case you learn a ton and pass; best case you join a rocket with eyes wide open.
More questions from users:
Worried your codebase might be full of AI slop?
I've been reviewing code for 15 years. Let me take a look at yours and tell you honestly what's built to last and what isn't.
Learn about the AI Audit →No-Bullshit CTO Guide
268 pages of practical advice for CTOs and tech leads. Everything I know about building teams, scaling technology, and being a good technical founder — compiled into a printable PDF.
Get the guide →
1 Comment
When I was eyeing a spot at a new startup, I zeroed in on understanding their actual work culture, beyond the buzzwords in their job listing. I asked for examples of projects that went well and those that didn’t – this opened up a real conversation about their processes and how they handle setbacks. I also nudged for a casual chat with future colleagues, which gave me a sneak peek into the daily grind and teamwork dynamics. Frankly, these chats were more insightful than any mission statement on their website, offering a raw glimpse into what my day-to-day would look like.