Killer Questions to Ask at the End of an Interview (18 Examples)

Last updated: August 2026

Quick Answer

A killer closing question does two jobs at once: it shows you think like someone already doing the role, and it extracts information you cannot get from the job posting. The best ones ask about how success is measured, why the role is open, what the last person struggled with, and what the interviewer would change. Ask three to five, listen to how the answer is delivered as much as what it says, then rehearse your delivery in OphyAI Interview Practice so the questions land as curiosity rather than a checklist.

#	Question	What it reveals
1	What does success look like in this role at 90 days and at one year?	Whether expectations are defined or vague
2	Why is this role open right now?	Growth, backfill, or a churn problem
3	What did the person who was most successful in this role do differently?	The real, unwritten performance bar
4	What is the hardest part of this job that is not in the description?	The friction you would inherit
5	How does this team make decisions when people disagree?	Whether the culture is functional under pressure
6	What would you change about this team if you could?	Candor, and the interviewer’s own frustrations
7	How is performance actually reviewed and rewarded here?	Whether promotion is a process or a favour
8	What is the biggest risk to this team hitting its goals next year?	Business health and strategic clarity
9	How much of this role is building versus maintaining?	Whether the work matches what you want
10	What is your own experience been like here, honestly?	The unscripted answer, if you have earned it

The Questions, With What Each One Reveals

Each question below includes why it works, what a strong answer sounds like, and what a weak answer should tell you. Pick three to five that match what you genuinely need to know, and never ask a question whose answer is on the careers page.

1. “What does success look like in this role at 90 days, and at one year?”

Why it works. It reframes you from candidate to hire. It also forces the interviewer to be concrete about expectations, which is the single most useful piece of information you can leave an interview with.

A strong answer sounds like: a specific, sequenced picture. “In 90 days you own the reporting pipeline and have shipped one improvement to it. By a year, you are setting the roadmap for that area and mentoring the junior analyst.”

A weak answer tells you: if you get “just get up to speed and be a team player,” the role is undefined. Undefined roles are where good people get quietly judged against a bar nobody told them about.

2. “Why is this role open right now?”

Why it works. It surfaces the story behind the requisition. There is a large difference between a role created by growth, a backfill after a promotion, and a backfill after someone burned out.

A strong answer sounds like: a direct, unembarrassed explanation. “We split one overloaded role into two,” or “Priya moved into a staff role and we need to cover her old scope.”

A weak answer tells you: hesitation, vagueness, or “there has been some turnover” is worth a gentle follow-up. Ask how long the previous person was in the seat.

3. “What did the person who has been most successful in this role do differently from everyone else?”

Why it works. Job descriptions list requirements. This question gets you the actual performance bar, which is usually a behaviour rather than a skill.

A strong answer sounds like: a specific trait tied to an example. “She spent her first month talking to the field teams instead of touching the code, and every project after that landed better.”

A weak answer tells you: if the interviewer cannot name what distinguishes a top performer, the team may not have a clear standard, which makes reviews unpredictable.

4. “What is the hardest part of this job that would not be obvious from the job description?”

Why it works. Every role has friction: legacy systems, a difficult stakeholder, a reporting line that does not quite work. Asking directly signals you are evaluating the job seriously rather than just trying to get an offer.

A strong answer sounds like: honest specificity. “The data is messier than you would expect and you will spend real time on cleanup,” or “You will need to influence a team that does not report to us.”

A weak answer tells you: “Honestly, nothing, it is a great job” is a missed opportunity for them and a small red flag for you. Every job has a hard part.

5. “How does this team handle disagreement when two people are confident and wrong in opposite directions?”

Why it works. Culture questions usually get culture answers. This one gets a mechanism, because you asked about a specific situation rather than about values.

A strong answer sounds like: a described process. “We write it up, we disagree in the doc, and the tech lead calls it if we are still stuck after a week.”

A weak answer tells you: “We are all pretty aligned” often means disagreement is suppressed or decided by whoever has the most political capital.

6. “If you could change one thing about how this team works, what would it be?”

Why it works. It invites candor and gives you a read on psychological safety. An interviewer who can name a real problem in front of a stranger works somewhere that tolerates honesty.

A strong answer sounds like: a genuine, bounded complaint. “Our planning cycle is too long, and we are trying to fix it.”

A weak answer tells you: a defensive non-answer suggests either a rehearsed culture or an interviewer who does not feel safe being candid.

7. “How is performance reviewed here, and what actually drives promotion?”

Why it works. Compensation conversations happen later, but the promotion mechanism is a fair question now and it is where a lot of dissatisfaction originates.

A strong answer sounds like: a described system with a cadence. “Twice yearly, against a published levelling guide, with your manager plus peer feedback.”

A weak answer tells you: if promotion sounds like it depends on visibility to a specific executive, factor that into your decision.

