Questions to Ask Startup Interview
Twenty questions for the team rounds of a startup interview, when you are talking to the hiring manager and the people you would work beside. They cover what the work looks like week to week, how decisions and releases actually happen, what the hours are, and why people have left.
The questions
Open any question for the note
What are you working on this week?
Why ask it
A small question with an unusually high yield. You get the real texture of the work rather than the job description, and you find out whether the person in front of you is doing what they were hired to do. Answers that drift immediately into firefighting tell you where the company's actual load sits.
What did the team ship most recently, and how long did it take from first idea to customers using it?
Why ask it
One concrete cycle time is worth a dozen claims about moving fast. Listen for where the weeks went: review, sign-off, waiting on another team. That is the friction you will inherit, and most people describe it honestly because they find it annoying too.
How did you end up here?
Why ask it
Easy to answer and it gives you their private reasoning about the company, usually including what else they were considering. Someone who joined for the specific problem behaves differently from someone who joined because a friend was here or the market was bad, and both are worth knowing.
What happens in a new person's first month, and who do they learn from?
Why ask it
You are looking for a named person and something resembling a plan. At small companies onboarding often does not exist, which is survivable if they say so plainly and someone is assigned to you. Answers about being thrown in the deep end usually mean nobody has time, and your first month will be spent guessing.
Who decides what I would work on, and how often does that change mid-week?
Why ask it
Two separate facts: the source of authority and the stability of priorities. Frequent mid-week changes are normal at an early stage and exhausting at scale. If several people can reassign you and nobody arbitrates, you will spend your energy on negotiation rather than the work itself.
Walk me through how something gets from a decision to customers.
Why ask it
Asking for the path rather than the process gets you the real steps, including the informal ones: the person who has to be asked, the release that only happens on certain days, the manual step nobody has automated. Hesitation partway through the answer marks the place where the pipeline actually stalls.
How do you find out whether something you shipped worked?
Why ask it
Many startups ship constantly and measure nothing, which means the same debates recur every quarter with no evidence. A team that can name the dashboard, the metric, or the customer they call is a team where your work will be judged on results rather than volume.
What breaks most often, and who gets called when it does?
Why ask it
Gets you the state of the system and the on-call arrangement in one answer, and it is easier to ask than requesting the incident count. If the same person is always the one who gets called, either you are about to become that person or you are about to depend heavily on someone who may be near the end of their patience.
How much of the week is meetings?
Why ask it
A number you can hold up against the claim that this is a place where you get to build things. It also reveals coordination overhead: five hours means small autonomous teams, fifteen at a company of thirty people means decisions are being made by committee and you should ask why.
What does this team do that would look inefficient from the outside but is deliberate?
Why ask it
Flattering to answer and hard to fake, so you tend to get a real trade-off: a slow review step protecting a regulated flow, a manual check after an outage, pairing that costs time and saves rework. A team that cannot name one has usually never examined its own habits.
Honestly, what are the hours, and what happens during a crunch?
Why ask it
Prefacing with honestly gives permission and most people take it. The part to listen for is the crunch, since that is when culture shows: whether it is planned, paid for, recovered from, or simply how every week goes. Ask when the last one was and how long it lasted.
How is pay reviewed here, and has anyone had a raise in the last year?
Why ask it
Small companies frequently have no review cycle, which means compensation moves only when someone threatens to leave. The second half of the question is the test, because a policy can exist on paper while nobody has actually received an increase. A straight answer either way tells you how to plan.
What happened to the last person in this role?
Why ask it
The single most useful question in any interview, and a newly created role is a legitimate answer. If they were promoted, ask how long it took. If they left, listen for whether the reason is about them or about the job, because a role that has burned through two people is a job description problem, not a hiring problem.
When did this team last lose someone, and what changed afterwards?
Why ask it
Departures are unremarkable; the response to them is diagnostic. Look for whether anything was actually fixed or whether the work was quietly redistributed to the people who stayed. The second pattern predicts what happens the next time somebody leaves, possibly you.
What is the hardest part of your job that is not in your title?
Why ask it
Surfaces the unowned work that gets absorbed by whoever notices it: recruiting, customer support, keeping a fragile integration alive, managing one difficult stakeholder. In a small company a good share of that lands on new hires, so it is worth seeing the shape of it now.
Where does this team currently disagree with the founders?
Why ask it
Tests whether disagreement is speakable. A specific answer, even a mild one, means people can push back and survive it. A firm insistence that everyone is aligned is itself the answer, particularly if you hear it from several interviewers in identical words.
What do you wish you had known before you joined?
Why ask it
Invites regret without asking anyone to criticise their employer, which is why it usually works. The answers are practical, that the role was broader than advertised, that a particular system is worse than it looks, that decisions take longer than expected, and you can check each one against what you were told.
What would make you leave?
Why ask it
A candid answer names the fragile thing: a manager, a runway, an unsolved technical problem, the loss of one colleague. This is also the question where you can hear how safe the person feels talking to you, since some will answer only after the recruiter is off the call.
If I joined and it did not work out, what would the reason most likely be?
Why ask it
Asks your interviewer to predict your failure, which sounds risky and consistently produces the most useful answer of the conversation. What comes back is the unwritten requirement: tolerance for ambiguity, willingness to do unglamorous work, the ability to get along with one specific person.
What should I be asking that I have not?
Why ask it
Works because it is the point where the interviewer has seen your whole line of thinking and can spot the gap. Expect something concrete: a dependency, an upcoming reorganisation, a customer contract, a person you should meet before deciding. If they have nothing, the conversation was probably thorough.
Using these across interview rounds
Practical guidance for the conversation itself
Preparing
- Assign different questions to different rounds. Ask a peer what they are working on this week; ask the hiring manager what the role owns; save runway and equity for whoever can actually answer.
- Ask the same question of two people. Where the answers diverge, on hours, on who decides priorities, on why the last person left, is where the interesting conversation is.
- Look up the funding history and recent public news yourself. Spending your slot on facts you could have found reads as unprepared and wastes the one chance to ask about things that are not written down.
- Keep three or four questions per round. Most rounds leave you five to ten minutes, and one question followed up twice beats four asked once.
Reading the answers
Ask for the last time it happened
"Do you have work-life balance?" gets a yes. "When was the last weekend anyone worked, and why?" gets a date and a cause. Convert any question that could be answered with a value into a question about a specific recent event.
Count the hedges
Phrases like generally, we are working on that, and it depends on the week are not lies, they mark the parts of the company that are unfinished. Note where they cluster. Two hedges in a row about the same subject is worth one follow up question.
Ask everyone the departure question
Why people have left is the claim you can most easily triangulate. Consistent stories across interviewers mean an organisation that talks openly about it. Three different explanations for the same person mean nobody was told.
Notice who is not in the process
If you are hired to work closely with a team and never meet anyone from it, ask why. Sometimes it is scheduling. Sometimes the team does not know the role exists, and that is your first week ruined.
Common pitfalls
Asking only about the product
Product questions are the comfortable ones and they are also the ones the company most enjoys answering. If you leave knowing the roadmap but not who decides your priorities or how pay is reviewed, you learned the pitch.
Treating startup risk as a single decision
The risk is not simply whether the company survives. It is also whether the role survives a budget cut, whether your manager stays, and whether the equity is worth anything at a realistic price. Ask about each separately.
Letting enthusiasm stop the follow up
When you want the job, a vague answer feels like enough. Write down the questions you did not press on, and press on them before you accept, in writing if necessary.
Saving all the hard questions for the offer stage
By then you have a deadline and less leverage than you think. Hours, on-call, scope and review cycles are all fair to ask during interviews, and asking early gives you time to verify the answers elsewhere.
After the rounds
Write the contradictions down in one place
List each claim and who made it: hours, ownership, priority setting, turnover. The contradictions are your real interview result, and they are the specific things to raise before you sign rather than general concerns.
Talk to someone who is no longer there
One conversation with a former employee will usually confirm or dissolve everything you were unsure about. Ask what surprised them and what they would check if they were joining today, rather than asking why they left.
Decide what you would need in writing
Scope, title, reporting line, on-call expectations and any promised review date belong in the offer letter or in an email the hiring manager confirms. Verbal commitments at small companies tend not to outlast the person who made them.