Clear the rounds
25 Questions To Ask The Interviewer
Priya interviewed six candidates today. Five of them said "No ma'am, you have explained everything." The sixth asked what the team was struggling with right now, listened, and wrote one line down. It is 7 p.m. Guess which name she remembers.
11 min readFree, no email neededUpdated 11 September 2026
The last five minutes
The moment most freshers waste
🤔
Priya interviewed six candidates today. Five of them said "No ma'am, you have explained everything." The sixth asked what the team was struggling with right now, listened, and wrote one line down. It is 7 p.m. Guess which name she remembers.
"Do you have any questions for us?" is not politeness and it is not the end. It is the last thing on the scorecard. Saying no does not read as humble; it reads as not interested, or not prepared, and it wastes the only five minutes of the interview you control.
The rules
- Prepare five. Ask two or three.Some will get answered during the interview. Bring spares so you are never empty.
- Match the question to the person in front of you.Never ask an engineer about leave policy, or HR about the deployment pipeline. Wrong person, wasted question.
- Never ask anything the careers page answers.What the company does, when it was founded, how many employees. Ten seconds of homework.
- Ask about the work, not the perks.Every question in this guide is about the job. That is the whole trick.
Round 1 · with the engineer who tested you
Technical round
01What does a normal week look like on this team — how much new code versus maintaining what exists?
SignalsYou are thinking about the job, not the job title.
Good answerA real split, a sprint length, an honest mention of bug duty or on-call. "It varies" from a senior engineer means nobody has a plan.
02What is the stack for this specific team, and is anything changing this year?
SignalsYou care about what you will actually learn here.
Good answerNamed tools and versions, plus one honest migration ("we are moving from Java 8 to 17"). Worry if they cannot name the team's stack.
03How does code get from my laptop to production here — review, tests, deployment?
SignalsYou already know pull requests and CI exist. Very strong for a fresher.
Good answerPRs with one or two reviewers, automated tests, a staging environment, deploys weekly or daily. "We just push to main" is a real warning.
04What would a good first three months look like? What would I have shipped by then?
SignalsYou think in outcomes, and you plan to be useful early.
Good answerA concrete first task, a buddy or mentor, an onboarding doc they can name. If they have never thought about it, onboarding will be you guessing.
05Is there something about this codebase you wish someone had explained to you on day one?
SignalsCuriosity and humility. Engineers genuinely enjoy this one.
Good answerSomething specific and slightly painful — a legacy service, an undocumented rule. A perfectly rosy answer means they are being careful with you.
Round 2 · with the person you would report to
Manager round
06How is this team's work measured? What does a successful six months look like for you?
SignalsYou want to be judged, and you want to know the yardstick.
Good answerNamed goals or metrics the team owns. Vagueness here usually means the team's priorities change every month.
07How do you like to give feedback, and how often do you do one-on-ones?
SignalsYou are coachable and you expect to be corrected.
Good answerWeekly or fortnightly one-on-ones, feedback in the moment, a review cycle they can describe. "My door is always open" and nothing else is not a system.
08What is the biggest problem the team is solving right now, and where would a fresher fit into it?
SignalsYou want real work, not a training bench.
Good answerAn actual current problem, and an honest answer about what a junior would own inside it.
09What happens when something breaks in production — say I push a bug on a Friday evening?
SignalsYou expect to own mistakes. It also quietly tests the blame culture.
Good answerRoll back first, find the cause after, write it up, no names. A story about someone getting shouted at is your answer about the culture.
10What have people who joined this team as freshers gone on to do here?
SignalsYou are thinking in years, not months.
Good answerReal examples with names of roles and rough timelines. If nobody has stayed long enough to answer, that is also information.
Round 3 · with HR
HR round
11Is there a training period before I join a project, and is it paid at the full package?
SignalsYou understand how Indian service companies actually onboard.
Good answerA clear length, a clear stipend or full pay, and what happens if you fail the training assessment. Many pay a reduced amount for three to six months — better to know now.
12Is there a service agreement or bond? What are the amount, the duration and the terms?
SignalsYou read documents before you sign them. Nobody is offended by this.
Good answerA plain number and a plain duration, and an offer to share the clause in writing. Hesitation or "it is just a formality" means read it twice.
13What is the base location and the work model, and when is allocation confirmed?
SignalsYou are planning your move, not just chasing an offer.
Good answerA city, a number of office days, and a date for allocation. "We will let you know" close to joining is common — plan for it.
14How would you describe the culture here to someone about to join — not the website version?
SignalsYou want the truth, and you are comfortable asking for it politely.
Good answerSpecific habits: how meetings run, how decisions get made, what people complain about. Adjectives only ("dynamic, young") means they have not thought about it.
15What kind of person does well here, and what kind of person struggles?
SignalsSelf-awareness. The strongest question in the HR round.
Good answerBoth halves answered honestly. If they only answer the first half, ask the second half again — gently, once.
Final round · they already want you
Last round and offer stage
16Could you walk me through the package — fixed, variable, joining bonus, retention?
SignalsYou know CTC is not salary. Ask this only at offer stage, never in round one.
Good answerEach part named with a number, and a monthly in-hand figure on request.
17How is the variable component decided, and what percentage did last year's batch actually receive?
SignalsYou read the fine print. Very few freshers ask this.
Good answerA real historical percentage. "It depends on performance" with no number means treat the variable as optional money.
18By when do you need my decision, and what is the expected joining date?
SignalsYou are managing a process, not begging for a job.
Good answerA date for both. If they want an answer in 24 hours, it is fair to ask for a week in writing.
19Is there anything in my profile that gave the panel any doubt? I would rather address it now.
SignalsConfidence. It also hands you the chance to fix a weak answer.
Good answerOne honest gap you can respond to in two sentences. Do not argue — acknowledge, then give the missing evidence.
20Who would I work with in my first month, and could I speak to one of them before I decide?
SignalsYou are choosing them too. Reasonable companies say yes.
Good answerA name and a call. A flat refusal at offer stage is worth noticing.
Any round · any person · any company
Five that work anywhere
21What made you join, and what has kept you here?
SignalsYou treat the interviewer as a person. Almost everyone enjoys answering it.
Good answerA specific story with a date in it. A long pause is an answer too.
22If you could change one thing about working here, what would it be?
SignalsYou want the real picture, and you can handle it.
Good answerAn honest, small complaint — slow hiring, too many meetings, ageing tooling. "Nothing at all" is not a good answer.
23Is there anything from my answers today you would like me to clarify or go deeper on?
SignalsYou know one answer went badly and you are not hiding from it.
Good answerThey name the weak spot. Answer it in under a minute, then stop. Use this question once, at the end.
24What are the next steps, and by when should I expect to hear back?
SignalsBasic professionalism. Ask it in every single round, always last.
Good answerNumber of rounds left and a date. That date is also your permission to follow up politely after it passes.
25Between now and joining, what should I learn so I am useful faster?
SignalsThe strongest fresher question there is. It ends the interview on you being ready.
Good answerA named tool, book, doc or topic. Write it down, then mention what you did about it in your thank-you email.
Six to never ask
Each of these has undone an otherwise good interview. There is a safe version of most of them.
- "How many leaves do I get? What are the holidays?"The first thing you asked about was time away from work. Instead: ask HR after the offer letter, or ask question 01 and hear the same thing.
- Salary in round one, especially to the technical panel.Wrong person, wrong round — the engineer cannot change it and will remember you asked. Instead: question 16, at offer stage.
- "So what exactly does your company do?"Instantly fatal, and it happens more often than you think. Ten minutes on the website and one recent news item prevents it forever.
- "Is work from home allowed?" as your only question.Reads as negotiating comfort before you have done anything. Instead: question 13, asked as a factual planning question.
- "How did I do? Did I clear this round?"They usually cannot tell you, and it puts them on the spot. Instead: question 24, which gets you the timeline instead.
- "Will there be overtime? Do you work weekends?"Reads as pre-negotiating effort. Instead: question 01 — a normal week tells you everything without the flinch.
And one habit, not a question: do not ask something they already answered. If they covered it, say so out loud — "you already covered the review process, so instead I wanted to ask…". That single sentence proves you were listening.
How to use their answer
A question you do not listen to is worse than no question at all. Four moves, in order.
- 1Follow up once. Exactly once."You said deploys go out weekly — is that a fixed release day, or whenever the tests pass?" One follow-up turns a question into a conversation. Two turns it into an interrogation.
- 2Take a note while they talk.Write one line on paper. It shows you asked because you wanted to know, not because you had read a list. On a video call say "one second, let me note that down" so the typing is not rude.
- 3React like a human."That is good to hear — my last project had no review process at all and I could feel it." One honest sentence, connected to your own work, and it is no longer a Q&A.
- 4Close the loop within 24 hours.Use their answer in your thank-you email: "You mentioned the team is moving to Java 17 — I spent the weekend on records and sealed classes." This is the line that gets remembered.
Aarav, round 1
"No sir, everything is clear, thank you." Interview ends four minutes early. Nothing to write in the thank-you email.
Aarav, round 3
Asks question 08, follows up once, writes one line down, and emails that evening about the exact problem the team named. Priya forwards the email to the manager.
Google Meet · Zoom · Teams
Asking on a video call
- Keep the list on paper, not on screen.A sticky note beside the laptop, or one line on a notepad. Visibly scrolling a document while you "think of a question" is obvious on camera.
- Ask at the 40-minute mark of a 45-minute call.Do not wait for "we are at time". Say: "I have two questions if we have a minute." You will almost always get them.
- One sentence per question.Bad audio plus a 30-word question equals "sorry, could you repeat that?" Look at the camera to ask, at the screen to listen.
- On a panel, address one person by name.Get every name at the start, spelled. "Rahul, this one is for you as the tech lead —" makes three faces in boxes feel like a conversation.
- Do not paste questions into the chat box.Ask them out loud. The chat is for links and nothing else.
- If the call drops or time runs out, move them to email."I will send my two questions by email so I do not hold you up" — then actually send them, inside the thank-you mail, that day.
Before the call: write the interviewer's name, the team name, and your five questions on one sheet of paper. That sheet is also what you use to write the thank-you email an hour later.
Want this on your phone?
Everything above, as a PDF built to read on a phone the morning of the interview. It costs nothing — we ask for an email so we can send it, and that is all.