How many questions should I ask at the end of an interview?

Two or three is usually right. Prepare four or five so you can drop the ones already answered. A panel may give you one question each; keep each one short and directed at the relevant person.

Is it bad to ask about salary in the first interview?

It depends on the stage and who is asking. In a recruiter screen, asking for the range is normal and saves time. With a hiring manager before the role has been discussed, it can narrow the conversation too early. Ask about the range, not your negotiating position.

What if I blank when they ask “any questions?”

Use a safe, specific fallback: “What would success look like in the first six months?” Then follow up on the answer. Keep one fallback in mind so you are not inventing a question under pressure.

Should I ask the same questions to every interviewer?

No. Match the question to the person’s perspective. The recruiter knows the process, the manager knows the outcomes, and the peer knows the daily work.

What questions should I not ask?

Avoid anything answered clearly on the website, questions that invite the interviewer to list your weaknesses, and questions that signal you are already thinking about leaving. Ask about the work, the team and the next step first.

Can I ask about remote or hybrid work?

Yes, but frame it around how the team works rather than what you can avoid: “How does the team split time between office and remote, and what happens on the days people are in?”

QUESTIONS TO ASK

Questions to ask the interviewer

Updated 2026-11-03 · 7 min read

The last five minutes are not a formality. Your questions show whether you listened, whether you understand the role, and whether you are choosing the job as much as they are choosing you.

Why the last five minutes matter

Interviewers remember the end of a conversation disproportionately. A candidate who asks a sharp question about the work sounds engaged; a candidate who asks about holiday allowance before the role has been discussed sounds like they are negotiating a job they do not understand yet. The goal is not to collect answers. It is to show that you can listen, prioritise and turn information into a useful question.

You are also gathering evidence. An interview is a two-way decision, and vague answers about the team, the manager or the definition of success are useful data. Ask the question, then listen for specifics: names, numbers, recent examples, and what happens when the answer is “it depends”.

How to choose three questions

One about outcomes. What does good look like in the first six months, and how is it measured? This tells you whether the role is designed or improvised.
One about the team. How does the team make decisions, and where does work get stuck? This tells you whether the job description matches the operating reality.
One about the process. What happens next, and is there anything you would like me to clarify? This gives you a clean close and a chance to address a concern.

If the interviewer has already covered one of your questions, say so and ask for the next layer: “You mentioned the migration is the priority this quarter — what is the part most likely to slip?” That is better than repeating a question they just answered.

Match the question to the interviewer

Interviewer	A good question	What the answer tells you
Recruiter or phone screen	What are the two or three things the hiring manager is most worried about getting wrong?	Whether the role is clearly scoped and whether the recruiter knows the team
Hiring manager	What would you want the person in this role to have changed by the end of month six?	Whether the manager has a definition of success or only a list of tasks
Peer or team member	Where does this team lose the most time today?	The real workflow, tooling and friction the job description leaves out
Skip-level or department head	What decision is the team waiting on that this role could help unblock?	How the role connects to the wider business, and whether it has sponsorship
Panel	Which of these priorities would you trade off first if the timeline slips?	Whether the panel agrees on priorities; watch who answers and who defers
HR or people team	How is performance reviewed in the first year, and what does the process look like?	Whether feedback is continuous or only annual, and whether the process is clear

Role and success questions

What does a strong first six months look like, and who judges it?
Which outcome matters most in the first 90 days?
What would make you say this hire was a mistake at the one-year mark?
Which parts of the job description are aspirational rather than immediate?
What is the hardest decision this role will have to make in the next quarter?
How much of the role is inherited work versus new work?
What does the team do today that this role is meant to stop doing?
If I started on Monday, what would you want me to have learned by Friday?

Team and manager questions

How does the team make decisions when there is no clear owner?
What is the manager’s default feedback style: written, verbal, scheduled or ad hoc?
Where does work get stuck most often: prioritisation, review, dependencies or headcount?
How does the team handle disagreement in a meeting?
What is the team’s meeting rhythm, and which meeting would you protect?
Who are the closest collaborators outside the team, and how well does that relationship work?
What happened to the last person in this role?
How do you onboard someone who has the skills but not the domain context?

