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 Interviewer During Phone Interview

Questions for a phone interview with a hiring manager, when you have ten minutes at the end and no body language to read. They cover scope, reporting lines, hours, pay range, and next steps, so you leave the call knowing whether the job is worth a second round.

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 this role covers day to day?

    Why ask it

    A manager who answers with project names and standing meetings has thought about the job. One who reads the posting back to you may be hiring against a gap they have not defined yet, which usually becomes your problem in month two.

  2. Is this a new position, or would I be replacing someone?

    Why ask it

    New roles come with undefined scope and no precedent for what good looks like. Backfills come with a predecessor's reputation, good or bad. The two need completely different follow-up questions.

  3. What would you want this person to have done by the end of their first six months?

    Why ask it

    Vague answers here are the clearest early warning you can get. If nobody has decided what the hire is for, priorities will shift under you and reviews will be judged against a target set after the fact.

  4. Who would I report to, and who else would I work with every week?

    Why ask it

    The named reporting line often differs from where the work actually comes from. Two or three informal bosses is a workable arrangement, but only if you know about it before you start.

  5. What is the team struggling with right now that this hire is meant to help with?

    Why ask it

    This gets you the honest version of the job description. Answers about backlog, a departure, or a system nobody wants to own tell you what your first year will actually consist of.

  6. What would onboarding look like for this role?

    Why ask it

    Ramp-up ranges from a planned first month with a named buddy to a laptop and a backlog. A manager who has thought about it will answer concretely, and a blank usually means you would be designing your own start.

  7. How does work get assigned and prioritised on the team?

    Why ask it

    You are checking whether there is a single queue or five people who can drop work on you. A team that cannot describe its intake process is a team where the loudest requester wins.

  8. How often would we meet one to one, and how do you prefer to be kept updated?

    Why ask it

    Managers reveal a great deal here. A firm weekly slot and a preference for written updates is a different working life from "my door is always open," which often means you will be chasing them.

  9. How much of this job depends on people outside your team?

    Why ask it

    The hidden difficulty of a role usually sits in the handoffs. Ask which teams you would rely on and whether those relationships currently work, because a broken one is not something you can repair from your side.

  10. What has turnover on this team looked like over the last two years?

    Why ask it

    This is uncomfortable and worth asking on the phone, where it costs you less. A manager who knows the number and can explain the departures is a much better sign than one who deflects to company growth.

  11. How do decisions get made when the team disagrees about an approach?

    Why ask it

    The answer tells you whether authority is clear or contested. "We keep talking until we reach consensus" often means projects stall until someone senior intervenes.

  12. What would I have to work with: budget, tools, anyone to hand work to?

    Why ask it

    Managers describe ambitious targets far more readily than they mention the shared licence and the frozen budget. Asking about the means alongside the goals separates a funded plan from a wish.

  13. What is the expectation on hours, and how often do evenings or weekends come up?

    Why ask it

    Asking for frequency rather than policy gets a concrete answer. "Around a launch" is reasonable; an answer about people who are passionate about the work is a warning.

  14. Has the salary range for this role been set, and can you share it?

    Why ask it

    A phone interview is the cheapest point to find out you are misaligned on money. A manager who cannot say and does not offer to find out is telling you how much control they have over their own hiring.

  15. How is performance reviewed here, and when does the cycle land?

    Why ask it

    Ask what evidence the review draws on and what the calendar is. Someone who starts two months before a cycle closes is often judged on a partial year, which matters when pay decisions hang off it.

  16. Where does this team sit in the company's plans for the next year?

    Why ask it

    You want to know whether you would be joining something being invested in or something being maintained. Both can be fine jobs; only one of them is a growth job.

  17. How long have you been leading this team, and how did you come into it?

    Why ask it

    A manager's tenure and route in predict how much they can get approved and how well they can shield the team. It is also an easy question that tends to loosen up the closing stretch of a call.

  18. What tends to make someone unsuccessful in this role?

    Why ask it

    Hiring managers answer this candidly because it protects them from a bad match. Answers about needing to chase people, or not getting comfortable with ambiguity, describe the real friction in the job.

  19. What are the next steps, and who else would I meet?

    Why ask it

    Beyond logistics, the shape of the remaining process tells you how the company decides. Five more rounds with no clear owner suggests decisions here are slow and diffuse.

  20. Is there anything in my background you would like me to explain further?

    Why ask it

    This is the one chance to address a doubt before it becomes a rejection you never hear the reason for. Phone screens end fast, and an unspoken concern usually goes unresolved otherwise.

Handling the phone interview

Practical guidance for the conversation itself

Set the call up properly

Have the questions in front of you

Nobody can see your notes. Print or open your four or five questions and cross them off as they get answered during the conversation, so you do not ask something they already covered.

Confirm how long you have

Ask at the start whether it is thirty minutes or an hour. It determines whether you save your questions for the end or fold one or two into the conversation as it goes.

Take the call somewhere you can write

Phone interviews are where salary ranges, start dates, and process details get mentioned once and never repeated. Write numbers down as you hear them.

What to listen for without visual cues

  • Length of pause before an answer. On the phone, hesitation about turnover or hours is the clearest signal you get.
  • Whether they answer in specifics or categories. "We shipped the billing rewrite in March" beats "we work on high-impact projects."
  • Whether the manager talks about the team as people with names, or as headcount.
  • Any mismatch between the recruiter's description of the role and the manager's. Ask about the difference directly.
  • Who they say the job reports to, compared with what the posting said.

Common pitfalls

Saving every question for the end

Calls run out of time. Ask the one question whose answer would make you withdraw early, not last.

Asking eight questions in a row

It turns the last ten minutes into an interrogation. Ask, respond to the answer, then follow up. Two questions explored properly beat six skimmed.

Skipping money because it feels early

The range question costs nothing on a screening call and saves both sides three rounds of interviews when the numbers cannot work.