8. “What is the biggest risk to this team hitting its goals in the next year?”

Why it works. It is a strategic question that most candidates do not ask, and it tells you whether the interviewer understands their own business context.

A strong answer sounds like: a real constraint named plainly. “Our biggest customer is up for renewal and half the roadmap is shaped around that.”

A weak answer tells you: an interviewer with no view on this is either junior to the strategy or working somewhere without clear direction.

9. “How much of this role is building something new versus maintaining what exists?”

Why it works. This is the question that most often prevents a bad match. Many people accept a role imagining greenfield work and inherit a maintenance queue.

A strong answer sounds like: an honest ratio. “Realistically 70 percent maintenance in year one, and the new platform work starts after that migration lands.”

A weak answer tells you: if the split keeps shifting during the conversation, ask for a concrete example of what the last quarter looked like.

10. “Who would I work with most closely, and what do they need from this role?”

Why it works. It shows you think in terms of collaborators and dependencies rather than tasks, which is how the role will actually feel day to day.

A strong answer sounds like: named roles and specific needs. “Mostly the two product managers; what they need is someone who can push back on scope with data.”

A weak answer tells you: vagueness here may mean the role’s place in the organisation has not been thought through.

11. “What is the team’s approach to work that fails or gets cancelled?”

Why it works. Every team ships things that do not work. How they treat that reveals more about the culture than any values statement.

A strong answer sounds like: a normalised process. “We run a blameless retro, write it down, and move on. Two projects were cancelled last year and nobody was punished for it.”

A weak answer tells you: if failure is not discussed openly, expect risk aversion and a reluctance to surface problems early.

12. “How has this team changed in the last year, and where is it heading?”

Why it works. It gets you the trajectory. A team that has doubled and a team that has halved present very differently in an interview but feel completely different to join.

A strong answer sounds like: a clear arc with a reason. “We went from four to nine after the funding round, and the next hire is a designer.”

A weak answer tells you: significant unexplained churn deserves a polite follow-up about retention.

13. “What does support for someone new look like in practice here?”

Why it works. Onboarding quality is a strong proxy for how much the organisation invests in its people, and it is directly relevant to whether you will succeed.

A strong answer sounds like: something concrete. “You get a buddy, a 30-60-90 plan, and your first ticket is deliberately small.”

A weak answer tells you: “You will pick it up as you go” means you are expected to be self-sufficient immediately. That is workable if you know it in advance.

14. “What is something the company gets wrong that you wish it did better?”

Why it works. A more pointed variant of question 6, aimed at the organisation rather than the team. Use it in later rounds, with a senior interviewer, once rapport exists.

A strong answer sounds like: self-aware honesty. “Communication across offices is genuinely poor and we know it.”

A weak answer tells you: deflection to a strength (“we care too much”) is a rehearsed non-answer.

15. “What would make you decide, six months from now, that hiring me was a great decision?”

Why it works. It is the closing question that most directly translates to a plan you can act on if you take the job. It also leaves the interviewer picturing you in the role.

A strong answer sounds like: a specific outcome. “You have taken the on-call burden off the two senior engineers and they are back on roadmap work.”

A weak answer tells you: if they cannot answer, the hiring case may not be well formed, which often means shifting expectations later.

16. “How does this team work with the rest of the organisation, and where does friction usually show up?”

Why it works. Cross-functional friction is where most of the frustration in a job lives, and it rarely appears in a job description.

A strong answer sounds like: an acknowledged seam. “Handoffs to the compliance team are the slowest part of anything we ship.”

A weak answer tells you: claiming zero friction with other teams is not credible in any organisation above a certain size.

17. “What are the next steps, and when should I expect to hear from you?”

Why it works. It is the practical close. It sets a clear expectation and gives you a legitimate reason to follow up if the date passes.

A strong answer sounds like: a specific date and stage. “Two more rounds; the recruiter will reach out by Thursday.”

A weak answer tells you: a vague timeline is common and is not a red flag on its own, but note the date they give you and use it. See our guide to following up after an interview.

18. “Is there anything about my background that gives you hesitation?”

Why it works. It is the highest-risk and highest-reward question on this list. Asked with genuine composure, it gives you one last chance to address an objection that would otherwise sink you silently after you leave.

A strong answer sounds like: a real concern you can then answer. “You have not managed a team this size before” gives you an opening to address it directly.

A weak answer tells you: “No concerns at all” costs you nothing. Only ask this if you can hear a criticism without becoming defensive, because the recovery is the part being evaluated.

Which Questions to Ask, and When

Not every question fits every round. Match the question to who is in front of you.

