Questions to Ask and Closing the Interview

The answers you give are only half of an interview. The other half is how you handle the quiet moments: the end, the blank moment in the middle, the email afterwards, and the offer.

Most people spend all their time on the questions and none on these parts. That is a pity, because these parts are easier to prepare for, and they leave a lasting impression. The last five minutes of a conversation are often the part people remember best.

"Do you have any questions for us?"

Almost every interview ends with this. Many candidates say "No, I think you covered everything". It is a small miss. Think of it like a shop visit: if you walk in, look at nothing and ask nothing, the shopkeeper wonders if you are really interested.

Your questions do three jobs. They show you have thought about the work. They give you information, because you are also choosing them. And they make the conversation feel like two people talking, not a test.

Have at least three questions ready, and write them in your notes. Expect that some will be answered during the interview, so bring more than you need.

Group them by who you are talking to

The person in front of you matters. A recruiter does not know the details of the code. An engineer does not decide your pay. Ask the right question to the right person.

Questions for an engineer

These are about real daily life. A peer will usually answer them honestly.

• What does a normal week look like for you, from Monday to Friday?
• How long does it take for a change to go from your laptop to real users?
• When something breaks at night, what happens? Who gets called?
• What part of the code do you like least, and what would you change if you had a month?
• How are code reviews done here? How long does a review usually take?
• What did you learn in your first three months that you did not expect?
• When did you last disagree with a decision, and how was it handled?

The last two are quiet favourites. People like answering about themselves, and the answers tell you a lot.

Questions for a manager

A manager can tell you about direction, expectations and growth.

• What would a successful first 90 days look like for this role?
• What is the biggest problem the team is trying to solve this year?
• How do you give feedback, and how often? Is there a regular one-to-one?
• How do people grow here? Can you give me an example of someone who was promoted, and what they did?
• How does the team decide what to build next? How much say do engineers have?
• What is something the team is not good at yet?

That last question is a gentle one, and a good manager will answer it. If they cannot name anything, that is a small warning sign about honesty.

Questions for a recruiter

A recruiter knows process and basic facts. Keep it practical.

• What are the remaining steps and how long does each usually take?
• Is there a pay range for this role? (It is fine to ask. In many places, they must tell you.)
• What is the team size, and is the role hybrid, remote or in the office?
• When do you expect to make a decision?
• Is there anything I should prepare for the next round?

Weak questions to avoid

None of these will lose you the job on its own. But they send a signal, and early in the process you want a good one.

Leave and flexibility are fair things to ask about. Ask the recruiter, usually after you know they like you. You are not doing anything wrong by caring about them.

One more tip about questions

Ask one thing that comes from the conversation. If the interviewer mentioned a migration, a big launch or a tough problem, say "You mentioned the move to a new database. What has been the hardest part?" It shows you were listening, and a question like that cannot be copied from a list.

What to do when you blank

It will happen to you sooner or later. A question lands and your mind goes empty, as if somebody wiped the whiteboard. It feels like a disaster. It is not.

Interviewers have seen it many times. They are far more bothered by someone who panics or bluffs than by someone who pauses for ten seconds.

Buy time, in plain words

You do not need a trick. You need a few honest sentences. Here are some you can say out loud.

• "That is a good one. Can I take a moment to think?"
• "Let me think of a good example. I want to pick the right one."
• "Can I make sure I understood the question? You are asking about a time when..."
• "I am trying to pick between two stories. Give me a few seconds."

A pause of 10 to 20 seconds feels very long to you and very short to the other person. Use it. Look at your notes if you have them, or take a sip of water.

A plain script when your mind is empty

If 20 seconds pass and you still have nothing, try this order.

1. Say what is happening, calmly: "I am drawing a blank on a perfect example. Can I come back to this one?"
2. Move on, and come back later. Often the memory returns as soon as you stop forcing it.
3. If you do not have a story that fits, say so, and offer something close: "I do not have a perfect example for a conflict with a manager, but I have one about a disagreement with a teammate. Would that be useful?"
4. If you really do not know something technical, say what you do know and how you would find the rest: "I have not used that tool. I know it is used for X, and I would start by reading its documentation and asking the team."

What you should not do: make something up. A made-up answer collapses at the first follow-up, and then you look both blank and dishonest.

Before the interview, stop blanks from happening

• Keep your story bank (4 to 6 stories, with numbers) in a note on your desk or a second screen, if the interview is remote and notes are fine. It is common to have notes in a video interview, but do not read word for word.
• Practise starting a story with one short line, for example "The first thing that comes to mind is a release where...". The first line is the hardest part. After that, the rest follows.

Recovering from a bad answer

Say you finish an answer and you know it was poor. You rambled, or you picked a story that did not fit, or you said something you wish you had not.

It is fixable. One weak answer in an hour-long interview is rarely the deciding thing. Interviewers form their view over the whole hour, and many of them quietly expect one rough moment.

What to do:

• Stop and breathe. Do not apologise four times.
• If you realise it in the moment, correct it once: "Actually, can I try that again? A clearer example would be..."
• If you realise later in the same interview, you can come back to it: "Earlier you asked about X. I thought of a better example, if you have a minute."
• Do not let one bad answer ruin the next. Each question is a new start.
• If it was a technical slip, say it was a slip: "I said that wrong. What I meant was..."

The recovery itself is a good thing for them to see. It shows you can notice a mistake and fix it, which is exactly what they want in a teammate.

