To end an interview strong, use the last five minutes for four things: ask one or two sharp questions, ask whether anything about your background gives the interviewer pause and address it, give a 30-second closing statement that links your best evidence to the role's top need, and confirm the next steps. Then thank them by name and finish on time.
The close won't rescue an interview that went badly, and a weak close rarely sinks a strong one. What it can do is fix a gap the interviewer is still unsure about and leave them with a clear, one-line summary of why you fit. That matters because many interviewers write their notes or scorecard soon after you leave, and the last thing you said is fresh when they do. This guide gives you the sequence, the closing statement formula, the exact wording for the concerns question, and four closing examples we wrote.
What should you say at the end of an interview?
Most interviews end with "Do you have any questions for me?" Treat that as the start of your close, not the end of the interview. Here is the sequence, in order, for a typical five-minute window.
| Step | Time | What you say | Why it works |
|---|---|---|---|
| 1. One or two real questions | 2 min | A question about the team's priorities or how success is measured | Shows you're already thinking about the job, not just the offer |
| 2. The concerns question | 1 min | "Is there anything in my background that gives you pause for this role?" | Brings a hidden doubt into the open while you can still answer it |
| 3. Closing statement | 30–45 sec | Their top need, your proof, your interest | Gives the interviewer a clean summary to write down |
| 4. Next steps | 30 sec | "What are the next steps, and when should I expect to hear?" | Sets expectations so you know when to follow up |
| 5. Thanks and exit | 15 sec | Thank them by name; mention one thing you enjoyed discussing | Ends warmly and on time |
If the interviewer runs over and you only have a minute, skip straight to steps 3 and 4. A short closing statement and a clear next step are worth more than a rushed question.
The closing statement formula
A closing statement is a 30–45 second summary, roughly 80–110 words, that you deliver after your questions. It answers the question every interviewer has to answer on their scorecard: why this person, for this role? Use this formula:
- Thank them for something specific. "Thanks for walking me through the migration roadmap."
- Name the role's top need in their words. Repeat a priority the interviewer mentioned, such as "you need someone who can own reliability for the payments service."
- Give one or two proof points. Pick the results from your experience that match that need most closely, with a number if you have one.
- State your interest plainly. "This is the kind of problem I want to spend the next few years on."
- Look forward. "I'd be glad to go deeper on any of this in the next round."
Prepare the proof points before the interview, but write the first two parts in the room, based on what you heard. A closing statement that repeats your résumé summary sounds rehearsed; one that uses the interviewer's own words sounds like you listened. If you tend to run long, our guide on how to stop rambling in interviews has a timing drill that works well for closes. The statement overlaps with "why should we hire you?", so the evidence you prepared for that question is a good starting point.
How do you ask if there are any concerns about your candidacy?
Asking about concerns is the most useful closing move, and the one most candidates skip. The interviewer may already have a doubt, such as limited experience with a tool, a short tenure or a gap in your résumé. If you never hear it, you can't answer it.
Pick wording that feels natural to you:
- "Is there anything in my background that gives you pause for this role?"
- "Based on our conversation, is there an area where you'd like more evidence from me?"
- "Is there anything I said today that I could clarify?"
When they name a concern, use a three-part reply: acknowledge it, give evidence, and check. Keep it under a minute. Don't argue, and don't over-explain.
Example exchange we wrote:
- Interviewer: "The one thing I'm unsure about is that you haven't managed people directly."
- You: "That's fair. I haven't had direct reports. For the last year I led a four-person project team on our billing rewrite: I ran the planning, set the review standards and onboarded two new engineers, who were both shipping on their own within six weeks. Does that address what you'd need from someone in this role, or is there a part of people management you'd want to see more of?"
Some interviewers won't share concerns. In structured interviews, the interviewer may be told not to give feedback, and some companies have a policy against it. If you hear "Nothing comes to mind" or "I can't share that," say "Thanks, that's helpful" and move on. The question still shows you're open to feedback.
Final questions and next steps
Ask one or two questions before you close. The best final questions point at the work itself and give you information you can use in your closing statement:
- "What would make someone successful in this role in the first six months?"
- "What is the biggest challenge the team is working on right now?"
- "How does this role work with product and design day to day?"
For a longer list, see our questions to ask the interviewer, and the questions to ask a hiring manager for the manager round in particular. Avoid questions about salary, vacation or remote days in a first-round close unless the interviewer brings them up; the recruiter is usually the right person for those.
Then confirm next steps: "What are the next steps in the process, and when would you expect to make a decision?" If they give a date, write it down. If you have other offers or deadlines, this is the moment to mention them briefly and politely. Send a short thank-you email after the interview, ideally the same day, and reuse one line from your closing statement in it.
On a video call, let the interviewer end the meeting rather than leaving first. In person, stand when they stand, shake hands if that's the norm, and thank anyone who escorted you out.
4 closing examples we wrote
Each of these is an example we wrote, about 30–45 seconds when spoken. Use the structure, not the words.
1. Software engineer, hiring manager round
"Thanks for explaining how the team is splitting the monolith. It sounds like you need someone who can move services out without breaking the checkout flow. At my current company I led the extraction of our notifications service: we moved 40 million messages a month to the new service with no customer-facing incidents, and cut deploy time from an hour to twelve minutes. That's the work I enjoy most, and I'd be excited to do it here. What are the next steps on your side?"
2. Product manager, final round
"I appreciate you sharing the retention numbers. What I heard is that activation in the first week is the problem to solve this year. In my last role I owned onboarding for a B2B analytics product, and we raised week-one activation from 31% to 44% over two quarters by cutting setup steps and adding a guided first report. I'd love to bring that approach here. Is there anything you'd want to see more evidence of before the next step?"
3. Career changer or new graduate
"Thank you for the time today. You mentioned the team needs someone who learns fast and communicates clearly with clients. I'm new to analytics as a full-time job, but in my capstone project I built a churn model for a local gym chain and presented the findings to their owners, who changed their renewal offer based on it. I'm keen to keep building those skills on a team like yours, and I'd welcome the chance to continue."
4. After a round that felt shaky
"Before we finish, I want to come back to the caching question. I rushed my answer: the approach I'd take is a write-through cache with a short expiry, because the data changes often and stale prices would cost you money. I wanted you to have that clearer version. Thanks for a challenging conversation; I'm still very interested in the role. What are the next steps?"
The fourth example is a recovery close. Use it once, briefly, and only for an answer you can now improve in a sentence or two. If a whole round went badly, our guide on how to recover from a bad interview answer covers what to do next.
Closing mistakes to avoid
- Saying "No, I think you covered everything." It ends the conversation on a flat note. Have at least one question ready.
- Asking "So, did I get the job?" It puts the interviewer in an awkward position. Ask about next steps and concerns instead.
- Repeating your whole résumé. A closing statement is one need and one or two proof points, not a career summary.
- Running over. If the interviewer has another meeting, a close that eats into it works against you. Watch the clock and shorten.
- Getting defensive about a concern. Acknowledge, give evidence, check. Don't argue with the doubt.
- Sounding unsure. Phrases like "I hope I did okay" weaken an otherwise solid finish. State your interest and stop.
Strong closes are one part of what interviewers notice. For the full picture of how managers read the round, see what hiring managers look for in an interview, the hub on what a hiring manager interview is, and signs a hiring manager wants to hire you. If the manager asks how you'd approach your first months, a short 30-60-90 day plan makes a strong closing reference.
Practice it
A close only sounds natural if you have said it out loud several times. Write two proof points for your target role, then rehearse the whole five-minute sequence: questions, the concerns question, the closing statement and next steps. Time the closing statement and cut it until it fits in 45 seconds.
To rehearse with feedback, run a practice round with an AI interview assistant like CoPilot Interview. Its Mock Interview builds questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10 with what to fix. It's free for 15 minutes a day with no account, which is enough for a few full closes. Follow each employer's rules on AI tools, and use AI to prepare beforehand.
Rehearse your close before the real thing
Answer real interview questions out loud and get each answer scored with what to fix. Free, nothing to install.
Try a free AI mock interviewFAQ
How do you end an interview on a strong note?
Ask one or two thoughtful questions, ask whether anything in your background gives the interviewer pause and address it, give a 30 to 45 second closing statement that ties your best evidence to the role's top need, confirm next steps and thank the interviewer by name.
What is a good closing statement for an interview?
A good closing statement thanks the interviewer for something specific, names the role's main need in their words, gives one or two proof points from your experience and states your interest plainly. Keep it to about 80 to 110 words.
Is it okay to ask an interviewer if they have any concerns?
Yes. Asking whether anything gives them pause lets you answer a doubt while you are still in the room. Some interviewers can't share feedback because of company policy, so if they decline, thank them and move on.
Should I ask about next steps at the end of an interview?
Yes. Ask what the next steps are and when they expect to decide. It sets expectations, tells you when to follow up and is a natural way to wrap up the conversation.
What should you not say at the end of an interview?
Avoid asking whether you got the job, saying you have no questions, apologizing for your performance or bringing up salary and time off in a first-round close unless the interviewer raises them.
How long should the end of an interview take?
Plan for about five minutes: two for your questions, one for the concerns question, under a minute for your closing statement and a short close on next steps. If time is tight, give the closing statement and ask about next steps.