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

Best Questions to Ask in a Phone Interview

Twenty questions for a first phone call with a recruiter or hiring manager, covering what the job involves, what they screen for, how the team works, how performance is measured, and what the remaining steps are.

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

The questions

Open any question for the note

  1. What does a typical week look like for someone in this role?

    Why ask it

    A week is easier to describe accurately than a day, and it exposes the recurring meetings and reporting cycles that make up more of the job than anyone lists.

  2. What are you screening for on a call like this?

    Why ask it

    Recruiters usually answer directly, and it tells you what to emphasize for the rest of the conversation instead of guessing at their criteria.

  3. Is this a new position or a replacement?

    Why ask it

    A new role means you help define it and may lack a template. A replacement means there is a standard you will be measured against from week one.

  4. What are the two or three things this person has to be good at?

    Why ask it

    Forces a shortlist out of a long requirements section. If the answer is longer than four items, the role has not been scoped and may be two jobs.

  5. Who is on the team, and who would I report to?

    Why ask it

    Names, roles, and team size are basic facts a screener should know. Difficulty here suggests the recruiter is working from a document, not a conversation.

  6. How would I know if I was doing well after six months?

    Why ask it

    Asks for observable signals rather than metrics, which is a question people answer more honestly. Watch for whether it is output, hours, or being liked.

  7. What is the most common reason candidates do not make it past the next stage?

    Why ask it

    Recruiters see the pattern and often share it, which is the closest thing to being told the marking scheme before the exam.

  8. What does onboarding look like, and who would train me?

    Why ask it

    A named person and a plan is a real answer. Where training means shadowing whoever is free, expect a slow and uneven first quarter.

  9. What salary range has been approved for this role?

    Why ask it

    Better asked on the first call than after four rounds. If the recruiter deflects twice, treat the range as lower than you would like.

  10. How much flexibility is there on hours and location?

    Why ask it

    Ask about both, since one is often traded for the other. The word 'currently' in the answer means the arrangement is not settled.

  11. What is the biggest thing the team is trying to fix at the moment?

    Why ask it

    The problem they name is what you would be hired into, and it is more informative than any description of team culture.

  12. How does the team communicate day to day?

    Why ask it

    Constant chat, scheduled standups, and long email chains all suit different people. Mismatch here is a common reason good hires are unhappy.

  13. What do new hires usually find hard in the first month?

    Why ask it

    Answers tend to be specific and useful: a complicated approval chain, an undocumented system, a lot of names to learn. It also shows they pay attention to new joiners.

  14. How long have most people on the team been there?

    Why ask it

    A team where everyone arrived in the last year is either growing fast or losing people fast, and the follow-up question sorts out which.

  15. What would you change about this role if you could?

    Why ask it

    Invites the honest complaint. Hiring managers answer this better than recruiters, so save it if you get a second call.

  16. Is there travel involved, and roughly how much?

    Why ask it

    Travel is frequently omitted from postings and is the detail most likely to make an otherwise good offer unworkable.

  17. What are the remaining stages, and who would I meet?

    Why ask it

    Lets you plan preparation and compare processes if you are interviewing elsewhere. A long undefined process often means an undecided hiring committee.

  18. When are you hoping to have someone start?

    Why ask it

    Urgency affects your leverage. A start date months out means you have time; a date in two weeks means the decision is being made quickly.

  19. Is there anything on my resume that gave you pause?

    Why ask it

    Screeners are usually the ones with the concern, and this is your only opportunity to answer it before it becomes a rejection note.

  20. What is the best way to reach you if something else comes up?

    Why ask it

    Gets you a direct channel rather than a general inbox, which matters most if you later need to move faster because of another offer.

Phone Interviews Are Short

Practical guidance for the conversation itself

Working the Time Limit

Pick four, not twenty

A first call usually leaves five minutes for your questions. Choose the four whose answers would change whether you continue, and save the rest.

Ask the screening question first

Finding out what they are assessing early lets you steer the remainder of the call, which no other question in the list can do.

Say the numbers back

Repeat the range, start date, and stage count out loud before you hang up. It confirms what you heard and catches misunderstandings while they are cheap.

Recruiter or Hiring Manager

Recruiter

Ask about range, process, stages, timeline, and what gets candidates rejected. They see the whole funnel and are usually candid about it.

Hiring manager

Ask about the week, the problem the team is fixing, what they would change, and how they would judge six months. They own those answers.

Either

New position or replacement, team size, travel, and onboarding. If the two people give different answers, that is worth following up on.

Common Pitfalls

Saving every question for later rounds

The range and the travel requirement can end the process. Asking them on call one saves both sides a month.

Asking a recruiter technical questions

It puts them in an awkward position and produces nothing usable. Ask who on the team could answer it in the next round instead.

Sounding like a list

Reading questions in order without responding to the answers is obvious on a phone line. React to what they say, then move on.