Interviewer	Best questions	Avoid
Recruiter	2, 12, 17	Deep technical or team-dynamics questions
Hiring manager	1, 3, 4, 9, 15, 18	Questions they cannot answer about other teams
Peer or team member	5, 6, 10, 11, 13, 16	Compensation and promotion mechanics
Skip-level or executive	8, 12, 14	Day-to-day operational detail

Ask three to five, not ten. A closing that turns into an interrogation shifts the tone of the conversation. Prioritise the ones whose answers would actually change your decision, and be genuinely prepared to hear something that puts you off the role.

How to Practice These

The questions are the easy part. The delivery is what separates a candidate who sounds curious from one who sounds like they memorised a list. Two things help: knowing your three questions well enough that you do not read them, and being ready to ask a natural follow-up when an answer opens something up.

Run a full mock round in OphyAI Interview Practice and use the closing minutes to practise asking your questions out loud, including the follow-up. The transcript and per-answer feedback show you where you sounded rehearsed. For live rounds, OphyAI Interview Copilot keeps your structure visible on Zoom, Teams, or Meet so you do not lose your closing questions when the conversation runs long.

Start practicing →

Frequently Asked Questions

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

Three to five is the right range for most interviews. Fewer than two suggests low interest or poor preparation; more than five turns the closing into an interrogation and often runs past the scheduled time. Prepare six or seven so that you have replacements ready when some get answered during the conversation itself, then ask the three whose answers would genuinely affect your decision about the role.

What questions should I never ask at the end of an interview?

Avoid anything answered on the careers page or in the job description, since asking signals you did not prepare. Hold compensation, benefits, holiday, and remote-work policy for the recruiter or the offer stage rather than raising them with a peer interviewer. Do not ask “did I get the job” or anything that pressures for an immediate decision, and avoid questions that criticise the company or a competitor, which read as combative rather than curious.

Is it a bad sign if the interviewer cannot answer my question?

Not necessarily, and the reason matters more than the fact. An interviewer who is genuinely outside their area (a peer engineer asked about promotion committees, for example) is a normal limit and a good one will offer to find out. What is worth noting is when a hiring manager cannot describe what success looks like in the role they are hiring for, or cannot say why the position is open. Those are core to their own hiring case, and vagueness there often predicts unclear expectations later.

Should I ask about salary at the end of the interview?

Generally no, not with a hiring manager or a peer interviewer. Compensation is a recruiter conversation, and it usually belongs at the screening stage (to confirm the range is workable before you invest hours) or at the offer stage. Raising it in the middle of a technical or team interview shifts the tone unhelpfully. If a recruiter asks your expectations early, give a researched range rather than a single number. See our salary negotiation guide for how to handle the conversation when it arrives.

Can I write my questions down and read them?

Bringing notes is fine and generally reads as prepared rather than unprepared, in person and on video alike. Glancing at a short list to check what you still wanted to ask is normal. Reading questions verbatim off a page is what damages the impression, because it removes the conversational quality that makes these questions work. Know your top three well enough to ask them from memory, and keep the rest as a written backstop.

What if all my questions get answered during the interview?

Say so, briefly and specifically, then ask something new. “You covered most of what I planned to ask, particularly around the roadmap, so let me ask something different” shows you were listening rather than waiting for your turn. Keep one or two questions in reserve that rarely get answered spontaneously, such as what the most successful person in the role did differently, or what the interviewer would change about how the team works.

Do these questions matter for the hiring decision?

Yes, more than most candidates expect. Many interviewers explicitly score the closing questions as a signal of preparation, engagement, and seniority, and in close calls between two candidates the quality of the questions is a common tiebreaker. The questions also change the impression of you generally: asking what success looks like at one year makes the interviewer picture you in the seat, which is a meaningful advantage at the point where they write up their feedback.

Related Guides

These closing questions map directly onto the interview processes covered in our company guides:

• Amazon interview guide
• Google interview guide
• Microsoft interview guide
• Revolut interview guide
• Stripe interview guide
• Deloitte interview guide

For a broader list of closing questions, see questions to ask the interviewer. For questions designed to make you memorable rather than to gather information, see unique interview questions to ask an employer.

Sources and verification notes

Last reviewed August 2026. This guide is editorial advice built from patterns in hiring practice rather than a report of any single employer’s policy. The questions and the readings of typical answers are general guidance: no employer publishes a scoring rubric for candidate questions, so treat “what a weak answer tells you” as a prompt for your own judgement rather than a diagnostic rule. Nothing here is a prediction about how any specific interviewer will respond.

• US Bureau of Labor Statistics, Job Openings and Labor Turnover Survey: official US data on hires, quits, and openings, useful background on turnover when you are weighing why a role is open.
• Society for Human Resource Management (SHRM): HR practitioner guidance on structured interviewing and onboarding practice, the professional-body view of the processes these questions probe.
• Harvard Business Review, on hiring and interviewing: management research and practitioner writing on interview effectiveness and candidate evaluation.