She had four questions written on a sticky note, and the interviewer answered three of them unprompted during the round. So when he said “any questions for me?”, she read out the fourth one anyway — “what does a typical day look like?” — and watched him give the answer he had clearly given nine times that week. The sticky note had survived the interview. Her attention had not.
Most advice about questions to ask the interviewer hands you a list to memorise, which is exactly the failure above. The list is not the problem. The problem is that a memorised question proves you were rehearsing while the other person was talking. This guide covers what the last five minutes are actually measuring, the questions to ask at the end of an interview in a technical round versus an HR round, what freshers should ask when they have no work history to anchor to, and the ones that quietly cost you.
The last five minutes are a scored round
Interviewers are usually filling in a form. Not always a formal rubric, but some structured version of “would I want this person on my team” with space for evidence. Your questions land in that box, because they are the only part of the interview you controlled entirely.
That cuts both ways, and it is why this section is worth more than its length suggests. Everything else in the round was reactive — they asked, you answered. The questions are the one moment where the interviewer learns what you chose to care about with nobody prompting you.
This is also why the standard listicle underperforms. A question copied from a blog post is, by construction, a question that could have been asked of any company on earth. The interviewer has heard it. They will answer it politely. It buys you nothing.
Why “what is the company culture like?” costs you
It is the single most common question candidates ask, and it is close to unanswerable. Nobody says “the culture is poor and people leave within a year.” You get a warm, generic answer that tells you nothing, and you have spent your one turn on it.
The same applies to “what does a typical day look like?”, “what are the growth opportunities?”, and “what do you like about working here?” They are not offensive. They are just inert — questions that produce a brochure answer and reveal nothing about you.
The fix is not a cleverer question. It is a narrower one. Culture questions work when they ask about a specific mechanism instead of a mood: how code review disagreements get settled, what happens when a sprint commitment slips, whether the on-call rotation includes the people who wrote the service. Those have real answers, and the real answer is genuinely useful to you.
Questions to ask at the end of an interview
These work across most rounds because each one forces a concrete answer rather than a pitch.
- “What does someone need to have done in the first six months for you to feel this hire went well?” The strongest general-purpose question there is. It converts a vague role into a specific scorecard, and a hiring manager who cannot answer it has not thought the role through — which is information you want.
- “What is the part of this role people underestimate before they join?” Invites honesty and usually gets it, because it gives them permission to name the annoying part.
- “What is the team spending most of its time on right now — building, maintaining, or migrating?” The ratio tells you more about your next year than any culture answer will.
- “Where does this team sit relative to the thing the company makes money from?” Distance from revenue is a reasonable proxy for budget stability and for how visible your work will be.
- “What is the next step, and what is the timeline?” Not insightful, but always ask it. It ends the round with a concrete commitment and saves you a week of refreshing your inbox.
If you take nothing else from this post, take the first one. It works in a technical round, an HR round, and a final round, and it is one of the few questions that improves the interviewer’s opinion of you while also giving you something you actually need.
Questions to ask in a technical round
The engineer interviewing you is evaluating whether working with you would be pleasant and whether you think about systems past the whiteboard. Ask about the work, not the perks.
- “What is the most annoying part of the codebase right now, and is anyone allowed to fix it?”
- “How long does it take from merging a change to it running in production?”
- “What happens when something breaks at 2am — who gets paged, and does the person who wrote it get paged?”
- “How much of the test suite do you actually trust?”
- “What technical decision made here would you reverse if you could?”
Two of these are near-guaranteed to get a real, unrehearsed answer — engineers enjoy complaining accurately about their own systems, and an honest complaint is the most reliable signal you will get about what the job feels like on a Tuesday.
Questions to ask in an HR round
The HR round is often treated as the throwaway one, which is a mistake — it frequently controls the offer, the timeline, and the band. Ask questions HR is actually equipped to answer, because asking a recruiter to explain the architecture wastes both of you.
- “How is the compensation structured — fixed, variable, and what the variable is tied to?”
- “Is the band for this role already set, or does it depend on the panel’s level recommendation?”
- “What is the notice period expectation, and is there flexibility on the joining date?”
- “How many people are you interviewing, and where in the process are you?”
- “Is this a backfill or a new position?” — a backfill means someone left, and it is entirely fair to ask why.
On the money questions, ask about structure rather than naming a number here. You are gathering the information you will need later without anchoring yourself early. If you want the longer version of that argument, see our guide on how to answer salary expectations.
Questions to ask the interviewer for freshers
The fresher problem is that most good questions lean on work experience you do not have yet. The workaround is to ask about the first year specifically, which is both genuinely useful to you and demonstrates that you are thinking past the offer letter.
- “What does onboarding look like for someone joining straight out of college?”
- “Who would I be learning from day to day — is there a mentor, or is it learn-by-ticket?”
- “What separates a fresher who does well here from one who struggles?”
- “How soon do new joiners get to touch production code?”
- “Is there a training or bond period, and what are its terms?” — ask this plainly and early; see training bonds and service agreements in India.
That last one makes some candidates nervous. Ask it anyway. A company with reasonable terms will answer it without flinching, and a company that reacts badly to a factual question about a contract you are about to sign has told you something important for free.
What never to ask
- Anything findable in ten seconds. “So what does the company do?” ends the interview in the interviewer’s head. Do the reading — researching a company before an interview takes twenty minutes.
- Leave, holidays, and work-from-home policy in a first round. All legitimate concerns, all badly timed. These belong with HR or at offer stage, not with the engineer deciding whether to advance you.
- “Did I get the job?” It puts a person who cannot answer it on the spot. Ask about next steps and timelines instead.
- Anything about a person. Why the last holder of the role left, whether the team has problems with a named manager. Even when the answer matters, this is not the room.
- A question they already answered. The most damaging one on this list, because it proves you were not listening — and it is entirely avoidable by having more questions ready than you plan to ask.
Which points at the real preparation. Write six candidate questions, expect three to be answered during the round, and go in willing to abandon the sticky note. The best question you ask will usually be one you did not write down.
Where practising this actually helps
You can prepare questions from a list — Indeed, Glassdoor and the standard careers-blog roundups all have serviceable ones, and there is nothing wrong with reading them for raw material. What none of them can rehearse is the part that goes wrong: noticing, live, that question three just got answered, and producing a fourth one out of what the interviewer said instead.
Reading a list silently and saying a question out loud to a person who then reacts are different skills, and only one of them is the one you need at minute forty-two. Asking a friend helps, but a friend will not follow up on a weak question — they will nod, because they like you. Generic ChatGPT prompting has the same shape: it will happily generate twenty questions, and it will not sit through a forty-minute interview and notice you asked one that was already answered.
That gap is why Greenroom exists. Ari, the AI interviewer, runs the whole round out loud — including the end — and pushes back when a question is filler, the way an interviewer who is scoring you will not. I built it after walking out of interviews knowing I had underperformed and not being able to say where.
Being straight about the tradeoff: Ari does not know your specific interviewer, and it cannot tell you what this particular hiring manager cares about. For that, the research still has to be yours. What it can do is make sure the last five minutes are not the first time you have said these sentences aloud.
Frequently asked questions
What questions should I ask the interviewer?
Ask questions that could only have been written after this specific interview. The strongest general-purpose one is what someone would need to have achieved in the first six months for the hire to be considered a success, because it turns a vague role into a concrete scorecard. Follow it with something drawn from what the interviewer actually said during the round, and always close by asking about next steps and timeline.
Is it bad to have no questions for the interviewer?
Yes, in most rounds. Saying you have no questions reads as low interest even when you are simply tired, and it wastes the only part of the interview you control. If everything you planned genuinely got answered, say so explicitly and ask one thing anyway, such as what the next step is or what would make the first six months go well. Silence is the one answer with no upside.
What questions should you ask in an HR round?
Ask about the things HR actually owns: how compensation is structured between fixed and variable, whether the band for the role is already fixed or depends on the panel's level recommendation, the expected notice period and joining-date flexibility, where they are in the overall process, and whether the position is a backfill or newly created. Ask about structure rather than naming your own number at this stage.
How many questions should you ask the interviewer?
Ask two or three, and prepare about six. Interviewers commonly answer half your list during the round itself, so a longer prepared set is insurance rather than a plan to ask them all. Reading out every question you wrote turns the closing minutes into an interrogation, and the interviewer usually has another meeting.
What questions should freshers ask the interviewer?
Freshers should ask about the first year, since that is the part they can genuinely evaluate: what onboarding looks like for someone joining from college, who they would learn from day to day, what distinguishes a fresher who does well from one who struggles, how soon new joiners touch production code, and whether there is a training bond or service agreement and what its terms are. Ask the bond question plainly.
What questions should you never ask in an interview?
Avoid anything answerable by ten seconds of searching, questions about leave, holidays or work-from-home policy in a first technical round, asking directly whether you got the job, questions about specific individuals such as why the previous person left, and above all a question the interviewer already answered during the round. The last one is the most damaging because it demonstrates you were not listening.