Questions to Ask During Phone Interview
For the call with the person you would report to, where the useful subject is the work rather than the process. These twenty stay on what the job actually involves: what lands on your desk, what is planned against what arrives unannounced, which decisions are yours, what the team owes the rest of the company, and what a bad version of this job looks like. They assume pay, location and the number of rounds have already been covered by a recruiter, or will be.
The questions
Open any question for the note
What does the person in this role spend most of their week doing?
Why ask it
Job adverts describe responsibilities in the abstract; this asks for the calendar. If the answer is mostly meetings and coordination when you were expecting hands-on work, better to learn it in the first ten minutes.
What would land on my desk in the first week?
Why ask it
Managers answer this concretely because they are already thinking about it. It also exposes whether the job is defined or still being invented.
What are the two or three things you need this person to get done in the first six months?
Why ask it
Managers who have thought the role through answer this in specifics. A vague answer usually means the priorities are not settled, and you would be arriving into someone else's unresolved argument.
Which parts of this work are done alone, and which are done with other people?
Why ask it
The split matters more to daily life than the job title does, and it is rarely in the posting. It also tells you how much of your week is other people's calendars.
Who does this role depend on to get anything done?
Why ask it
Most difficulty in a job comes from the dependencies rather than the tasks. If the answer names three other teams, ask how those relationships currently work, because that is what your week will consist of.
How do decisions get made on your team, and what needs your sign-off?
Why ask it
This is the clearest signal about autonomy you will get, and it is more revealing than asking whether the culture is empowering. Note the gap between what they say people can decide and what they describe approving.
What would you expect me to handle without checking with you?
Why ask it
Phrased this way, the answer describes the actual boundary of the role. Managers who cannot name anything are usually describing a job with less scope than the title suggests.
How do you prefer to work with the people who report to you?
Why ask it
You are asking about their management style without inviting a rehearsed answer about being supportive. Follow up on the frequency and purpose of one to ones, because that is where the style shows.
What is the split between planned work and things that arrive unannounced?
Why ask it
A team that is mostly reactive requires a very different temperament from one running a roadmap. The answer also predicts how realistic those six-month priorities are.
How does the team decide what to drop when everything is urgent?
Why ask it
Every team faces this and the good answers are specific: a named owner, a regular triage meeting, an explicit rule. If nothing is ever dropped, the overflow is going somewhere, usually into people's evenings.
What tools and systems does the team actually work in day to day?
Why ask it
The answer tells you what the learning curve looks like and how mature the team's process is. Several overlapping systems for the same job usually signals unresolved disagreement about how to work.
What does this team produce that the rest of the company depends on?
Why ask it
Puts the role in the wider machine, which is where you find out whether the work is load bearing or optional. Anything nobody depends on tends to get cut first.
Where do you expect this team to be different in a year?
Why ask it
You are testing whether the manager has a plan or is holding a line. Their answer also tells you whether the role has somewhere to go or exists to keep the current arrangement running.
What part of this job do people underestimate?
Why ask it
This gets you the unglamorous reality: the reporting, the internal negotiation, the volume of small requests. Managers usually answer honestly because they would rather not hire someone who quits over it.
How do you handle it when someone on your team makes a costly mistake?
Why ask it
The answer tells you whether the team is safe to be honest in, which affects everything else. Look for a concrete example rather than a statement about blameless culture.
How much of this job is fixing what exists rather than building something new?
Why ask it
Two very different jobs are often advertised with the same words. Ask for a rough percentage and you will get a straighter answer than you expect.
How would you describe the team to someone about to join it?
Why ask it
You are inviting a description of colleagues rather than a description of culture, which is harder to answer with slogans. Details about individuals suggest a manager who pays attention to their team.
When this job is done badly, what does that look like?
Why ask it
The failure description is more specific than the success description and easier for a manager to give. It tells you what they are actually watching for.
What does the team do when the work it depends on arrives late?
Why ask it
Every team is downstream of someone, and this is where the real frustration lives. The answer shows you both the process and the temperament.
What would you want me to understand about the work before the next conversation?
Why ask it
Closes on the substance rather than on logistics, which suits a manager call. Whatever they name is what the next round will be about.
Handling an interview you cannot see
Practical guidance for the conversation itself
Setting up
Take the call somewhere with signal and no interruptions
A dropped call in the middle of your best answer is hard to recover from. Use a landline or a headset rather than speakerphone, which flattens your voice and picks up the room.
Lay out three pages in front of you
The job advert, your own history with dates and numbers, and your questions. Nobody can see you reading, which is the one clear advantage of a phone interview.
Stand up, or at least sit upright
Posture changes how your voice carries, and phone interviews are decided entirely on voice. Smiling audibly sounds contrived; sounding awake and interested does not.
Write the interviewer's name down as soon as you hear it
You will want it for your follow-up email and for the next round. Ask how to spell it if you are unsure.
Talking without visual cues
- Keep answers to about ninety seconds, then stop and let them steer. Without body language you cannot tell when you have said enough.
- Signpost longer answers: there were three parts to that project. This gives the listener a structure and stops you rambling.
- Pause after they finish, since delays on the line make interruptions easy. A short silence sounds thoughtful rather than slow.
- Say numbers slowly and repeat the important ones. Figures are the first thing lost over a phone.
- If you do not understand a question, ask them to rephrase it rather than answering a version you invented.
What goes wrong on phone interviews
Treating it as less serious than an in-person round
The same decision gets made on this call as in a room. Prepare the same examples and dress however helps you sound like you are at work.
Reading from a prepared script
Scripted answers are audible on the phone, where tone carries everything. Use notes with a few words per point rather than sentences to read out.
Asking questions the recruiter already answered
If you had a screening call, do not spend the manager's time on process, salary bands, or benefits. Ask about the work, the team, and their expectations.
Letting a poor line ruin the call
If the connection is bad, say so early and offer to call back. Struggling on through a broken line costs you more than the small awkwardness of restarting.
After the call
Within a few hours
- 1Write down the six-month priorities they named, in their words. This is what you will build on in the next round.
- 2Note anything you fumbled, and prepare a better version in case it comes up again.
- 3Send a short note referring to one specific thing from the conversation, not a general thank-you.
- 4Record the date they said you would hear by, and follow up on that day if nothing arrives.