Questions You Should Ask the Interviewer

Every interview ends with some version of Do you have any questions for us? and most candidates say no. That answer costs you twice: it reads as low interest, and it wastes the only part of the interview where you get to find out what you are actually signing up for.

Why this part is not a formality

By the time you are asked, the interviewer has largely formed a view. A good question can still shift it, because it shows how you think about work. Equally important, you are about to commit one to three years of your career, and details that decide whether you will be happy, such as shift timings, on-call load, variable pay and appraisal cycles, are never in the job description.

Prepare six questions and ask two or three, chosen based on what came up during the conversation. Carry them written down. Taking out a small notebook is a positive signal, not a negative one.

Questions for the technical round

Ask the person who will work alongside you about the work itself.

• What would I be working on in the first three months, and is it a new build or an existing system?
• How large is the team, and how is work split between the India team and any onsite or client-side team?
• What does the release cycle look like, and who handles production issues?
• Which parts of the stack are you planning to change in the next year?
• What do people in this role usually find hardest in the first six months?

That last one is the most useful question on the list. The answer is rarely rehearsed and tells you a great deal about the team.

Questions for the HR round

This is where you ask about terms, and you are entitled to clear answers before you accept anything.

• How is the CTC split between fixed, variable and retirals, and what is the variable linked to?
• Has the variable component been paid in full in recent cycles?
• Is there a service bond, a training agreement or a retention bonus with a clawback clause?
• When is the appraisal cycle, and will I be eligible in the first cycle after joining?
• What are the working hours and is there any shift or on-call requirement?
• What is the current policy on work from office, and is it likely to change?
• What is the notice period on my side after confirmation?

If you are talking to a consultancy rather than the company, add two more: whose payroll will I be on, and is this a contract-to-hire arrangement with a conversion timeline? Many candidates in Gurugram and Bengaluru only discover this at offer stage, when they have already resigned.

Questions for the hiring manager or panel

With a manager, ask questions that show you are thinking about delivery rather than just tasks.

• How do you measure whether someone in this role is doing well?
• Is this a new position or a replacement, and what happened to the previous person?
• What is the one problem you are hoping this hire will solve?
• How do you usually give feedback to the team?

In a panel interview, direct each question to a specific person rather than the room, and ask the technical panellist a technical question and the manager a delivery question.

Questions to avoid, and when

Timing matters more than the topic. Leave policy, food allowance, cab facility and salary negotiation are fair questions, but they belong in the offer discussion, not in the first technical round. Asking How many leaves do I get? before you have been assessed suggests your first thought is about being away from work.

Also avoid anything you could have found on the company website, since it signals you did not look. Do not ask How did I do? at the end of a round, which puts the interviewer in an awkward position. And do not ask a question you do not actually want answered, because interviewers can tell when a question is decorative.

How to ask so it lands well

Attach your question to something that came up. For example: You mentioned the team is supporting two products. Does the same engineer handle both, or is it split? That shows you were listening rather than reading from a list.

Ask two or three, not eight. If the round is running late, say: I had a couple of questions but I know we are over time. May I send them to you on mail? That is a good impression and a legitimate reason to follow up in writing.

Finally, always close by asking about process: what the next step is and roughly when you can expect to hear. Meera, a candidate in Mumbai, put it simply at the end of every round: What is the next stage, and by when should I follow up if I have not heard from you? It gave her a date, a reason to email, and a clean way to chase without seeming anxious.

Good questions do not just leave a better impression. They stop you accepting a job whose real shape you never asked about.