The questions you ask are part of the assessment
Almost every interview ends with some version of "do you have any questions for us," and how you answer it carries real weight. Good questions show that you have thought about the role, that you can reason about a business, and that you are evaluating the fit rather than just hoping to be chosen. Weak questions, or none at all, leave a flat final impression even after a strong conversation.
There are two jobs your questions do at once. They signal judgement to the interviewer, and they get you the information you need to decide whether to take the role if it is offered. The best questions do both. This guide gives you patterns rather than a script to memorise, because a question read off a list sounds exactly like a question read off a list.
Match the question to the person
A common mistake is asking everyone the same questions. Different interviewers can answer different things well, and tailoring shows you understand who you are talking to. Find out in advance who you will meet, recruiters will usually tell you, and aim a couple of questions at each person's actual vantage point.
The recruiter
Recruiters are best on process, logistics, and the shape of the role rather than deep technical detail. Use them for:
- What the rest of the process looks like and the rough timeline.
- How the team is structured and where this role sits in it.
- What they think makes someone successful in this role.
- Why the position is open.
The hiring manager
This is the person you would likely report to, and the most important conversation for understanding your day-to-day. Worthwhile directions:
- What the first ninety days would look like for whoever takes this role.
- How they would describe their management style and how they give feedback.
- What success at six months and a year would actually look like.
- What the biggest challenge facing the team is right now.
Peers and future teammates
Peer interviewers can tell you what the work really feels like, away from the official line. Ask about:
- What a normal week looks like, and what tends to eat the time.
- What they enjoy about the team and what they find frustrating.
- How decisions get made and how disagreements are resolved.
- What they wish they had known before they joined.
Senior leaders
If you meet a founder or a senior leader, they are best on direction and strategy. Aim higher:
- Where they see the biggest opportunity and the biggest risk over the next year.
- How this team's work connects to the company's priorities.
- How they think the company will change as it grows.
Make your research visible
The strongest questions grow directly out of homework you have done. If you used the product, read an engineering blog post, or noticed something in the news, turn it into a specific question. This is the kind of thing no generic candidate can produce, and it proves you did the work.
For example, rather than "what is the tech stack," which you could ask anyone, try something rooted in what you found:
I read your post about moving to a monorepo last year. How has that played out, and would you make the same call again?
Or, from using the product:
I tried the onboarding and the import step was smooth, but I noticed there is no undo on a bulk action. How does the team think about destructive operations like that?
Questions like these turn the end of an interview into a real conversation between future colleagues rather than a formality.
Questions that help you decide
Remember that you are also gathering information to make your own choice. Some of the most valuable questions are the ones that surface how the company actually operates, asked plainly and without an edge.
Useful areas to probe:
- How performance is measured and how growth and promotion work in practice.
- What the on-call or support expectations are, if relevant to the role.
- How the team handles work-life balance during crunch periods.
- Why the last person in this role left, or why a new role was created.
- What the company is genuinely working to improve right now.
Asking what a company is trying to improve is quietly revealing. A healthy organisation can name a real weakness and what it is doing about it. An answer that there are no problems at all tells you something too.
How to ask well
Delivery matters as much as content. A few habits keep your questions landing as curiosity rather than interrogation.
- Ask open questions that invite a real answer, not yes-or-no questions.
- Listen to the reply and follow up on it, rather than racing to your next prepared item.
- Keep two or three ready per interviewer and adapt to what the conversation has already covered.
- Read the time. If a session is running short, pick your best one or two questions rather than forcing all of them.
It is also fine, and often good, to ask a question that arose during the interview itself. "Earlier you mentioned the team is rebuilding the billing system. What is driving that?" shows you were paying attention.
What to avoid
A few patterns reliably weaken the impression. Asking only about salary, holidays, and perks before you have shown any interest in the work reads as transactional. Asking questions whose answers are plainly on the company website signals you did no preparation. And asking nothing at all suggests either disinterest or that you did not engage with the conversation. Save the detailed compensation and benefits discussion for the recruiter or the offer stage, where it belongs, and use your interview questions to understand the role and the team.
A small kit to carry in
For the recruiter: process, timeline, why the role is open
For the manager: first 90 days, success at 6-12 months, biggest challenge
For peers: a normal week, what they wish they had known
For leaders: biggest opportunity and risk in the next year
One question from your own research
One question raised live during the interview
Walk in with a kit like this, adapt it to the room, and the closing question becomes one of your strongest moments rather than an afterthought.
Continue your prep
Build the research that makes great questions possible: