skip to content

questions

4

Why do the questions a candidate asks at the end of an interview round affect how their seniority is read?

level: juniorimportance: must knowfreq 80%

answer

  1. The window is still being scored
  2. People ask about what cost them
  3. Subject matters more than delivery
  4. Perks sit at the junior end
  5. First question gets quoted in debrief

basics

~20 s

A candidate's closing questions are evidence, exactly like their answers: they show what that person has had to care about at work. Questions about equipment and perks describe a scope nobody has had to own yet.

solid answer

~40 s

A behavioral interviewer treats the candidate's closing questions as data, not as a courtesy round. People ask about what has cost them something, so the **subject** of a question places the asker on a scale: laptop specs and snack policy at one end, and at the other something like 'How are technical decisions made here, and what happens when one is revisited?'. Someone who has owned work asks how decisions get made, where their team's ownership stops, and how far out the plan is actually firm. Someone who has only been handed work asks about their own comfort. Tone and confidence barely move that reading; the subject moves it a lot, and the first question you ask is the one most likely to be quoted in the debrief.

go deeper

for a junior

Recall that the closing window is still being assessed, and bring at least two questions about the work itself. Asking how the team decides what to build next already puts you above the equipment-and-perks default.

for a middle

Be ready to explain why the subject of a question carries the signal: people ask about what has already cost them something. Prepare questions about how work is decided and reviewed, not about your own comfort.

for a senior

Demonstrate that you can follow your own question. Pick asks about ownership boundaries and decision-making where you have a sentence of real experience to trade once the interviewer answers.

for a principal

Own the calibration tradeoff: aim at the role's scope plus about one step. Questions pitched far above the posted role read as auditioning for a different job, and cost you the same round they were meant to win.

### The closing questions are part of the round, not the exit When a behavioral interviewer says "what questions do you have for me?", the interview has not ended. Many scorecards carry a line for it, and even where they do not, the interviewer walks into the debrief holding an impression of what this candidate cared about. That impression is built almost entirely from **the subject of the questions** — what they are about — and only slightly from how confidently they were delivered. The reason the subject carries so much weight is simple: people ask about what has already cost them something. Someone who has been paged at night asks about paging. Someone who has watched a rebuild get abandoned asks how decisions are revisited. Someone whose whole experience is receiving tickets and closing them asks about tickets, tooling and comfort, because that is the entire surface they have touched. ### Sort your candidate questions by what asking them reveals The useful artefact here is one list of every question you might ask, sorted not by topic but by what asking it reveals about the asker. Junior tells sit at one end; ownership probes sit at the other. | What you might ask a behavioral interviewer | What asking it reveals | | --- | --- | | Which laptop and monitor setup do you give new hires? | your surface ends at your own desk | | Is the team in the office, and on which days? | a real constraint, but pure logistics — no scope evidence either way | | What does a typical sprint look like for someone in this role? | you have received work and want to know its shape | | Who reviews my changes, and what makes one easy to approve? | you have worked inside a team and want to fit in | | How does this frontend team decide what goes into the web client next quarter? | you have seen planning and want to know whether it is real | | Where does this team's ownership of the web client stop, and who owns what is past that line? | you have hit a boundary before and paid for it | | How are technical decisions made here, and what happens when one is revisited? | you have lived through a decision being reversed and want to know whether that is survivable here | Nothing in the top rows is forbidden. Equipment and office days are legitimate things to know, and you will need those answers before you accept anything. They are simply **not evidence of scope**, so spending your interview questions on them buys you nothing on the axis the interviewer is measuring. ### Why leading with perks costs more than it looks Order matters more than most candidates expect. The first question is the one the interviewer remembers and the one most likely to be written down close to verbatim, because attention is highest just before the round formally closes. A candidate who opens with equipment and snacks has spent that slot on a subject that carries no signal, and now needs positive evidence later to overturn a first impression instead of merely adding to one. This is the most common way an otherwise competent candidate under-reads. It is rarely ignorance. It is a candidate who prepared their answers thoroughly and then treated the question window as small talk. ### Sounding senior is not the same as being read as senior Two traps sit on the other side of the same axis. - **Vocabulary without a subject.** A question packed with strategy words but asking about nothing concrete reads worse than an honest logistics question, because it looks like performance rather than curiosity. - **A question you cannot follow.** The evidence does not land in your question; it lands in the twenty seconds after the answer, when you say something of your own. If you ask how decisions get revisited and have nothing to offer when the interviewer describes reversing the web client's state approach three quarters in, the question was borrowed rather than earned. So the working test, applied to every question before it goes on your list: *if this is answered honestly, do I have a sentence of my own experience to trade back?* If the answer is no, you like the sound of the question rather than having earned it. ### Calibrate to the role plus about one step Aim the subject of your questions at the scope of the role you are interviewing for, plus roughly one step out. For a first engineering job that means how work is reviewed and how the team decides what to build next. For a role that owns a surface, it means ownership boundaries and how far out the plan is firm. Reaching several steps past the role does not read as ambition; it reads as someone auditioning for a different job than the one on offer.

  • Does asking a behavioral interviewer about paging and on-call read as a senior question or as a complaint?
    As a senior question, if you ask about the shape rather than the burden. 'Who gets paged for the web client, and what happens the morning after?' is an ownership probe. 'How often would I be woken up?' is about your comfort, and lands where the equipment questions land.
  • If the interviewer answers in one thin sentence and moves on, has your question still done anything for you?
    Yes. The signal you sent is in what you chose to ask and in what you trade back afterwards, and both survive a short answer. Offer your own sentence anyway — 'we hit that when our web client's rendering approach changed' — then move to your next question rather than re-asking the same one.
  • Is it worse to ask a perk question or to ask nothing at all?
    Asking nothing is generally read worse, because it suggests either no curiosity or no preparation, and it leaves the interviewer with zero evidence on this axis. A perk question at least reads as human. Neither is a good use of the slot when one prepared ownership question would fit.

saying these in an interview costs you the question

  • Opening the question window with equipment, snacks or perks
  • Treating the closing window as small talk after the real round
  • Bringing no questions and calling the role already clear
  • Asking strategy-flavoured questions with no concrete subject in them
  • Asking something you cannot say anything of your own about

context

open as a page

When a candidate asks how technical decisions are made and revisited, what does that reveal to a behavioral interviewer?

level: middleimportance: must knowfreq 63%

basics

~20 s

It signals the candidate has lived with a decision being reversed. The subject is the team's process over time rather than the asker's own comfort, and the revisiting clause is the part that cannot be answered with a slogan.

open as a page

How should a candidate word a question about a team's incident postmortem culture so the answer describes practice, not policy?

level: seniorimportance: should knowfreq 51%

basics

~20 s

Anchor the ask to countable recent incidents and to artefacts: how many of the last several incidents produced a written postmortem, who wrote them, and what changed afterwards. A question about whether the culture is blameless invites a policy answer instead.

open as a page

Which closing questions evidence real scope when you are being considered one level above your current title?

level: principalimportance: nice to knowfreq 44%

basics

~20 s

Ask about the boundary you would own and the horizon you would plan on: where this team's ownership stops, and how many quarters of the plan are actually firm. Questions pitched several steps above the role read as posturing rather than as scope.

open as a page