Skip to content
Question Vault?
Free to readNo accountNo email wallNo invented statisticsNo ads on medical, legal or end-of-life pagesCopy or print any set and take it with you
03 · Professional & Academic

Unique Questions to Ask During Recruitment

Twenty questions for a candidate being recruited, covering whether the role is real, what it pays, who decides, and what the team is like day to day, with the answers that should give you pause.

20 questions · each with a note on why · conversation guide

The questions

Open any question for the note

  1. Is the role approved and funded, or still being scoped?

    Why ask it

    Ask on the first call. Recruiters do run searches for headcount that is not finalised, and candidates lose months in processes that quietly stall. A confident yes with a start date attached is what you want to hear.

  2. Is this a new role or a backfill, and what happened to the person before me?

    Why ask it

    A backfill after an internal promotion reads very differently from the third person in the seat in two years. If the answer is vague about where the last person went, ask directly whether they left the company or moved teams.

  3. What salary range are you working with for this level?

    Why ask it

    Ask early, before you invest four rounds. Recruiters usually know the band, and a refusal to share any range while pressing you for your current number is a real signal about how the offer conversation will go.

  4. How is the offer usually structured: base, bonus, equity?

    Why ask it

    The shape matters as much as the total. Ask what portion is guaranteed, when a bonus is paid, and what the vesting schedule is, because a large headline figure can be mostly contingent.

  5. Who's in the interview loop, and what will each of them be looking for?

    Why ask it

    Any competent recruiter can tell you this and it is the single most useful preparation you can get. If nobody can describe what each interviewer assesses, the process is likely to be unstructured, and unstructured processes produce inconsistent decisions.

  6. What's the timeline from here, and when do you expect to decide?

    Why ask it

    Gives you something to hold them to and lets you sequence other processes. Note the date, and if it passes in silence, that is information about how the company treats people it has not yet hired.

  7. Who would I report to, and how long have they been in that role?

    Why ask it

    A manager appointed two weeks ago, or one who is themselves interviewing elsewhere, changes the job entirely. Ask to speak to them before any final decision, and treat a refusal as a serious answer.

  8. How big is the team, and how much has it changed in the last year?

    Why ask it

    Growth and churn look identical in a headcount number. Ask how many people joined and how many left, and count the difference yourself rather than accepting a description of the team as dynamic.

  9. What's made the strongest candidates stand out so far?

    Why ask it

    You are asking for the scoring rubric in plain language, and most recruiters will give it to you because it improves their pipeline. Use the answer to decide what to lead with in the next round.

  10. What's caused people to be turned down at the final stage?

    Why ask it

    More useful than the previous question, because the failure modes are specific: a bad system design round, a values interview, an inability to describe their own contribution. Vagueness here often means the bar is not written down anywhere.

  11. What does the first ninety days look like, and who decides whether it went well?

    Why ask it

    The second half is what matters. If success is judged by someone you have not met, or by a metric nobody can state, you are being hired into a job whose definition is still open.

  12. What do people find harder about this job than they expected?

    Why ask it

    Phrased so that answering honestly is not disloyal, which is why it works better than asking about challenges. Legacy systems, slow approvals and a demanding internal customer are all normal answers; no answer at all is not.

  13. How much of the week is meetings, and how much is uninterrupted work?

    Why ask it

    Ask for the actual shape of a Tuesday. People underestimate their own meeting load, so a specific answer with a number in it is more trustworthy than an assurance that they protect focus time.

  14. How often does the team actually finish and release something?

    Why ask it

    Cadence tells you how the work really runs, faster than any statement of values does. If the answer is that a release has been coming soon for several months, ask what is holding it up, because the same thing will hold up your first project.

  15. What's the office expectation in practice, not in policy?

    Why ask it

    Written policy and lived reality diverge here more than on any other subject. Ask how many days the team is actually in and whether the people who get promoted are the ones who are visible.

  16. At the last review cycle, how many people on this team were promoted?

    Why ask it

    A factual question about advancement that cannot be answered with a description of a career ladder. If nobody has been promoted in two cycles, the ladder exists on paper only.

  17. How does the company handle it when someone isn't working out?

    Why ask it

    You are asking whether there is a fair process or a sudden exit, and the answer applies to you as much as to anyone else. Listen for whether managers are described as having conversations early or as documenting problems.

  18. What would make you hesitate about me right now?

    Why ask it

    Best asked at the end of a later round, to the hiring manager rather than the recruiter. It is the only way to address a concern before it is discussed without you in the room, and most people will name something real if you ask calmly.

  19. If I turned this down, what would you think I'd misunderstood about the role?

    Why ask it

    An unusual framing that gets you the honest pitch instead of the polished one, because it invites them to correct a misconception rather than sell. It also surfaces what they think the weak point of the role is.

  20. What can I send you that would help you make the case for me internally?

    Why ask it

    Treats the recruiter as an ally, which is often accurate, since their job depends on filling the role. A specific request in return, such as a writing sample or a reference, tells you they are actively working your candidacy rather than parking it.

Working a Recruitment Process

Practical guidance for the conversation itself

Ask the Right Person

The recruiter

Best on compensation bands, the interview loop, timelines and process. They usually cannot speak to the technical detail of the work, so do not judge the role by their description of it.

The hiring manager

Best on the first ninety days, how success is judged, and what the team is genuinely struggling with. Save the question about hesitations for them, and ask it near the end.

Peers on the team

Best on meetings, shipping cadence, office reality and what happens when someone raises a problem. This is where you find out whether the manager's description matches the week.

Whoever sends the offer

The only source that counts on money, start date and title. Anything agreed verbally should appear in the written offer before you resign anywhere.

When to Ask What

First call, fifteen minutes

  1. 1Is the role approved and funded, and is it new or a backfill.
  2. 2What range are you working with at this level.
  3. 3Who is in the loop and what is the timeline.

Middle rounds

  1. 1What the first ninety days look like and who judges them.
  2. 2What people find harder than expected, and how the week is actually shaped.
  3. 3Promotions at the last cycle, and how underperformance is handled.

Final round and offer stage

  1. 1What would make you hesitate about me right now.
  2. 2How the offer is structured, and what portion is guaranteed.
  3. 3What I can send you to help you make the case internally.

Answers That Should Give You Pause

  • We are like a family here. In practice this usually describes blurred boundaries and an expectation that you will absorb problems personally rather than raise them.
  • A refusal to name any salary range while asking repeatedly what you currently earn. It tells you the offer will be anchored to your history rather than to the work.
  • Nobody can describe what the first ninety days involve. The role is still being invented and you would be inventing it while being judged on it.
  • A hiring manager you are not allowed to speak to before deciding. This is the person who determines whether the job is good, and there is rarely a good reason to keep them away.
  • The last person left and nobody will say where they went. Ask once more, plainly. If it stays vague, assume the answer is unflattering.
  • A deadline on the offer that is shorter than the process took. Urgency at the end of a slow process is a pressure tactic, and it is reasonable to ask for a week.

Keeping Track

  • Keep one page per company with the range, the names, the dates promised and the answers you were given. By the fourth process they blur together.
  • Write the answers down the same day, in their words. Specific phrases are what you will want when comparing two offers.
  • Ask the same three questions everywhere, so you are comparing answers rather than impressions.
  • Get anything that affects your decision into writing, including remote arrangements, start date and title. Verbal agreements do not survive a change of manager.