"Do you have any questions for us?" usually arrives at the end of an interview, when you are tired and relieved. It is still part of the assessment. Good questions show that you prepared and that you are judging fit seriously, and the answers give you information you cannot get from a job description.
Career guides agree on the basics. Cleveland State University's careers office says your questions should achieve three things: leave the interviewer with no reservations about you, show interest in the employer, and help you decide whether the employer is right for you. It recommends preparing three to five questions. Carnegie Mellon's interviewing guide suggests a list of five to eight well-researched questions for the end of each interview. A sensible middle path: prepare about eight, expect to ask two to four, and choose based on what the conversation has already covered.
An earlier version of this article included an anecdote with a salary figure and a survey statistic we could not trace to any source. Both have been removed.
Questions for the HR or recruiter screening
This conversation is about the role's basics, the process and practical fit.
| Question | What the answer tells you |
|---|---|
| What are the next steps, and what is the expected timeline? | How organised the process is, and when to follow up |
| What would make someone successful in this role in the first six months? | What to emphasise in later rounds |
| Is this position on the company's own payroll or through a staffing partner? | Who your legal employer would be, which affects benefits and stability |
| Which location and shift timings apply to this role? | Whether the role fits your life before you invest more time |
| How many interview rounds are there, and who will I meet? | How to prepare for each round |
Recruiters in India commonly ask for your current and expected CTC at this stage. If they do, answer honestly with a researched range; you will negotiate the details once there is a written offer.
Questions for the hiring manager
This is the most important set. The hiring manager decides what your days look like.
| Question | What the answer tells you |
|---|---|
| What are the biggest problems the team is working on right now? | Whether the work interests you, and where you could contribute early |
| What does a typical week look like in this role? | How much of the job is meetings, focused work, support or travel |
| How will you measure success for this role at the end of the first year? | Whether expectations are clear and realistic |
| Why is this position open? | Growth, a replacement or a new team, each of which means something different |
| How do you prefer to give feedback, and how often do you have one-to-ones? | The manager's style, which shapes your day-to-day experience |
| What would you want me to learn first? | Gaps you can start closing before joining |
"Why is this position open?" can feel bold, but it is a fair, neutral question. If the role has turned over several times, the answer often hints at it.
Questions for team members or a technical panel
- What does code review (or work review) look like on this team?
- How are priorities set when everything is urgent?
- What tools and processes does the team use day to day?
- What do you enjoy most about working here, and what would you change?
Peers are often more candid than managers. Listen for specifics rather than slogans.
Questions for senior leaders
Keep these strategic and connected to the role:
- How does this team's work connect to the company's priorities for the coming year?
- What would you most like a new person in this role to bring?
- How has the team or role changed over the last few years?
Cleveland State's list includes a similar question about how the position has evolved, which is useful at any level.
India-specific questions to ask before you accept
Some important details are best asked once an offer is close or in hand, usually with HR. They are practical rather than awkward, and good employers answer them clearly in writing.
| Topic | Question to ask | Why it matters |
|---|---|---|
| Pay structure | How is the CTC split between fixed pay, variable pay and benefits? | Monthly take-home depends on the fixed part, not the headline CTC |
| Service agreement | Is there a training bond or service agreement, and what are its terms? | You need to know any repayment conditions before signing |
| Probation | How long is probation, and what changes on confirmation? | Notice period and some benefits can differ during probation |
| Notice period | What notice period applies after confirmation? | It affects your future job moves |
| Joining | What is the joining date, and which documents are needed for verification? | Avoids delays from missing certificates or relieving letters |
Our guide to comparing salary and benefits explains how to read each component.
Questions to avoid or reframe
- Facts you could have looked up. "What does your company do?" signals no preparation. Cleveland State's and Carnegie Mellon's guides both stress researching the employer first.
- Leading or negative framing. Instead of "Is the workload terrible?", ask "How does the team handle peak periods?"
- Pay and leave in a technical round. University guides advise against raising salary and benefits in interviews. In Indian hiring, compensation is usually discussed with HR, so save those questions for that conversation or the offer stage.
- Questions already answered. If the manager has explained the team structure, don't ask about it again. Ask a follow-up instead: "You mentioned the team is moving to a new platform. What is the hardest part of that move?"
Worked example: turning research into sharp questions
Generic questions are fine; researched ones are memorable. Here is the method, applied to a fictional company.
| What you found (illustrative) | Generic question | Researched question |
|---|---|---|
| The company's careers page says it is expanding its Pune office | "Do you have growth plans?" | "I read that the Pune office is growing. Will this team be part of that, and how would it change the role?" |
| The job description mentions "migrating legacy reports" | "What will I work on?" | "The description mentions migrating legacy reports. Where is that project now, and what has been hardest so far?" |
| The interviewer said the team recently missed a release | "How is the team doing?" | "You mentioned the last release slipped. What did the team change afterwards?" |
The formula: one specific fact, then an open question about its effect on the role or the team. Open questions that start with "how" or "what" produce better answers than yes/no questions.
How to listen to the answers
Asking is only half the job. Note the answers right after the interview, because they matter when you compare offers.
- Specific answers — named tools, real examples, clear success measures — usually reflect a team that knows what it wants.
- Vague answers to simple questions, such as how success is measured, may mean expectations are unclear. Ask a gentle follow-up before drawing conclusions.
- Inconsistent answers between interviewers about the role's scope are worth clarifying with the recruiter.
A one-page checklist
- Research the company's website, recent news and the job description.
- Prepare about eight questions across the categories above.
- Pick two to four in the moment, skipping anything already covered.
- Keep pay, bond, probation and notice-period questions for HR or the offer stage.
- Write down the answers within an hour of the interview.
- Use any question you forgot in a short follow-up email, as our interview follow-up guide shows.