Questions to Ask in a Phone Interview
Questions to ask during a phone interview, where the call is short and the goal is to find out fast whether the role is worth more of your time: how it was scoped, what the first quarter demands, the pay band and the process ahead. The list is for candidates choosing which phone interview questions to ask an employer in the few minutes they get. What to ask in a phone screen, when the caller is a recruiter who knows the range and the process better than the work, has a group of its own.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The role
How did this role come about: is it a backfill or new headcount?
Why ask it
A backfill means there is a template and usually a reason the last person left. New headcount means the scope may still be negotiable, which is an opening for you rather than a problem.
What would you want this person to have accomplished by the end of the first quarter?
Why ask it
A specific answer means someone has a plan. If the answer is to get up to speed, the job has not been defined yet, and that ambiguity will land on whoever takes it.
What is the team working on right now?
Why ask it
Current work is easier to describe honestly than culture, and it gives you something concrete to react to for the rest of a short call.
Who would I report to, and how many people are on the team?
Why ask it
Get the manager's name so you can prepare for the next round. A manager with fifteen direct reports will give you far less attention than one with four.
Which parts of the job description matter most in practice?
Why ask it
Postings are usually assembled from several sources. Hearing which two or three requirements are load-bearing tells you what to emphasize and whether a gap is fatal.
Is the job description still accurate, or has the role changed since it was posted?
Why ask it
Descriptions are often recycled from an older vacancy or written by someone other than the manager. Asking gives the recruiter permission to tell you which parts are aspirational, and that is usually where the interview questions will come from.
What's a real part of this job that isn't in the posting?
Why ask it
Every role carries unlisted work: a legacy system nobody wants, a weekly report, an awkward stakeholder. Managers usually answer this candidly because they would rather you know now than leave in six months.
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.
How does this role connect to what the company is trying to do this year?
Why ask it
A role on the critical path gets resourced and defended. One that nobody can connect to a stated priority is the kind that disappears in a reorganization.
How long has this been open, and what has made it hard to fill?
Why ask it
This is the first question that can sting, so ask it once the call has some rapport. A role open six months has a reason: the range sits below market, the requirements combine two jobs, the manager is hard to satisfy, or the location is a problem. A candid answer here is a good sign about the culture.
Why did the last person in this role leave?
Why ask it
Reasonable to ask directly. A promotion, a relocation or a poor fit are all fine answers. A pause followed by a general remark about culture is worth remembering.
How long do people usually stay in this role before moving?
Why ask it
Eighteen months and four years mean different things. Follow up on where the movers went, inside the company or out of it.
What is it about this job that makes people turn it down?
Why ask it
Recruiters and managers both have an answer to this and are usually candid, because they have heard it several times. Whatever they name is the thing you will be living with.
If I take this job and it goes badly, what will have gone wrong?
Why ask it
It asks for the failure mode rather than the pitch, and it is a fair question to put to anyone hiring. Vague answers here usually mean nobody has thought about it.
Would you take this job if you were me, and what would make you hesitate?
Why ask it
Direct, and most people answer it more honestly than they intend to. The hesitation half is the part to listen for.
Phone screen
How long do we have, and what would be most useful to cover?
Why ask it
Sets the clock openly so neither of you is guessing, and it often gets you their agenda in one sentence. On a short screen, knowing they need fifteen minutes on your background changes when you ask everything else.
Are you the hiring manager, or will you be passing your notes on to them?
Why ask it
A recruiter screen and a hiring manager screen are different conversations. A recruiter is checking basics: range, location, work authorization, one or two must-have skills. A manager is testing whether you can do the work. Knowing which you are in tells you whether to speak in headlines or in detail.
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.
What in my background made you want to talk to me?
Why ask it
Tells you which part of your experience they are buying, so you can lead with it later. If they struggle to answer, you may have been included to widen a shortlist.
Has the budget for this role been approved?
Why ask it
Some searches run on an anticipated opening or are used to benchmark against an internal candidate. A hesitation here is worth more than any other single answer in a screening call.
How many candidates are you speaking to, and where are you in the process?
Why ask it
It tells you whether you are early enough to be shaped into the role or arriving after a favorite has emerged. Screeners usually answer it plainly because it is a scheduling fact rather than a judgment.
Are there internal candidates in the process?
Why ask it
Roles are sometimes advertised while an internal favourite is already lined up, and recruiters will often say so if asked directly. It does not always mean you should withdraw, but it should change how much unpaid work you are willing to do.
How does the hiring manager like to work with people?
Why ask it
Recruiters see managers across many hires and will often describe a style plainly: hands-off, detail-focused, hard to get time with. This is one of the few chances to hear it from someone with nothing to sell you.
Day to day
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.
How much of a normal week here is meetings versus focused work?
Why ask it
Calendars are almost always worse than advertised. If the honest answer is five hours of standing meetings a day, you know now whether this is the job you thought you were applying for.
Where does the work come from: a queue, a manager, or the person themselves?
Why ask it
This is the difference between executing a list and setting your own agenda. Candidates who assume the wrong one are the ones who leave in six months.
How much of this job is fixing existing work compared with building something new?
Why ask it
The proportion is almost never in the posting, and it is frequently the difference between a job you would enjoy and one you would not.
What tools and systems does the team work in?
Why ask it
The named stack tells you how much ramp-up you face and whether the environment is being built or maintained. It also gives you something specific to study before the next round.
How is the work split between this team and the ones next to it?
Why ask it
Overlapping charters cause most day-to-day friction in a job. Ask where the seams are and who settles arguments across them.
Who would I work with most closely, and what do they need from this role?
Why ask it
The answer maps the job onto real people and often reveals a difficult interface: a team that has been waiting on support, a partner group with a competing plan. Ask for roles rather than names if the manager hesitates.
How many days a week is the team in the office?
Why ask it
Ask what is currently enforced rather than what the policy says, and whether it has changed in the past year. Office rules move faster than job descriptions do.
What part of this job do people find hardest?
Why ask it
Interviewers usually answer this one straight, and the difficulty they name tells you whether it is the kind you find interesting or the kind you have left jobs over.
Team and manager
How does the team know whether it is doing well?
Why ask it
If the measure is something the team controls, decisions probably make sense internally. If it is a company-level number, expect priorities to swing whenever that number does.
What has changed on this team in the past year?
Why ask it
New leadership, departures and a shifted mandate are all worth knowing before you commit to four more conversations.
How long has the manager for this role been leading the team?
Why ask it
A manager three weeks into the job will reshape the role whatever the posting says. Long tenure paired with heavy turnover underneath is a different kind of warning.
What does the manager's first month with a new hire usually look like?
Why ask it
Close guidance and wide autonomy both work, but only if they match what you need. Ask what the most recent new hire actually got.
How does feedback happen between formal reviews?
Why ask it
Ask for the mechanism, whether that is a weekly one-to-one or something looser. Teams with no answer tend to save everything up for the annual review.
What happens here when a deadline is going to slip?
Why ask it
Shows whether bad news travels early or late. This is the answer that predicts what your evenings will look like.
What do people say on the way out of this team?
Why ask it
Exit conversations are the one place employers hear the truth, and interviewers remember them. A claim that nobody leaves is itself an answer.
Pay and terms
Where does the salary band for this role sit?
Why ask it
Asking on an early call is normal and can save both sides several weeks. A flat refusal to name any range is itself worth noting.
Where in the range would someone at my level land, and what moves someone up it?
Why ask it
More useful than the range itself, which is usually wide enough to be meaningless. If nobody can say what moves a person up it, assume nothing does.
What is in the package besides base pay?
Why ask it
Bonus, equity, pension and leave are exactly the things a recruiter is equipped to answer. Asking early saves discovering a gap after three rounds.
What is the title and level, and what sits directly above it?
Why ask it
Titles compress and vary wildly between companies, so the level matters more than the words. Knowing what sits above tells you what promotion means here, and whether you would be joining at the ceiling of a band with nowhere to move.
How do performance reviews and pay increases work here?
Why ask it
Cycle timing, whether increases are budgeted annually, and who decides. All of it is easier to ask before an offer than after you have accepted one.
How does someone in this role get promoted, and who decides?
Why ask it
You want mechanics: cycle timing, whether an open headcount is required, who signs off. Merit with no process attached often means promotions happen only when someone threatens to leave.
What are the hours, and is there any on-call or travel?
Why ask it
Cheap to ask on a screen and expensive to discover later. Ask how often on-call comes round, whether it is paid, and what proportion of nights away a typical month involves, since averages hide the busy quarter.
Next steps
What does the rest of the process look like, and what is the timeline?
Why ask it
This is what a phone call is best placed to answer. Knowing the number of rounds and the format lets you plan around other conversations instead of guessing.
Who would I be meeting at each stage, and what does each of them care about?
Why ask it
Recruiters will often tell you exactly what a particular interviewer focuses on, which is the most useful preparation you can get. Very few candidates ask, so the information is usually sitting there unused.
Is there a test, presentation, or take-home task, and how long does it take?
Why ask it
Unpaid work of ten or twenty hours is worth knowing about before you commit. The stated duration is also worth noting, since tasks described as two hours frequently are not.
What has made strong candidates fall short in later rounds?
Why ask it
Interviewers often answer this candidly, and it tells you exactly what to prepare for, whether that is a case exercise, a portfolio walkthrough or a systems discussion.
Is there anything you would want me to prepare for the next conversation?
Why ask it
A strong closer. Screeners often name the specific topic the next interviewer will push on, which can be the most valuable thing you take from a twenty-minute call.
Is there anything in my background you would want clarified before the next round?
Why ask it
This gives you a chance to answer an objection while you are still on the call, rather than losing to it silently in someone's written notes.
Was anything I said unclear on this line?
Why ask it
Phone interviews lose words to bad connections and interviewers rarely ask you to repeat yourself. This offers one clean chance to fix an answer that landed badly, and it takes ten seconds.
What is the best way to reach you if something comes up?
Why ask it
Phone screens often end abruptly. A name and a channel saves you a week of wondering whether silence means rejection.
Handling a Short Call Well
Practical guidance for the conversation itself
Setting Up the Call
Have the posting open and annotated
Mark the two or three requirements you are strongest on and the one you are weakest on. On a call with no visual cues, you will not remember to steer toward them unless they are in front of you.
Pick three questions, not seven
Most phone interviews leave five minutes for your questions. Decide in advance which three matter, and lead with the one that could end your interest in the role.
Take the call somewhere you can be heard
A dropped call in the middle of an answer costs more than it should. Use a landline or a strong signal, and have a number the interviewer can call back on.
During the Call
- Ask your salary and process questions before the call runs out, not after
- Write down names and titles as they are mentioned, spelled out if needed
- Pause a beat before answering, since interruptions are harder to recover from on the phone
- If a question is vague, ask which part they want you to focus on rather than answering all of it
- Note the words the interviewer uses for the team and the work, then use those words in the next round
Common Mistakes
Treating it as a formality
Phone screens eliminate more candidates than any later stage. Prepare a two-minute account of your recent work and practice saying it out loud before the call.
Saving every question for the hiring manager
Pay range, location expectations and process timeline are usually best answered on this call. Holding them back can cost you three weeks on a role that was never viable.
Answering culture questions in the abstract
Without body language, general answers sound evasive. Anchor each answer in a specific project, decision or number.
Ending without knowing the next step
Ask who decides, when you will hear, and what happens if you do not. Silence after a phone screen is common and mostly means nothing.