Why the interviewer asks, and what two good questions do
The interviewer asks for three reasons. It signals that the interview is ending and gives you a polite close. It tests whether you were listening: a question that picks up something said twenty minutes earlier is the strongest proof of attention you can give. And it tells them what you care about, because the first thing you ask is read as your priority. That is why 'what is the leave policy?' in a first round costs you, and 'what does a good first six months look like in this role?' helps you.
Two questions is the right number. One looks like you had nothing; four eats into the next candidate's slot. Choose one about the work (the role or the team) and one about you in the role (growth, measurement, the first ninety days). Keep a third ready in case the first is answered before you ask it, which happens often. Use the lists below as a menu, not a script; pick the ones you would genuinely want answered, and rephrase them in your own words.
The listening test
The best question in any interview is one built from something the interviewer said. 'You mentioned the team is moving the billing module to the cloud this year; would a new joiner be part of that, or on the existing system first?' beats any question from a list, because it proves you were in the room.
Questions about the role (8)
- What does a typical week look like in this role, and how much of it is the kind of work we discussed today?
- What would you expect the person in this role to have achieved in the first six months?
- Is this a new position, or am I replacing someone? If so, what did that person move on to?
- What is the hardest part of this role, the part that people underestimate?
- Which teams or clients would I work with most closely, and how is that contact usually handled?
- How much of the role is maintaining what exists versus building something new?
- Which tools and systems does the team use day to day, and which are you planning to change?
- What is the one problem you would most want the person in this role to solve first?
These work in any round. The second and the last are the strongest because the answer gives you a target to repeat in later rounds and in your closing line. If the interviewer is the hiring manager, ask one of these first; if the interviewer is HR, ask about the process instead and save the role question for the manager.
Questions about the team and the manager (7)
- How is the team structured, and who would I report to day to day?
- How does the team handle a disagreement about priorities, say between delivery and quality?
- How do you prefer to give feedback: in regular one-on-ones, on the work itself, or at review time?
- What do the people who do well on this team have in common?
- How long have most of the team been here, and what has kept them?
- How does the team work with the client or the business side: directly, or through a lead?
- If I joined, who would I learn the most from in the first few months?
Ask these only when the interviewer is the manager or a senior team member, never to a recruiter who has not met the team. The feedback question is useful because the answer tells you how the next year will feel. The question about what good performers have in common is one most interviewers enjoy answering, and the answer is usually a list of things you can then say you do.
Questions about growth and learning (7)
- How is performance measured in the first year, and how often is it reviewed?
- What does the path from this role to the next one look like, and how long does it typically take?
- Does the company support certifications or courses, and how do people usually choose them?
- Is there a formal training programme for new joiners, and how long does it run before project allocation?
- Can people move between projects, domains or locations, and how does that usually happen?
- Can you give an example of someone who joined at this level and where they are now?
- What skills does the team expect to need in two years that it does not have today?
For freshers in IT services drives, the training and allocation question is the one to ask: it is practical, it shows you expect to stay, and the answer matters to you. Experienced candidates should ask about the path and the example, and then listen for whether the example is specific; a vague answer is itself information.
Questions about culture and working style (6)
- What do you personally like most about working here, and what would you change?
- How does the team work: in the office, hybrid, or remote, and does that vary by project?
- What are the working hours and shift patterns in practice, especially with overseas clients?
- How does the company handle a crunch period, such as a release or year-end, and how are people recognised afterwards?
- How do new joiners usually get to know the rest of the team and the company?
- How are decisions about which work to take on actually made, and how much say does the team have?
The first question is safe anywhere and the answer is often the most honest thing you hear all day. The hours and shifts question is legitimate in a first round when it is asked as a practical question about client time zones; it becomes a red flag only when asked as 'do I have to work late'. Keep the tone curious, not suspicious.
Questions about the process and next steps (6)
- What are the next steps in the process, and how many rounds remain?
- When can I expect to hear back, and whom should I contact if I have not heard by then?
- Is there anything about my background you would like me to clarify or send more detail on?
- Is there anything I said today that gave you a concern about my fit for the role?
- Which documents or references will you need, so I can have them ready?
- What is the expected joining timeline if an offer is made?
Ask one of these to HR or the recruiter; they are the questions HR expects and can answer. The two 'is there anything' questions are the bravest and the most useful: they give you a chance to fix a doubt before you leave the room. Ask them only if you are ready to answer calmly, in one minute, without arguing.
Campus drives (6) and government boards: when to ask nothing
- What technology or domain will the training cover, and is there a choice at the end of it?
- When do freshers from this batch typically join a live project?
- Which locations are freshers from this drive usually posted to?
- How are freshers mapped to a business unit, and is performance in training a factor?
- Is there a buddy or mentor system for new joiners in the first year?
- What did the freshers who joined last year find hardest in their first six months?
In campus and IT services drives the HR round is short and the panel has a quota of candidates, so ask one question, two at most, from this list, and make it about training, allocation or the first year. Do not ask about the bond amount, the package or leave in the interview; those are in the offer letter, and asking about them before the offer suggests you are already looking for the exit.
Government and PSU boards: usually ask nothing
In a UPSC, State PSC, bank PO, SSB or PSU board, the panel does not usually invite questions, and you should not volunteer them. The board's job is to assess you; the process, posting and pay are published in the notification. If the chairperson asks 'anything you would like to ask us?', a short 'No sir, thank you for the opportunity' is correct. The exception is a clarification during the interview itself, such as asking for a question to be repeated. For how those boards run, see the UPSC interview and IBPS PO interview guides.
Questions to avoid, and when they become acceptable
How to ask two questions in thirty seconds
- 1
Signal and thank
'Yes, I have two quick questions, thank you.' Four seconds. Saying 'two' tells the interviewer how long this will take, and 'quick' promises you will not overrun.
- 2
Ask the work question
Pick the role or team question that connects to something said in the interview. One sentence, under fifteen words if possible. Then stop talking and listen to the full answer; do not nod through it while reading your next question.
- 3
React in one line
'That is helpful; that is the kind of work I was hoping for.' A one-line reaction turns a list into a conversation and lets you repeat your interest without a speech.
- 4
Ask the 'me in the role' question
Growth, measurement or the first ninety days. 'How is performance measured in the first year?' is a good default for almost every role and level.
- 5
Close
Thank them, state your interest in one sentence, and ask about next steps only if they have not been covered. Then stop. The close is not the place for a summary of your strengths.
If you are nervous about timing, write your two questions on the last line of the notepad you bring in, and glance at it when the question comes. Interviewers do not mind a candidate reading a question from notes; it shows you prepared. For the full structure of a strong HR round, see HR interview questions with answers and the Questions to Ask and Closing the Interview course.
Sample closing lines, spoken
Do you have any questions for us? (Fresher, IT services campus drive)
Yes, two quick ones, thank you. You mentioned that freshers go through a training programme before allocation; is there a choice of technology at the end of it, or is it based on project demand? And how is a fresher's performance measured in the first year, so I know what to focus on? Thank you for your time today, especially for the discussion on my project; I would be very glad to join this batch.
Panel checks: that you asked about the work and the first year, picked up something they said, and closed in one line.
Say this answer out loudDo you have any questions for us? (Experienced, hiring-manager round)
Two questions. Earlier you said the team is splitting the billing service out of the monolith this quarter; would the person in this role be on that split from the start, or on the existing system first? And what would you want to see from me at the end of the first six months to feel the hire had worked? Thank you; this has been the most useful conversation I have had about the role, and I am keen to go to the next round.
Panel checks: a question built from their own words, a question about how you will be judged, and a confident close with no summary speech.
Say this answer out loudDo you have any questions for us? (Final HR round, offer stage)
Yes, thank you. What are the next steps and the expected timeline for a decision, and whom should I write to if I have not heard by then? And if an offer is made, what is the expected joining window, so I can plan my notice period? I also wanted to confirm: the role is based in Pune with three days a week in the office, as discussed with the manager? Thank you for coordinating all three rounds so smoothly.
Panel checks: process questions aimed at HR, a confirmation rather than a renegotiation, and courtesy to the recruiter.
Say this answer out loudDo you have any questions for us? (When your questions were already answered)
You have actually answered the two things I wanted to ask, about the training path and how the first year is reviewed, so thank you for that. One small question: is there anything I said today that you would like me to clarify or expand on before you make a decision? Otherwise, thank you for your time; I am very interested in this role.
Panel checks: you did not invent a question for its own sake, and you gave them a chance to raise a doubt.
Say this answer out loudWould you like to ask the board anything? (Government or PSU board)
No, sir, thank you. The board has been very kind, and I have no questions; whatever I needed to know about the service and the process was in the notification. Thank you for the opportunity.
Board checks: composure and protocol. Stand only when told to, thank the chairperson, and leave without lingering.
Say this answer out loudWhat the ExamPilot AI interviewer checks at the close
Every ExamPilot mock ends with 'do you have any questions for us?', and the close is scored separately from the rest of the round. The AI interviewer answers your questions the way a real manager or HR would, including with a vague answer now and then to see whether you follow up, and it notices whether your question connects to something it said earlier in the session.
Run it for your role in job interviews, for example the product and design loop, where the closing questions carry real weight because the manager is judging curiosity. The other nineteen questions that come before this one are in most common interview questions, and fresher versions of the whole round are in interview questions and answers for freshers.
Practise out loud
Practise the close with the AI interviewer
A full product and design loop that ends every round with 'any questions for us?', answers them like a real manager, and scores your questions and closing line.
Job interviews · Product & design
Frequently asked questions
- What are good questions to ask at the end of an interview?
- Questions about the work and about how you will be judged: what a typical week looks like, what the person in this role should achieve in six months, how the team handles disagreements, how performance is measured in the first year, and what the path to the next role looks like. The strongest question is one built from something the interviewer said during the round, because it proves you were listening.
- How many questions should I ask the interviewer?
- Two, with a third ready in case one gets answered before you ask it. One looks unprepared and four overruns the slot. Keep the whole exchange, including the interviewer's answers and your close, under two minutes in a campus drive and under five in a hiring-manager round. Say 'I have two quick questions' so the interviewer knows what to expect.
- Is it okay to ask about salary at the end of an interview?
- Not in a first round, and not to a hiring manager. Salary, leave and work-from-home questions belong in the HR or offer discussion, or when the interviewer raises them. Asking them early reads as a priority on pay before you have shown value. If HR asks for your expectations, answer them; if not, wait for the offer stage.
- What questions should I ask HR at the end of an interview?
- Process questions: the next steps and number of rounds, when to expect a decision and whom to contact, which documents will be needed, the expected joining timeline, and whether anything in your background needs clarification. For campus drives, ask about training duration and project allocation. Save questions about the team's work for the hiring manager, who can actually answer them.
- Should I ask questions in a government or PSU interview board?
- Usually no. UPSC, State PSC, bank and SSB boards assess you; they do not invite questions, and process details are in the notification. If the chairperson asks whether you have anything to ask, a polite 'No sir, thank you for the opportunity' is the right answer. Asking for a question to be repeated during the interview is fine.
- What if the interviewer has already answered all my questions?
- Say so, and thank them for it: 'You have covered the two things I wanted to ask, about training and the first-year review.' Then ask one of the process questions, or the bravest one: 'Is there anything I said today that you would like me to clarify?' That shows you were listening and gives them a chance to raise a doubt you can fix.
- How can I practise asking questions at the end of an interview?
- Write your two questions and your closing line, say them aloud until they are under thirty seconds, and then run a full ExamPilot mock, which ends every round with 'any questions for us?', answers them like a real manager or HR, and scores whether your questions were relevant, built on what was said, and aimed at the right person, with a transcript to review.