Questions Not to Ask in an Interview: What to Ask Instead

The questions not to ask in an interview are the ones that only serve you and that a minute of research would answer: pay, holiday, hours, remote policy, when you can leave, and anything already stated in the job ad. Skip too the questions that put the interviewer on the spot about other candidates, their own performance or office gossip. Ask about the work, the team, how success is measured and what the first few months look like. Keep pay and benefits for the offer stage.

Why a question can cost you before it is answered

The interviewer hears two things at once: what you asked and what it suggests about your priorities. A pay question in minute five reads as "I am here for the money" even when your rent is the last thing on your mind. You cannot control that reading, but you can control the question.

Three tests catch most of the damage before you open your mouth.

Would the answer change what you do in the first six months? If not, the question belongs later, or with the recruiter.
Could you answer it yourself from the job ad, the company site or the recruiter's first email? If yes, asking it suggests you skimmed.
Does it ask the interviewer to reveal something they should not — other candidates, their own review, a colleague's history? If yes, drop it.

Worked example of the first test failing: "What are the hours?" The answer, whatever it is, will not change how you do the job in month one. The replacement, "What does a typical week look like for this team?", passes because the answer tells you how the work is paced and where the pressure sits, which does shape how you start.

Second test failing: "What does the company do?" The ad, the site and the recruiter's email all answer it. Replacement: "The ad mentions the migration project; what stage is it at?" That question can only come from someone who read the ad.

Third test failing: "Why is the last person leaving?" Even if you get an answer, you have asked the interviewer to discuss a colleague and signalled that other people's problems are your first interest. Replacement: "What would a strong first six months look like in this role?" Same curiosity about the ground you are stepping onto, none of the discomfort.

The questions not to ask in an interview because the ad answers them

The question	Why it lands badly	Ask this instead
"What does the company do?"	It is on the site and in the ad; the question says you did not look	"The ad mentions the migration project; what stage is it at?"
"What would I be doing?"	The responsibilities are listed; asking again suggests you skimmed	"Which of the listed responsibilities takes the most time in a normal week?"
"Is this role remote or hybrid?"	If the ad states it, you look careless; if it does not, the recruiter can answer by email	"How does the team split its time between office and home at the moment?"
"What are the hours?"	It sounds like clock-watching	"What does a typical week look like for this team?"
"Do you offer [benefit]?"	Benefits are the recruiter's or the offer's business, not the hiring manager's half hour	"What support does the team get for [the thing you actually care about]?"
"How much holiday do I get?"	It puts the exit before the entrance	Save it for the offer conversation
"When is the next pay review?"	Same problem, sharper	Save it for the offer conversation
"How much notice do people usually give?"	You are asking about leaving before you have arrived	Drop it
"How did I do?"	It corners the interviewer into a verdict they cannot give	"What are the next steps and the timeline?"
"What is the worst thing about working here?"	Asked cold, it reads as a trap and the answer is rarely useful	"What is the biggest constraint on the team right now — time, headcount or something else?"

Each replacement does one job: it moves the question from your needs to the work. That is the shift the interviewer notices, and it costs you nothing to make.

The questions that sound like you are already leaving

Holiday, pay reviews and notice periods are all reasonable things to want to know. They are the wrong questions for the first interview because they put the exit before the entrance. The offer conversation is the right room for them, and nobody finds them odd there.

If a date genuinely matters, say it as a fact rather than asking. "I have a week booked in August; I can start on the 12th" gives the interviewer what they need and shows you have thought about the handover.

The same logic applies to overtime. Asking about overtime pay in a first interview sounds like you are pricing your evenings before you have seen the work. Ask "How does the team handle crunch periods?" instead. You learn whether they exist, how often, and whether the team plans for them — which is what you actually wanted to know.

The questions that put the interviewer on the spot

Some questions are not rude so much as unanswerable. "Do you think I got the job?" asks for a verdict the interviewer cannot give honestly at that point, and it makes you look anxious. "How did I do?" has the same problem; ask about next steps instead, which is a fair question with a fair answer. There is a good way to do that without sounding nervous: asking about next steps without sounding anxious.

"What is your favourite thing about working here?" is fine and often gets a warm answer. "What is the worst thing about working here?", asked cold by someone they met twenty minutes ago, can read as a trap. If you want the honest version, ask about constraints: "What is the biggest constraint on the team right now — time, headcount or something else?" People answer that one candidly because it is about the work.

Anything about a named colleague's performance, salary or history is gossip. Drop it. It will be remembered long after the interview.

