Recruiter call audio: you are being interviewed too

A phone screen is the only part of your hiring process where the candidate evaluates the company through a single pair of ears. They cannot see the office, the team, or the product. They have your voice, thirty minutes, and whatever they can infer from how the call sounds. That is a thin channel to carry an employer brand, and a bad line degrades it faster than any missing perk.

This page is written for the interviewer's side of that call — recruiters, hiring managers, anyone who runs screens in batches and has stopped noticing what those calls sound like from the other end. The candidate's side is a different guide by different people; we're concerned with the half you control and are judged on.

The asymmetry nobody accounts for

The candidate prepared for this call. They blocked the time, found a quiet room, tested their headphones, and rehearsed an answer about their proudest project. You are on screen six of eight, eating lunch with one hand, and your machine has been awake for eleven hours.

That asymmetry is the whole problem. Their attention is fully on the call; yours is split, and every artifact in your audio lands on a listener with nothing else to do but notice it. The keyboard clatter while you take notes reads as this person is doing something else. The level that drifts between screens reads as disorganization. The voice that arrives thin and distant reads, unfairly but reliably, as a company that doesn't invest in things.

The fix isn't more effort per call. It's a setup that holds across all eight so you never spend attention on audio again.

What a rough line actually costs a recruiter

• Drop-off you never attribute. Candidates rarely tell you the call felt off. They just go quiet, or take the other offer, and you file it under "not interested."
• Mishearing the number. Compensation expectations, notice periods, and visa details are spoken once, often quickly, often by a nervous person. A noisy line is how "eighty-five" becomes "ninety-five" and how a scheduling conflict gets discovered three rounds later.
• Notes that reconstruct badly. Whatever captures your calls — your own typing, a recorder, an assistant tool — is working from the same signal you heard. Noise in, ambiguity out.
• The referral tax. Candidates describe their interview experience to peers with startling specificity. "I couldn't hear her" is a sentence that travels.

Set it once for the whole screening block

Screening days are batch work, so treat audio as batch infrastructure: configure before the first call, then don't touch it until the block is over. Fiddling between calls is how settings drift.

The ribbon’s thinning is drawn, not measured: the page says only that the sixth-hour voice is quieter.

The full pre-call ritual, in the version you can screenshot, lives on the first-impression audio checklist. Recruiters should run it once per block, not once per call.

The first thirty seconds set the register

Open with a sentence that does audio work without announcing itself. "Hi Dana — can you hear me clearly?" accomplishes three things: it confirms the line, it gives you a sample of their audio to calibrate against, and it signals that you care whether this call goes well. Then, crucially, believe the answer. If a candidate says "you're a little quiet," they are being polite about something significant; adjust immediately rather than pressing on.

Avoid the long technical preamble. Two questions about their setup is diligence; five is a hostage situation, and you've spent the candidate's goodwill before you've asked anything about their work.

When it's their line that's struggling

Candidates take screens from stairwells, parked cars, and borrowed conference rooms, because many of them are calling you from a job they haven't left yet. Their bad audio is usually evidence of discretion, not carelessness, and it should never cost them.

Name the connection as the culprit, offer a fix, and move on in one breath. What you must not do is let a poor line silently shape your evaluation — that's how audio quality becomes a proxy for candidate quality, which is both unfair and expensive. If you couldn't hear a third of their answers, write that in your notes instead of a rating.

The habit that keeps it honest

Once a month, listen back to two minutes of one of your own screens — where recording was consented to and appropriate — and grade only the sound. Are you audible at a steady level? Is there a floor under you? Do you interrupt more than you remember? Most recruiters discover that they sound rushed, and rushed is the one impression that undoes the entire pitch about a company that cares about people. The broader version of that habit is on follow-up call habits.

Questions from the interviewer's chair

Should I apologize for my own background noise?

Once, briefly, and only if it was genuinely disruptive. Repeated apologizing shifts the emotional labor onto the candidate, who now has to reassure the person deciding their future. One calm "sorry, that's the street — go on" is the whole performance.

Is it fair to note that a candidate had bad audio?

Note it as a fact about the call, never as a trait. "Line was poor, could not assess the systems-design answer" is useful and honest. "Seemed unprofessional" from the same evidence is a bias with a job title.

Do I need anything beyond what my meeting platform includes?

If you screen from a quiet room, no — and we'd rather say that than sell you something. If you screen from anywhere with other humans in it, a dedicated layer earns its keep on volume alone: eight calls a day, every day, with one thing you never think about again.

Related: the full setup on sounding professional on client calls, and what to do when something loud happens mid-conversation on the noise-mid-pitch playbook.