That experience rewired how I think about startup interviews. The questions you ask aren't just about gathering information — they're about stress-testing a company's honesty. A good startup will answer hard questions directly. A bad one will deflect, generalize, or give you a rehearsed pitch.

Here are the 10 questions that actually matter, drawn from conversations with 30+ startup employees and hiring managers, and from analyzing 104,875 open startup roles on NewJob.

The 10 questions worth asking

1. "What's your runway, and what has to be true for the next round to happen?"

This is the single most important question you can ask at a startup, and most candidates never ask it. Runway tells you how long the company can survive at its current burn rate. The follow-up — what has to be true — tells you whether the plan is realistic or aspirational.

A healthy answer sounds like: "We have 18 months of runway. We need to hit $3M ARR to raise a Series B, and we're currently at $1.8M growing 15% month-over-month." A red flag sounds like: "We're well-funded" or "We're not worried about that right now."

2. "How many people have left in the last 12 months, and why?"

Attrition at startups is normal — people leave for all kinds of reasons. What matters is the pattern. If three engineers left in six months, that's a signal. If the answer is vague ("a few people moved on"), push harder.

The best version of this question is even more specific: "Of the people who were here a year ago, what percentage are still here?" A startup with 50 people that lost 15 in a year has a 30% attrition rate. That's not a startup — that's a revolving door.

3. "What does this role look like in 6 months if things go well? What about if they don't?"

This question reveals two things: whether the company has actually thought about the role beyond the immediate hire, and whether they're honest about downside scenarios.

At a startup, "things going well" might mean you're leading a team of four. "Things not going well" might mean the product pivots and your role fundamentally changes. Both are fine — but you want to know the range of outcomes before you sign.

4. "Who's the most recent hire, and what's their experience been like so far?"

This is a backdoor question about onboarding and integration. If the most recent hire joined three months ago and is already thriving, that's a good sign. If they can't name a recent hire, or if the answer is hedging, that tells you something too.

Even better: ask if you can talk to that person directly. A startup that's confident in its culture will say yes immediately.

5. "What's the biggest internal disagreement happening right now?"

Every healthy startup has disagreements. Should we go upmarket or stay SMB? Should we hire more engineers or more salespeople? Should we build the feature or buy the integration?

If the interviewer can name a real, substantive disagreement, it means the company has the kind of intellectual honesty that makes startups work. If they say "we're all pretty aligned," either they're lying or they're not thinking hard enough about their problems.

6. "What would I need to accomplish in the first 90 days for you to feel great about this hire?"

This is better than "what are the expectations for this role" because it forces specificity. You're not asking for a job description — you're asking for a success metric. The answer tells you whether the company knows what it needs, and whether the bar is realistic.

Watch out for answers that are either impossibly ambitious ("rebuild our entire data pipeline") or impossibly vague ("get up to speed and start contributing"). The sweet spot is concrete and achievable: "Ship the new onboarding flow and reduce churn in the first-week cohort by 15%."

7. "How do decisions get made here when the founders disagree with the team?"

This is really a question about power dynamics. At some startups, the founders make every decision and the team executes. At others, there's genuine distributed decision-making. Neither is inherently wrong, but you need to know which one you're walking into.

The red flag isn't centralized decision-making — it's dishonesty about it. If the founder says "we're very collaborative" but every employee you talk to says "the CEO decides everything," run.

8. "What's your biggest customer complaint right now?"

This tells you where the product actually is versus where the pitch deck says it is. Every startup has customer complaints. The ones worth joining know exactly what those complaints are and have a plan (or at least a theory) for addressing them.

If the answer is "our customers love us," the interviewer is either in sales mode or genuinely disconnected from the customer experience. Neither is great.

9. "What's the compensation philosophy? How do you think about the cash-equity tradeoff?"

Don't wait for the offer to have this conversation. Ask early. The answer reveals the company's maturity and self-awareness.

Our data shows startup salaries vary wildly by role: engineering medians sit around $210K, while ops roles median at $140K. But the equity component can change the total comp picture dramatically. A startup that's thoughtful about this tradeoff — "we pay at the 60th percentile of market and make up the difference in equity" — is more trustworthy than one that says "we pay competitively" and then lowballs you.

10. "If I talked to someone who left the company, what would they say?"

This is the nuclear option. It's uncomfortable, and that's the point. The answer — or the reaction to the question — tells you everything about how self-aware the leadership team is.

A great answer: "They'd probably say we moved too fast and didn't always communicate changes well. That's fair — we're working on it." A terrible answer: silence, deflection, or "everyone who left wasn't a good fit."

The 5 questions to never ask

"What's the culture like?"

This question is so broad it's meaningless. Every startup will say something about being fast-paced, collaborative, and mission-driven. You'll learn nothing. Ask specific questions about decision-making, disagreements, and working hours instead.

"What's your tech stack?"

If you're an engineer, you already know this from the job posting or a 30-second look at their GitHub. Asking it in an interview wastes a question slot on information that's freely available. Ask about technical debt, deployment frequency, or incident response instead.

"Where do you see the company in 5 years?"

No startup knows where it'll be in 5 years. Most don't know where they'll be in 12 months. This question invites a rehearsed vision pitch that tells you nothing about the present reality. Ask about the next 6-12 months instead.

"Do you offer remote work?"

Again, this is on the job posting. Our data shows 16% of startup jobs are fully remote, 16% are hybrid, and the rest are in-office. If the listing says "San Francisco" and you want to work from Bali, this isn't the right role — no interview question will change that.

"Can you tell me about the benefits?"

Benefits matter, but they're a negotiation topic, not an interview topic. Asking about benefits in a first-round interview signals that you're more interested in the package than the work. Save this for after you have an offer, when you have leverage.

The meta-lesson

The best startup interview questions share a common trait: they're hard to answer with a rehearsed pitch. They require honesty, specificity, and self-awareness. If a startup can answer these questions well, it's probably a good place to work — not because the answers are perfect, but because the willingness to engage with hard questions is itself the signal.

And if they can't? Well, at least you found out before you signed the offer letter. That's a lot cheaper than finding out 14 months in, when the runway runs out and nobody seems surprised except you.