What to ask instead: three work questions that tend to land well

"What does success look like in the first six months?" — it gets at expectations and gives you material for your closing statement.
"Which part of the work slows the team down most at the moment?" — it shows you think about the work, not the perks.
"How does the team decide what to build next?" — it gets at process and culture without the vague "what is the culture like?"

The replacement rule: for every question you drop, write one about the work, the team or how success is measured. If you want a wider set to draw from, this guide to questions to ask in the closing minute covers the moment itself.

A hand holding a pen over a notepad with a short handwritten list and a check mark, next to a laptop on a desk

A worked sort: eight questions, five minutes left

You are in the final minutes of a first interview. The interviewer says, "Any questions for me?" You have eight questions on your page. Here is how they sort.

"What does success look like in the first six months?" — A, ask now. It is about the work and the answer is useful to you.
"What tends to slow the team down at the moment?" — A, ask now. It shows you are thinking about how the team operates.
"How does the team decide what to build next?" — A, ask now. Process and culture in one question.
"What is the salary range?" — B, recruiter. Legitimate, but not in this room.
"How much holiday is there?" — B, recruiter. Same.
"Is the role hybrid?" — B, recruiter. The ad may already say; if not, email before the interview.
"Why is the last person leaving?" — C, drop. It puts the interviewer on the spot about a colleague.
"How did I do?" — C, drop. Ask about next steps instead.

With five minutes, ask the three A questions in order and stop. Three thoughtful questions land better than eight, and the last thing the interviewer hears is you talking about the work.

If the interviewer raises pay first, answer with a range and a question back rather than a question about their budget. "Based on what the role involves, I would be looking at a range once I understand the full scope of the role; is that in line with the band you have in mind?" That keeps the conversation moving without turning it into a negotiation before you have an offer.

Deferring a pay question to the recruiter

If pay comes up and you would rather not fix a number in the room, use a short script and mean it:

"I am glad to talk about pay. I would rather do it properly with the recruiter or at the offer stage, once we both know the role is a good fit. Could we come back to it then?"

The sentence is not evasive because it names what will happen and when. It also keeps the interview focused on the work, which is where you are strongest. If the interviewer pushes for a number, give a range and ask how it sits against the band for the role.

Edit your list the night before: a five-minute sort

Copy this and work through it the evening before the interview.

Write every question you have on one page, in any order.
Mark each one A (ask now), B (recruiter or offer stage) or C (drop).
Aim for three A questions and no more than two B questions. If you have more than five A questions, cut the weakest.
Say each A question once, quietly. If it sounds like an accusation or a complaint, rewrite it as a question about the work.
Check each A question against the three tests at the top of this page.
Put the B questions somewhere you will find them: notes on your phone, or an email to the recruiter after the interview.

One decision rule covers the rest: if you would not be comfortable hearing the question asked back to you, do not ask it.

If you need to ask for adjustments to the interview itself, that is a different conversation with its own wording: how to ask for interview accommodations.

The one rule to take into the room

If a question is about what you get, save it for the recruiter or the offer. If it is about the work, the team or how success is measured, ask it now. That single split handles almost every case on this page, and it means you never have to memorise a list. Write your three work questions the night before, say them once, and let the rest wait for the right room.

Frequently asked questions

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

Not rude, but usually mistimed. Hiring managers often cannot discuss the band, and raising pay early shifts the conversation from the work to the package. If the recruiter asks for your expectations first, give a range and ask how it compares with the band. Otherwise, let the recruiter or the offer conversation carry it.

What if the interviewer invites me to ask anything at all?

Take the invitation at face value but stay on the work. "Anything at all" is an opening, not a licence to ask about holiday or other candidates. Pick your strongest work question first, then a second if there is time. If you genuinely have nothing left, ask about next steps and the timeline.

Should I ask about remote work if the ad does not mention it?

Ask the recruiter by email before the interview, not the hiring manager in the room. That gets you a clear answer early and keeps the interview for questions about the work. If the topic comes up naturally, ask how the team currently splits its time between office and home rather than whether the role is remote.

What if I have no questions left after filtering my list?

Use one of the three work questions from this article: what success looks like in the first six months, which part of the work slows the team down most, or how the team decides what to build next. Any of them works in almost any role. Having one ready matters more than having many.

Can I ask the same question to different interviewers on a panel?

Yes, and it can be useful. Different people often give different answers about the same team, and the gaps tell you something. Just vary the wording slightly so it does not sound rehearsed, and do not ask the same person the same question twice.

Preparing your question list? See how AI Interview assistant works.