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

Questions to Ask Phone Screen

A phone screen is short, and its job is to decide who moves forward. These twenty questions are written for the person running the call: what to ask a candidate, in roughly what order, and what the answers usually tell you about fit, timing and pay.

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

The questions

Open any question for the note

  1. Can you walk me through what you actually do in a normal week at your current job?

    Why ask it

    A resume describes scope; a week describes reality. Listen for whether the routine matches the seniority on paper, and for what they hand off to other people.

  2. What made you apply for this particular role?

    Why ask it

    The signal is specificity. Growth and new challenge are filler; naming the product, the team, or a line in the posting suggests they chose you rather than mass applying.

  3. What do you know about us so far?

    Why ask it

    You are not testing recall. Someone who skimmed the homepage will need convincing later, while someone who mentions a competitor or a recent change is probably already weighing you against another process.

  4. Which part of the job description looked like the strongest match for you?

    Why ask it

    Lets the candidate point you at the evidence worth digging into, which saves half the call. If they pick something peripheral to the actual job, the fit is thinner than the resume suggested.

  5. Which part of it looked like a stretch?

    Why ask it

    Most people will name something, and what they name shows how accurately they read themselves. Insisting nothing is a stretch usually means they have not read the posting closely.

  6. Tell me about a piece of work from the past year you would want me to pass on to the hiring manager.

    Why ask it

    Framing it as something to pass along produces one curated example instead of a career history. Weaker candidates describe a project; stronger ones describe a decision they made inside it.

  7. Take the main tool on your resume: what have you actually built or run with it?

    Why ask it

    Closes the gap between keywords and hands-on use. Answers like I supported that system usually mean they were nearby while someone else owned it.

  8. How much of that work was yours, and who else was involved?

    Why ask it

    Checks for inflated credit without making it an accusation. People who did the work name colleagues easily; people who did not tend to claim all of it and then cannot describe the parts they skipped.

  9. What are you hoping is different about your next job?

    Why ask it

    More useful than asking why they are leaving, because it points forward and gets a less rehearsed answer. If what they want is the one thing you cannot offer, better to know in minute nine than at offer stage.

  10. What is your notice period, and what date could you realistically start?

    Why ask it

    Notice periods, work authorization and childcare all surface here. A start date three months out may not survive the hiring manager's timeline, and that is cheap to learn now.

  11. What salary range are you working with?

    Why ask it

    Asking directly beats guessing, and it stops both sides spending four rounds on a number that was never going to work. Note whether they give a range or one firm figure, since that shapes any later negotiation.

  12. The team works in the office three days a week. How does that sit with you?

    Why ask it

    Say the real arrangement out loud rather than repeating the word flexible from the posting. Commute and office days are among the most common late reasons candidates walk away.

  13. Are you interviewing anywhere else, and how far along are those conversations?

    Why ask it

    Tells you what timeline you are competing against. Someone at final stage elsewhere needs a compressed loop or you will lose them by simply being slower.

  14. What kind of manager gets the best work out of you?

    Why ask it

    Better than asking about work style in the abstract. The answer usually describes the manager they have now, either as a template or as a complaint, and you can test it against the actual hiring manager.

  15. Tell me about something that went badly, and what you did next.

    Why ask it

    The follow-up matters more than the failure. Naming the mistake and the repair is a good sign; putting the whole thing on a former employer suggests you will hear the same story about your company later.

  16. What did you have to learn quickly in your last job, and how did you go about it?

    Why ask it

    Ramp speed is one of the few things a screen can genuinely predict. Look for method: who they asked, what they read, how long it took before they were useful.

  17. What would have to be true for you to accept an offer here?

    Why ask it

    Surfaces the real deciding factors, which are often title, remote days or one specific benefit rather than base pay. It also hands you the shape of an offer they would say yes to.

  18. Is there anything on your resume you would like to explain before I write this up, like a gap or a short stint?

    Why ask it

    Asked plainly, most candidates are relieved to explain. It stops the hiring manager inventing a worse story from the dates, and it protects people whose gap was illness or caring for family.

  19. What questions do you have for me?

    Why ask it

    Their questions are often a better signal than their answers. No questions at all after twenty minutes usually means either low interest or no preparation, and it is worth asking which.

  20. If we move ahead, is there anything you need from us on scheduling or on how the interviews are run?

    Why ask it

    Catches accommodations, religious observance, time zones and travel limits before scheduling becomes awkward. It also tells candidates the process is run by people who plan.

How to use these questions

Practical guidance for the conversation itself

How 25 minutes usually splits

A screen is not a shorter version of the full interview. Roughly two minutes to introduce yourself and the role, five on what the candidate does now, ten gathering evidence against the two or three requirements that genuinely matter, five on logistics such as pay, notice and location, and five for their questions. If you find yourself assessing depth of skill, you are doing the hiring manager's round for them and will run out of time for the things only you can check.

Ask the deal-breakers early

  • Pay range, start date and location decide more outcomes than skills do. Cover them in the first half so a mismatch ends the call kindly instead of at round four.
  • Give your range or your office policy first where you are allowed to. Candidates answer more honestly when they are not guessing at a hidden number.
  • Anything the role legally requires, such as a license, work authorization or a clean driving record, belongs on the screen rather than in an offer letter.
  • If a deal-breaker appears, say so on the call. Telling someone the band tops out below their number is more respectful than silence followed by a rejection email.

Common pitfalls

  • Do not read the job posting aloud. Candidates have already read it, and it burns the minutes you need for their answers.
  • Avoid two questions in one sentence. On the phone people answer the second one and forget the first.
  • Do not fill pauses. The more honest half of an answer usually arrives after a few seconds of silence.
  • Resist judging the first two minutes. Phone audio flattens warmth, and nervous openings often settle once someone starts describing real work.
  • Ask every candidate for the role the same core questions. Screens that wander are the easiest place for bias to enter and the hardest to defend afterwards.

Writing it up

  • Take notes during the call rather than after. By the third screen of the day, candidates blur together.
  • Record quotes instead of impressions. Owned the migration for six months is useful to a hiring manager; seemed sharp is not.
  • Note which requirements you probed and what evidence you got for each, including where evidence was thin or missing.
  • Pass on the practical constraints: notice period, range, competing offers. That is the part hiring managers most often say never reached them.