Business and strategy questions

What is the team’s biggest constraint this year: demand, capacity, regulation or budget?
Which competitor or substitute are you most worried about, and why?
What assumption in the current plan is most likely to be wrong?
How does this team’s work show up in the company’s revenue or mission?
What has changed in the last six months that made this role necessary now?
If the budget were cut by 20%, what would you protect first?

Questions to ask at the end of an interview

What are the next steps, and when should I expect to hear?
Is there anything in my background you would like me to clarify?
What is the expected start date, and what would need to happen before it?
How does the team document decisions and handovers?
What does “urgent” mean here, and who gets to declare it?
How do you handle on-call, overtime or last-minute client requests in this role?

Growth and development questions

What does growth look like from this role: deeper expertise, wider scope or people management?
What learning budget or time is available, and how do people actually use it?
Who in the company has done this job well, and what did they do differently?
What is the next role after this one, and is it usually filled internally?
What feedback have people in this role received most often?

Internship interview questions

What does a successful internship look like by the final week?
Will I own a project, or support someone else’s?
How much structure and supervision should I expect in the first month?
Is there a conversion path to a graduate role, and how are decisions made?

Questions to ask a software engineer interviewer

Who reviews code, and what does a good review comment look like here?
How do you decide when to refactor versus ship?
What is the on-call rotation, and what happened on the last incident?
Where does technical debt slow the team down most?
How are technical decisions documented and revisited?

Questions to avoid, and what to ask instead

Avoid	Why it backfires	Ask instead
“What does the company do?”	It signals you did not read the website.	“I saw the launch of X — how does this team’s work connect to it?”
“What is the salary and holiday allowance?”	Too early if the role and expectations have not been discussed; it can frame you as transactional.	“What is the range for the role, and how is the final offer decided?” (ask the recruiter, later in the process)
“Is there a lot of work?”	Sounds like an avoidance question.	“How does the team handle peak periods, and what is expected of this role then?”
“Do you have any concerns about me?”	Invites objections before you have heard the priorities; can end the interview on a defensive note.	“Is there anything you would like me to clarify before we finish?”
Questions answered on the careers page	Wastes your turn and shows you did not prepare.	Ask for the specific experience behind the policy: “How does that flexibility work in practice for this team?”
A list of ten questions	Turns a conversation into an interrogation and eats the interviewer’s time.	Three good questions, plus one follow-up.

How to follow up on an answer

A follow-up is what separates a prepared candidate from a scripted one. Use one of four prompts: “What does that look like in practice?”, “What would have to be true for that to work?”, “What happened the last time it did not?”, or “Who else is involved in that decision?”. Then stop talking. The interviewer’s answer is the point.

Illustrative follow-up

Interviewer: “We are still figuring out the roadmap.” You: “What is driving the uncertainty — customer demand, capacity, or a decision that has not been made yet?” This is specific, non-judgmental, and gives you a real answer about the team’s stage.

Panel interviews

In a panel, direct each question to one person and make it relevant to their role. Ask the hiring manager about outcomes, the peer about the workflow, and the skip-level about strategy. Do not ask the same question to the whole panel; it wastes the format and makes you look unprepared. If the panel disagrees, do not try to resolve it for them. Ask a neutral follow-up: “It sounds like there are two views on the priority. How will that be decided?”

After the interview

Write down the answers while they are fresh: the definition of success, the biggest constraint, the next step and any concern you need to address.
Send a short thank-you note that references one specific thing you discussed, not a generic paragraph.
If you were told a decision date, wait until then before following up. If the date passes, send one concise email.
Use the answers to decide whether you want the job, not just whether you can do it.

These guides are written and maintained by MockInterview as original practice material. They are not leaked employer questions, and no employer has reviewed or endorsed them. Sample answers are illustrative; use your own examples and verify role requirements, licensing and local policy with the employer. Last updated 2026-11-03.