If you realise after the interview was over, you can put a short correction in your thank you email. Keep it to two sentences. More than that looks anxious.

The thank you email

A thank you email is optional, but I would send one. It takes five minutes, and many interviewers appreciate it. Send it the same day, or the next morning, to the recruiter, or to the interviewer if you have their address.

Keep it short. Three to five sentences. Mention one specific thing from the conversation, so it does not look like a copy-paste.

An example:

Subject: Thank you for today

Hi Priya,

Thank you for taking the time to talk with me today. I enjoyed hearing
about how your team is moving the billing service to a queue, and the
way you described testing it with real traffic first.

I am still very interested in the role. If it helps, I am happy to
share anything more about the checkout project we discussed.

Thanks again,
Sam

The names are made up. Use the real ones.

A few small points:

• One email per interviewer is plenty. Do not follow up daily.
• If they gave you a date for the decision, wait until after that date, and then send one polite note: "I wanted to check in on the timeline. I remain very interested."
• Check the spelling of names before you hit send.

The offer conversation, the basics

If you get an offer, congratulations. This is when many people make their one avoidable mistake: saying yes in the first minute because they are happy and relieved.

An offer is like the price tag on something big, such as a second-hand motorbike. A good buyer does not hand over cash in the first minute. They look it over, compare, and ask questions. It is not rude, and the seller expects it.

Do not rush

Thank them warmly, and say you are excited. Then ask for time. This is normal.

"Thank you, I am really happy to get this. Could I have until Friday to go through the details and give you an answer?"

A few days is a reasonable ask. A week is common. If they need an answer sooner, they will tell you.

Get it in writing

A phone call is only the start. Ask for the offer in an email or a document, with these items:

• Base pay (the fixed amount you get each month or year)
• Bonus, and whether it is guaranteed or depends on results
• Equity (shares or stock options), with the amount and how long you wait before you own them
• Joining date, notice period and any joining bonus
• Leave, health cover and other benefits
• Job title, level and where you will work

If something you were told in the interviews is not on the paper, ask them to add it.

Compare in writing

If you have more than one offer, or a current job, put the numbers side by side in a simple table. Include everything, not just the headline pay. For example:

Money is not the only column. Look at the team, the manager, what you will learn and how stressful the work is. A slightly lower offer with a better manager can be worth more than it looks.

A gentle script for talking about pay

Many people fear asking for more because they think the offer will be taken away. In practice, a polite, reasonable question almost never makes a company cancel an offer. They expect some discussion.

A few rules that help:

• Be warm first. Show that you want the job.
• Give a reason. "Based on my research and the scope of the role" is better than "I want more".
• Ask a question. It is softer than a demand.
• Be ready for a no, and decide beforehand what you would accept.

A short script:

"Thank you again, I am excited about the role and the team. I have looked at the offer, and I have one question. The base pay is a bit below what I was hoping for, given the scope of the role and what I bring. Is there room to move it closer to X?"

If you have another offer, you may say it plainly, without pressure: "I have another offer at Y, and I would prefer to join you if we can get closer on pay." Say this only if it is true. Do not invent an offer.

If they cannot move the base pay, ask about other things: a joining bonus, an earlier review date (for example a pay review after 6 months), more leave, or a higher level.

When they reply, give a clear answer on time. Whether you accept or decline, thank them. Companies and recruiters talk to each other, and a polite no today can become a yes next year.

Different countries and companies treat negotiation differently, so read about the norms where you are. If you are junior and the pay is fair and fixed (like many graduate schemes), it is also fine to accept as it is.

One page checklist for the night before

Print it, or copy it into a note.

Stories and answers

• I have 4 to 6 real stories, each with a number.
• Each story has a four-line summary: what happened, my part, what I did, what changed.
• I know which story I would use for conflict, failure, feedback, ownership and a hard decision.
• I have one honest answer for "tell me about yourself" in about a minute.
• I can explain my current or last project in two minutes without jargon.

Questions to ask

• I have 3 questions for an engineer, 3 for a manager, and 2 for a recruiter.
• One question refers to something I read about the company or team.

The company

• I read the company website, and their blog or engineering posts, for 20 minutes.
• I know the role, the team and the products in one sentence each.

Logistics

• I know the time, including the time zone, and the name of the interviewers.
• The link works, or I know the route and how long it takes, with a spare 20 minutes.
• Laptop charged, charger nearby, headphones tested, and a quiet room is booked.
• Water, a pen and paper, and my notes are within reach.
• I have the recruiter's number in case something goes wrong.

Body and mind

• I have laid out what I will wear.
• I plan to sleep at least 7 hours. A short late-night cram helps less than rest does.
• I have a plan for the blank moment: pause, ask for a moment, say it plainly.
• I will take a short walk or stretch before the call.

After

• I will write down the questions I was asked, the same day, while I remember them.
• I will send a thank you email within a day.

Try it yourself

• Write 3 questions for each of the three kinds of people, then circle the one you really want answered. Ask that one first.
• Look at your questions and cross out any you could answer by reading the website.
• Practise the blank moment with a friend. Ask them to throw a surprise question at you, and use the plain script out loud. Notice how short the pause actually is.
• Write your own thank you email for a made-up interview. Cut it to five sentences.
• Say the pay script aloud, three times, until it does not feel strange in your mouth.
• Make your own one page checklist from the list above, then remove anything you would never do.