Questions to Ask in a Startup Interview
For a candidate working out which questions to ask a startup company in an interview, at any stage from a handful of people to a few hundred. A startup job interview is as much your check on the company as its check on you, so the list is grouped by what you are trying to find out: whether the business has customers and money, what the role really covers, how the work gets done week to week, what the pay and equity are worth, and what the founders and the team are like when things go badly.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The business
How many months of runway is the company working with, and does that number assume revenue keeps growing?
Why ask it
Runway quoted as cash divided by today's spending is a fact. Runway that counts on sales that have not happened yet is a forecast, and the two can be many months apart. Anyone senior should know which one they are giving you, and a peer who has no idea tells you how much the team is told.
How is the company funded, and when did it last raise money?
Why ask it
Check what is public before you ask, then use the question for what the announcement leaves out: how much of that round is left and what it was raised to do. A company funded by its own revenue or by its founders is a different bet from one on venture money, usually with less cash to spend and no investor expecting a sale. If the last round was a long while ago, ask what the plan is for the next one.
How does the company make money, and how has revenue changed over the past year?
Why ask it
Expect one or two sentences on who pays and for what. A long or shifting explanation usually means the model is still being worked out, which is common early on and worth knowing. Many private companies will not give a revenue figure in an interview, so ask for the direction and the rough pace, and leave the exact number for the offer stage.
What are the company's main goals for the next 12 months?
Why ask it
A good answer is short and can be checked: a revenue figure, a launch, a number of customers, the next raise. Ask what happens if the main one is missed, since at a startup that tends to decide hiring, budgets and sometimes whether a role continues. A list of eight goals means the choosing has not been done yet.
What is the biggest challenge the company is facing right now?
Why ask it
Every startup has one, so the test is whether you are told it. A specific problem, such as a slow sales cycle, one customer who accounts for too much of the revenue or a hire they cannot make, shows a team that sees its position clearly. Ask what is being done about it and whether your role is part of the fix. An answer about growing too fast is a pitch.
Who are the main competitors, and what does this company do better than they do?
Why ask it
Look the competitors up beforehand so you can tell whether the list is complete. A good answer is specific about one or two rivals and honest about where they are stronger. A claim to have no competition means either the market is untested or the interviewer has not looked. Follow with which rival the sales team meets most often.
Are customers paying, in a pilot, or using it free, and roughly how many of each?
Why ask it
The word customers covers all three in a pitch, and only one of them pays salaries. Pilots are normal early on, so ask how many have turned into contracts. A list that is all logos and no invoices means the hard part is still ahead.
Could the company reach break-even on the money it already has, if it had to?
Why ask it
A company that would like more funding and one that closes without it answer this very differently. A clear answer names what would be cut and what revenue would have to do. If nobody has thought about it, the plan depends on investors saying yes again.
Is the company still working out what customers will pay for, or growing something that already sells?
Why ask it
Those are two different jobs under the same title. In the first, expect the plan and possibly your role to change every few months, and in the second expect targets and process to arrive quickly. A founder who claims both at once should be able to say which customers are the evidence.
How many people work here now, and how many do you plan to hire over the next year?
Why ask it
Headcount set against funding gives you a rough sense of how fast the money is being spent. Rapid hiring means new managers, new process and a different company within a year, and a flat plan means the people you met are the ones you will work with. Ask which roles come first, because that shows where the company thinks it is weakest.
Has the company ever had a layoff, a pay cut or a hiring freeze, and how was it handled?
Why ask it
Plenty of good companies have been through one, so a yes is not the warning. Listen to how it was done: how much notice, what people left with, whether the founders took a cut too, and whether those who stayed were told the truth. Expect the same treatment if there is a next one.
Would the current investors put in more money if a new round took longer than planned?
Why ask it
Backers who would bridge a gap buy the company months that the cash figure does not show. Only a founder or the finance lead can answer this, so save it for them, and ask whether those investors joined the last round.
What do the founders want in the end: to sell the company, take it public or keep running it?
Why ask it
Equity generally turns into money only through a sale, a listing or some other chance to sell shares, so the founders' aim sets what your grant could ever become. A company built to stay private and profitable can be a fine employer whose options never become cash. Founders rarely know the timing, and a confident date deserves more doubt than an honest shrug.
Why would a customer choose this over carrying on as they are?
Why ask it
For many young companies the real rival is the spreadsheet, the agency or the habit a buyer already has, and a good answer names what that costs the customer today. If you get a list of features, ask who switched most recently and what pushed them.
What do customers use the product for most, and is that what you built it for?
Why ask it
A gap between the two is common and can be how a startup finds its real market. What matters is whether the company has noticed and followed the usage, or is still selling the original idea to people who want something else.
How long does a sale take from first conversation to money in the bank, and who has to be involved?
Why ask it
Cycle length tells you how quickly the company learns whether a change is working, and how lumpy the revenue is. If every deal needs a founder on the call, growth is capped by the founder's calendar, which matters most if you are joining sales, support or product.
When did someone on this team last speak to a customer directly, and what changed because of it?
Why ask it
At a small company there is no reason for the people building the product to be several steps from the people who rely on it. A recent date and a concrete change is the good answer. Where customer contact belongs to one person, ask whether you would be allowed in the room.
Which customer request have you turned down recently, and why?
Why ask it
A startup with one large customer can turn into that customer's contract workshop without ever deciding to. A specific refusal shows there is a product direction that survives a loud request. When nothing has been refused, the next question is who owns the roadmap in practice.
The role
What would success look like in this role after the first 90 days, and after a year?
Why ask it
At a startup the honest answer is often a problem to solve more than a list of duties, and that is fine as long as someone can name it. Listen for whether it can be measured and whether the things it depends on, such as a budget, a hire or a product release, are in your hands. If two interviewers describe success differently, raise it before you accept, because you will be judged by both.
What set this hire off: new funding, someone leaving, or work nobody can keep up with?
Why ask it
Each trigger makes for a different first quarter. New money means room to build, a departure means inheriting half-finished work, and overload means you are measured on the backlog before anything in the job description. When the answer is all three, ask which came first.
Who would I report to, and who would I work with most closely?
Why ask it
At a small company your manager may be a founder with many other reports, or someone managing for the first time, and either shapes the job more than the title does. Ask how often the two of you would meet and whether you will speak to that person before an offer. If the reporting line is undecided, ask who is deciding it and when.
What does a typical week look like for someone in this role?
Why ask it
Ask about last week in particular, since typical invites the tidy version. You are listening for the split between meetings, time working alone, customers and whatever was on fire. If the role is new and nobody can say, ask what the week looks like for whoever is covering the work now.
Which parts of the job description are settled, and which are a best guess?
Why ask it
Startup postings are often written before anyone knows what the work will turn out to be, and good interviewers admit it. You want to hear which two or three duties are certain. When every line is called flexible, ask what the role would be if you were only allowed to do one thing.
Would I be the first person in this role, or has it been tried before?
Why ask it
First means no predecessor to be compared with, and nobody who can tell you what good looks like. Tried before means there is a story, so ask what the company changed about the role afterwards. If nothing changed, the job that did not work for the last person is the one on offer.
Who decides what I would work on, and how often does that change mid-week?
Why ask it
Changes of plan in the middle of a week are normal at an early stage, so the part to pin down is who is allowed to make them. One person setting priorities is workable even when they move a lot. If several people can reassign you and nobody arbitrates, your energy goes on negotiating.
What could I decide on my own in this role, and what needs a founder to agree?
Why ask it
Ownership is the usual reason given for joining a startup, so test it with a concrete case: a vendor, a design choice, a price, a hire. Founders who still approve every detail are common early on. The useful follow-up is what they last handed over, and to whom.
What budget, tools or outside help comes with this role, and who approves the spending?
Why ask it
Responsibility without a budget is a familiar startup gap. Ask for the last thing this team wanted to buy and how long the yes took. Where every purchase waits on the chief executive, plan on doing a lot by hand.
How much of the job is building something new, and how much is keeping what exists running?
Why ask it
Interviews sell the building. Ask for last month's actual split from someone doing similar work, since maintenance, support and migrations seldom make it into the posting. Neither answer is bad, but it should match how you want to spend your days.
What happens in a new person's first month, and who do they learn from?
Why ask it
The good answer has a named person in it and something resembling a plan. Small companies often have no onboarding at all, which is survivable if they say so plainly and someone is assigned to you. Talk of being thrown in at the deep end tends to mean nobody has time.
Is there anyone senior in my field here to learn from, or would I be the whole department?
Why ask it
Being the whole function is a fast way to grow if you already know the job, and a lonely one if you were hoping to learn it from someone. If you would be alone, ask whether there is an adviser, an investor contact or a budget for outside help.
How does feedback reach people here: is there a review of any kind, or do you find out by asking?
Why ask it
Many early companies have no formal review, which is workable when a manager holds regular one-to-ones and says hard things early. Without either, the first clear feedback a person gets can be the conversation where they are let go. Ask when your interviewer last got feedback themselves.
Is there a levelling system here, or are titles agreed one person at a time?
Why ask it
A title costs a small company nothing, so it is sometimes offered where salary cannot be. Find out what yours would mean for pay and for who you report to, and whether it would hold if a more senior person were hired later. Where titles are agreed one by one, the one in your offer is open to discussion too.
If the company doubles in size, does this role become a team, stay as it is, or get a manager hired above it?
Why ask it
Early hires can be promised growth and then find a senior person brought in over them once there is money. An honest interviewer will say it depends on how you do, which is fair. Ask whether that has already happened to anyone here, and how that person took it.
What were you hired to do, and how close is that to what you do now?
Why ask it
Roles at a startup drift toward whatever nobody else is covering: recruiting, support tickets, one difficult customer, the integration that keeps falling over. The gap between their two answers is a fair forecast of your own. It also matters whether they chose the extra work or it landed on them.
What kind of person does badly here, however good they are at the job?
Why ask it
What comes back is the unwritten requirement. At a startup it tends to be about needing more structure, more certainty or more help than the company can give yet. If the description sounds like you on a tired day, take it seriously.
What are the next steps in the process, and who else would I meet?
Why ask it
Startups often settle the process as they go, so a clear answer with names and a date is a small sign of order. Ask who makes the final decision, and whether you will meet the people you would work with every day. If they want to move fast, say what you would need to see before deciding, such as the equity terms or a conversation with a future colleague.
The work
What is the team planning to build over the next six months, and who decided that?
Why ask it
A roadmap at a startup is a statement of intent, so listen more to how it was chosen than to the items on it: customer evidence, a founder's conviction or a promise made to close a deal. Ask which item was added most recently and what it pushed out. If your role is the one meant to build it, ask which part is yours and what it depends on.
Which parts of a normal week here would surprise someone coming from a big company?
Why ask it
Worth asking even if you are not that person, because the answer is a list of what is missing: no IT desk, nobody to hand a task to, a founder reading your draft before lunch, a customer who has your phone number. Ask which of those the last hire from a larger company found hardest.
What did the team ship most recently, and how long did it take from first idea to customers using it?
Why ask it
One real timeline is worth more than any claim about moving fast. Listen for where the weeks went: review, sign-off, waiting on a founder. That is the friction you will inherit, and people tend to describe it honestly because it annoys them too.
After something goes out, who checks whether customers used it?
Why ask it
With a small customer base there is rarely enough data for a chart to settle it, so the honest answer may be a person who rings three customers. That is fine. When nobody checks, work is judged by how much goes out, and the same arguments come back each quarter with nothing to settle them.
How far ahead is the work planned: a week, a quarter, a year?
Why ask it
No horizon is wrong, but it should fit the stage. A week at a time means priorities are set by whatever happened last, and a detailed annual plan at a company with nine months of money is decoration. Ask how much of the last plan survived.
How does everyone find out what the company's top priority is right now?
Why ask it
Whatever the channel, a weekly meeting or a pinned message, follow up by asking what the priority is. Then put the same question to your next interviewer. At a company small enough to fit in one room, two different answers mean the founders have not said it clearly or have not decided.
What was the last project dropped partway through, and who made that call?
Why ask it
Stopping work is healthy at a startup, and how it stops tells you a lot. A reason backed by evidence and explained to the people doing the work is a good sign. Work that simply faded when a founder lost interest will happen to your projects too.
What breaks most often, and who gets called when it does?
Why ask it
It need not be software: a supplier, a billing run or a weekly report can be the thing that falls over. If one person is always the one called, ask how long that has been true. Either you are about to share that load or you are about to rely on someone who is tired of carrying it.
What is the oldest problem everyone agrees should be fixed and nobody has had time for?
Why ask it
Most teams can name one straight away, and doing so is honesty, not disorder. Ask how long it has been on the list and what it costs each week. Then ask whether the new hire is expected to fix it, because that is sometimes the unadvertised job.
Who would look over my work before it goes out?
Why ask it
At a small company the answer may be nobody, which is freedom until the first mistake reaches a customer. If there is a reviewer, ask how long they usually take. If there is not, ask what happened the last time something went out wrong.
What gets written down here, and what lives in people's heads?
Why ask it
At ten people everyone can ask everyone, and writing feels like overhead. The cost shows up when you join and the only record of a decision is one person's memory. Ask where you would look to find out why something was built the way it was.
Where is everyone based, and when is the whole team expected to be reachable?
Why ask it
Get the real map: who is in an office, who is remote, and which time zones the founders keep. If decisions get made in a room you are not in, or the daily call lands at your dinner time, it is better to hear it now. Ask whether the arrangement has changed in the past year.
Honestly, what are the hours, and what happens during a crunch?
Why ask it
Hours in an ordinary week are the easy half. The crunch is where you learn how the place is run: whether it is planned, paid for and recovered from, or simply how every week goes. Ask when the last one was and how long it lasted.
When did you last take a full week off, and what happened to your work while you were away?
Why ask it
A leave policy says little at a small company, and an unlimited one says least of all. A date and the name of whoever covered is the good answer. If they laugh, or cannot remember, you have learned what the policy is in practice.
Pay and equity
What is the salary range for this role, and how was it set?
Why ask it
Whether a range is published depends on where the job is based, so you may have to ask. Startup salaries often sit below what a larger employer pays, with equity offered to make up the gap, and you can only judge that trade once you have both numbers. Ask how the range was arrived at: market data, what the last hire accepted, or what the budget allows.
How is pay reviewed here, and has anyone had a raise in the last year?
Why ask it
A small company may have no review cycle at all, and then pay tends to move only when someone is about to leave. The second half of the question is the test, because a policy can exist on paper while nobody has received an increase. A straight answer either way tells you how to plan.
Is any part of the pay a bonus or commission, and what did it actually pay out last year?
Why ask it
A bonus tied to company targets is only as reliable as the targets, and at a young company those are guesses. Ask what share was paid in each of the last two years and who sets the target. When you work out whether you can afford the job, count the base salary alone.
Is there a choice between more salary and more equity, and how do most people here choose?
Why ask it
Some startups offer two or three packages along that line, and some will if asked. How colleagues chose is the interesting part: people who know the company's numbers and still took the equity are telling you something. The right mix for you depends on what you can afford to earn if the shares come to nothing.
What percentage of the company would this grant be, counting every share and option already issued or set aside?
Why ask it
A share count means nothing without the total. Ask for the fully diluted figure, which includes options granted and reserved as well as shares issued, and divide your grant by it. A company that states the number of options and declines to give the total has left you unable to work out what is on offer. It is reasonable to wait for this until an offer is made.
Over how many years does the equity vest, and is there a cliff?
Why ask it
A common arrangement is vesting over several years with nothing owned until the end of the first, but terms vary by company and country, so get the actual schedule. Ask what happens to unvested equity if the company is sold, or if your role is cut shortly before the cliff. A longer schedule, or one weighted toward the later years, should be set against the size of the grant.
What is the strike price, and what did investors pay per share in the last round?
Why ask it
The strike price is what you pay to turn an option into a share, and the gap between it and the investors' price is a rough first guide to what the grant is worth on paper. Investors usually hold a different class of share with extra rights, so the two prices are not like for like. Ask when the strike price was last set and whether it is due to change before your grant is approved.
If I left the company, how long would I have to exercise my vested options?
Why ask it
Some plans give only a short period after leaving, sometimes a matter of months, and exercising means paying the strike price and possibly tax for shares you cannot yet sell. People stay in jobs they would otherwise leave for this reason. Some companies extend the period for longer-serving staff, so ask what the plan says and whether exceptions have been made.
How was the size of this grant decided: a band for the level, or case by case?
Why ask it
Bands mean the person hired next month at your level gets something comparable. Case by case means the number reflects how hard each person pushed, so push. Either way, ask where in the range your offer sits.
What type of equity is this, and when would I owe tax on it?
Why ask it
Options, restricted shares and other schemes are taxed at different moments, and the rules differ by country and sometimes by scheme. Ask how it works for employees where you live, and whether the company can point you to the adviser it relies on. A bill that arrives before any sale is the surprise to rule out.
Can you show me what my grant would be worth at a few different sale prices?
Why ask it
Asking for the worked example moves the conversation from share counts to money. A company comfortable with its terms will sketch a modest sale, a good one and a great one, after investors are paid. Reluctance to do the modest case is the thing to note.
Do people get further grants over time, or is the hiring grant the only one?
Why ask it
Without later grants your share of the company can only go down as new shares are issued, and once the first grant has vested there is nothing new to earn. Ask whether anyone has received a top-up and what for: promotion, tenure or a counter-offer. The last of those tells you how retention really works there.
How much would you expect my stake to shrink when the company raises again?
Why ask it
Dilution in each new round is normal, and a founder should be able to give a rough range from the rounds so far. You are checking that they treat it as a fact to explain, not a subject to avoid. Ask whether the option pool was topped up last time, since that comes out of existing holders too.
Has any employee been able to sell shares so far, and on what terms?
Why ask it
Until someone has, the equity is a number on a document. Some later-stage companies arrange sales to investors, and many early ones cannot or do not allow it. A plain no is fine: what you want to know is whether the only route to cash is an exit with no date on it.
Can I read the equity plan and the grant agreement before I sign?
Why ask it
The offer letter summarises, and the plan document rules. It is where you find what happens to your shares if you leave, are let go or the company is sold. A company that will not share it until after you start is asking you to accept terms unseen.
What benefits are in place today, and which are planned but not here yet?
Why ask it
Young companies add health cover, pension contributions and parental leave piece by piece, and what exists depends heavily on the country. Ask for the list as it will stand on your start date, not the one on the careers page. For anything you rely on that is still planned, ask for a date or a cash equivalent.
Has payroll ever been late, or has anyone been asked to defer pay?
Why ask it
It feels rude to ask and is not. It happens at companies short of cash, and those who lived through it remember. One late run with an explanation years ago is history, but a recent one, or a pause before the answer, should send you back to the runway question.
If the company had to let me go to save money, what would I leave with?
Why ask it
Notice, severance and how long you have to act on vested equity are set partly by local law and partly by the company, so ask how it works there. Many startups have no written policy, which is your cue to get the basics into the offer. It is a fair thing to price before taking the job, and a reasonable founder will treat it that way.
Founders and team
Why did the founders start this company, and what were they doing before?
Why ask it
Founders who worked in the industry, or had the problem themselves, tend to know the customers and where the difficulties are. Founders new to the field can still succeed, and then the thing to ask is who on the team brings that knowledge. Put the question to an employee as well: whether they tell the story the founders tell shows how well the mission has been passed on.
What made you join, and what has kept you here?
Why ask it
The first half gets you the pitch that worked on them, which is probably the one you are hearing now. The second half is the useful part: people who stay for their colleagues or the problem answer quickly, and people waiting for their equity to vest tend to pause. Ask it of everyone you meet and compare.
How would you describe the culture here, and what happened recently that shows it?
Why ask it
Asked on its own, culture gets adjectives: fast, open, collaborative. The second half is what makes the question work, because an example has to be about something that took place: a decision reversed, a mistake owned, someone told to go home and rest. If no example comes, the adjectives are an aspiration.
What did you give up to come here, and has it been worth it so far?
Why ask it
Many people who join a startup traded something for it: salary, a well-known employer, predictable hours. You hear what the trade was and whether it has paid off yet or is still a promise. Put it to a peer, and notice whether the answer is about the work or about the equity.
How long have the founders known each other, and had they worked together before this?
Why ask it
Founders who have already come through a hard stretch together have been tested. Those who met shortly before starting can work well too, so ask who has the final say when they disagree. With a solo founder, ask who tells them when they are wrong.
How often do you deal with the founders directly, and what is it usually about?
Why ask it
Ask a peer, not a founder. Daily contact about priorities is normal at a small company, while daily contact about the wording of an email is a founder who has not let go. No contact at all means there is a layer in between that you should meet.
What are the founders like when a deadline slips or a number comes in low?
Why ask it
Everyone is pleasant in an interview and in a good quarter. Ask for the last time it happened and what was said in the room. Blame aimed at one person, or a week of silence, will be the climate you work in, because missed numbers are routine at a startup.
When did a founder last change course because of something a person on the team said?
Why ask it
You are asking whether information travels upward. A named occasion, even a small one, means someone without the title can be right. When the only examples involve investors or customers, expect your own objections to be heard politely and left there.
Where does this team currently disagree with the founders?
Why ask it
A specific answer, even a mild one, means people can push back and keep their standing. A firm insistence that everyone is aligned is itself the answer, particularly if you hear it from several interviewers in identical words.
What are the founders not good at, and who covers for it?
Why ask it
Try it on someone who works for them, then ask a founder the same thing about themselves. Matching answers mean the gap is known and someone is covering it. A founder who can name no weakness, or a team that goes quiet, tells you the subject is not discussed.
When was bad news last shared with the whole company, and how was it delivered?
Why ask it
A lost customer, a failed raise, a senior departure: most startups have had one of these, so a team that cannot recall any is probably not being told. The good version is early, from a founder, with what happens next. Hearing it first from a colleague or from the press is the pattern to avoid.
Who here has worked at a startup before, and who is doing it for the first time?
Why ask it
A team of first-timers, founders included, will learn hiring, firing and fundraising on the job and on you. A few people who have seen a company grow or fail bring calm when things wobble. Neither mix rules a company out, but it tells you how much of the structure you may have to build yourself.
How many people have left in the past year, and what were their reasons?
Why ask it
At a company of twenty, three departures is a large share of the team, so ask for the number before the reasons. Some turnover is ordinary as a startup changes stage and the early generalists move on. Several people leaving the same team or the same manager is the pattern to ask about, as is any reluctance to answer at all.
Who joined most recently, and how has it gone for them?
Why ask it
The newest person is the best preview of your first months, and the answer shows whether anyone has been paying attention to them. See if you can speak to that person. They still remember what they were told in interviews and can say how it compared.
How are hiring decisions made, and has the team ever turned down someone a founder wanted?
Why ask it
Every hire changes a small company noticeably, so who gets a say matters. A team that has vetoed a founder's favourite has real influence over who joins. It also tells you how your own offer will be decided, and whether the people you met are choosing you or being informed.
Would you join again today, at the stage the company is at now?
Why ask it
This is not the same as asking whether they are glad they joined. Someone who came at ten people for a large grant may not think the terms on offer at fifty carry the same reward, and most will say so if asked plainly. A good follow-up is what would have to be in the offer for their answer to be yes.
What do new people here find out in their first month that they could have asked about in the interview?
Why ask it
A good last question, because by now the interviewer has heard what you did and did not ask. Expect something concrete: a customer contract up for renewal, a reorganisation, a person you should meet before deciding. Whatever they name, ask about it there and then.
Using these across interview rounds
Practical guidance for the conversation itself
Preparing
Match the group to the person
Ask a peer about The work, the hiring manager about The role, and keep the money questions in The business and most of Pay and equity for a founder, a finance lead or whoever makes the offer. A question put to someone who cannot answer it spends your slot and puts them on the spot. Founders and team works best on people who are not founders.
Ask the same question of two people
Where the answers diverge, on hours, on who decides priorities, on runway, on what the company's top priority is, is where the interesting conversation is. Pick two or three questions to repeat on purpose in different rounds.
Look up what is public first
Find the funding history and recent 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, such as whether the runway figure counts on sales that have not happened.
Keep three or four questions per round
Most rounds leave only a few minutes for your questions, and one question followed up twice beats four asked once. Lead with the one whose answer could end your interest.
Set your own numbers before you hear theirs
Before the first round, work out the lowest salary you can live on and the shortest runway you would accept. Answers about money are easy to explain away once you like the people, and a threshold you set in advance is harder to talk yourself out of.
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 are worth one follow-up question.
Compare the stories about one event
Pick something more than one interviewer will know about: the last funding round, a layoff, the role having been tried before. Consistent accounts mean a company that talks openly. Three different explanations for the same event mean most people were not 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 you would spend your first weeks explaining why you are there.
When they say they cannot share that
Early in a process some companies will not give runway or share figures, and that is reasonable before an offer. After an offer it is not: you cannot value equity without the share count, or judge the risk without the runway. Say you are happy to wait until the offer stage, then hold them to it.
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 the person you would report to 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 every hard question for the offer stage
By then the offer usually has a deadline on it, and there is little time to check an answer with anyone else. Hours, scope, who sets priorities and how pay is reviewed are all fair to ask during interviews. Runway and the equity terms can wait for the offer, but say early that you will be asking.
After the rounds
Write the contradictions down in one place
List each claim and who made it: hours, ownership, priority setting, runway. The contradictions are your real interview result, and they are the specific things to raise before you sign.
Talk to someone who is no longer there
A former employee has nothing to sell you. If you can reach one through your own contacts, ask what surprised them and what they would check if they were joining today. That gets further than asking why they left.
Decide what you would need in writing
Scope, title, reporting line, any promised review date and whatever was said about severance or further equity grants 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.
Get the equity paperwork read where it matters
How a grant is taxed and what happens to it when you leave depend on the country and the scheme, and nothing on this page is advice on either. If the equity is a real part of why you would take the job, an hour with an accountant or lawyer who handles employee equity where you live is worth having before you sign.