The Other-Interviews Disclosure, Scored to Name, Signal, or Decline

A recruiter or hiring manager just asked where else you are interviewing, and you have a few seconds to decide how much to say. This guide is for candidates in a live process who need a model, not a script, for that call. It scores the moment across four dimensions - who is asking, your stage with them versus the others, whether you are chasing speed or leverage, and your verification exposure - so you pick the response that fits instead of a default line, and can predict what each choice does to your timeline and your exposure.

The existing advice is one-size: "name them" or "politely decline." Both are wrong most of the time. The correct answer is usually a third thing, and the point of a framework is to tell you when it is not.

What "where else are you interviewing" actually asks

The question is rarely the question. It is a probe for one of three things, and the reason behind it determines what a good answer looks like. Read the asker's motive before you answer the words.

Documented reasons cluster into three:

• Interest-gauging. A hiring manager asking this is trying to assess how interested you really are and to size up their competition. They want to know if you will say yes.
• Timeline planning. Recruiters work against deadlines to fill a role. Knowing whether you are actively interviewing elsewhere tells them how urgently they need to move, and a real competing offer can expedite their decision.
• Competitive intelligence. Some asks exist only to fish for names and numbers you were not planning to offer. On practitioner forums the read is blunt: the recruiter is not asking for a stated reason, just trying to find some leverage.

The agency recruiter has a fourth, distinct reason that no internal recruiter shares: they need to know so they do not send your resume to a company where you are already in play. That single difference reshapes the whole call, and I return to it below.

The four dimensions that decide the call

Score the moment on four axes, in order. Each is a fast judgement you can make in under a minute, and together they point to name, signal, or decline.

1. Who is asking. Agency, internal recruiter, or hiring manager. This is the only dimension where the double-submission logic can flip your default toward disclosure.
2. Your stage with them versus the others. Leverage exists only after a company has invested through multiple interviews or explicit interest. Before that, disclosure reads as presumptuous.
3. Your objective: speed or leverage. Speed wants a compressed timeline. Leverage wants a better number. They fire at different stages and call for different disclosures.
4. Your verification exposure. In tech and among networked recruiters, assume a named company or a stated number can be checked. Exposure decides whether specifics are safe.

The three response levels sit on a single spectrum: as you move from declining to signaling to naming, both your leverage and your exposure rise together. The whole game is decoupling them - capturing the leverage without paying the exposure.

Signal in general terms is the dominant strategy precisely because it breaks the link between the two columns. Giving titles, sector, and contract type triggers the recruiter's fear of competition, which is set off by the existence of other processes, not their identity - while withholding the verifiable specifics that get people caught.

Who is on the other end, and why it changes the safe answer

The agency-versus-internal split flips the safe answer, and most candidates cannot tell which one they are talking to. With an agency recruiter, silence is the risky move; with an internal recruiter, silence costs you nothing.

Here is the mechanism. An agency's revenue depends on being the exclusive party that introduced you. If your resume reaches a company from two recruiters, that company may fear being invoiced twice - two introduction fees can aggregate to 50% of your remuneration - and faced with that, clients often retract the offer rather than pay both agencies. So when an agency asks where you are in play, telling them protects you from a duplicate submission that can kill an offer you never see coming.

An internal recruiter carries none of that risk, because they do not submit you anywhere outside their own company. The submission-protection reason is agency-only.

The problem is that the two populations are close to even, so you cannot assume. In Refolk's index of professional profiles, the US split between the two groups is nearly balanced.

If you are unsure who represents you, resolve it before you answer. A quick search of who works at the firm and whether it publishes a candidate-ownership policy settles it. Refolk writes your resume from your own history and tailors it to each posting, and the same index lets you confirm whether the person in your inbox sits inside the hiring company or at a staffing firm - which is the single fact that decides whether disclosure protects you or exposes you.

The agency compromise, in one instruction

When the asker is an agency, do not go silent and do not hand over blanket permission. Put yourself in control with a documented compromise: instruct the agency to name its clients and get your explicit approval before submitting you anywhere. Be wary of any recruiter unwilling to accept that.

Happy to work with you on this. Two ground rules so we avoid any double-submission problem:

1. Tell me the client name before you submit me, every time.
2. I confirm in writing before you send my resume anywhere.

I'm already in process at a couple of places, so this keeps us both clean on ownership. If that works, let's go.

Verification exposure: assume they can check

Assume any named company or stated number can be verified, and calibrate that assumption to how networked the market is. The denser the recruiter population, the more back-channels exist, and the less you can rely on a claim going unchecked.

Recruiters ask their recruiter friends at other companies all the time. Compensation departments at large tech companies run competitive comp analysis, so an unrealistic number gets discounted the moment it lands. The "just bluff, they cannot verify" advice is weakest exactly where candidates most want to use it, because density and verifiability move together.

The US has 15.5x the UK recruiter population in Refolk's index. In a market that dense, treat every specific as checkable. This does not mean never name a company; it means name one only when the claim is true, plausible, and something you would stand behind if a recruiter cross-checked it over coffee.

Score it: name, signal, or decline

Run the four dimensions, then pick the level. Signal in general terms is the documented default; you escalate to naming only when the specifics genuinely serve your objective and your exposure is low, and you fall back to declining when you have nothing real to disclose or the asker has not yet invested.

The judgement gets easier when you plot it. The two variables that most often decide between naming and signaling are your relative stage and your verification exposure.

Speed and leverage fire at different stages

Speed and leverage are not the same move, and they work at opposite ends of the process. Speed disclosure works before the company commits and can compress a two-week timeline into a few days. Leverage disclosure needs a written offer in hand and goes inert once the company has locked its internal approvals.

The mechanism is flexibility. Early, decisions are fluid and a deadline is something the company can act on. Late, after verbal offers or finalized paperwork, hands are tied - they would move if they could, but the commitments are made. A verbal offer is some leverage; a written offer is real leverage.

If your objective is speed and you have a real offer, the move is a single factual note.

Hi [name],

I wanted to be upfront. I've received an offer elsewhere with a decision deadline of [date]. I'm genuinely excited about [role] here and would rather see this through before I decide.

Is there anything I can do to help move the process forward, or would it be possible to get a decision by [date]?

Thanks either way.

If it does not work, you are out one email. That is the whole downside, which is why the note is the safest lever you have when the offer is real.

How this goes wrong

Most disclosure damage comes from a small set of repeatable mistakes. Each has a false positive - a moment where the wrong move looks reasonable - and a specific check that catches it before you speak.

• Claiming an offer you do not have, for speed. The company politely sets you free to go take your offer instead of accelerating. The tactic breaks precisely when there is no offer on the table. Check: send a deadline note only when a real offer exists.
• Naming a prestigious competitor. You read as already gone. At an early stage the company is not yet sure you are the right candidate, and a big name sounds like you are accepting elsewhere. One reported case: a recruiter at a small company got visibly deflated on hearing the candidate was interviewing at a tech giant. Check: is the name so strong it triggers a withdrawal read?
• Stating an implausible number. The comp team silently discounts you. If you bluff unrealistic numbers, the comp department knows right away. Check: would the figure survive a competitive comp analysis?
• Disclosing too late. After the company's offer or paperwork, they say they would love to but their hands are tied. Companies have limited flexibility once commitments are made. Check: are decisions still fluid, or already locked?
• Giving an agency free rein without client names. A duplicate submission surfaces later and the offer is retracted. Check: have you instructed the agency to name clients and get permission first?
• Reading a leverage probe as a neutral question. You volunteer names and numbers you never needed to. The ask may exist only to find some leverage. Check: answer the level, not the literal words.
• Using a weaker offer as leverage. A competing offer that would be a step down signals limited options and weakens your position. Check: does the offer strengthen your hand, or reveal its limits?
• Mistaking a rushed process for genuine urgency. You accept a bad-fit role under an artificial clock. A "now or never" ultimatum may signal desperation to fill rather than concern for fit. Check: does the recruiter reject a reasonable slow-down request and keep pushing?

The stakes on getting the multi-offer dance right are not trivial. A career site citing Gartner data reports that, over a 12-month period, 50 percent of respondents accepted a job offer and then backed out before starting, and 35 percent received four or more offers during their last search. Running several live processes is normal, which is exactly why a repeatable disclosure model beats a one-off script.

Before you answer, run the checklist

Use this the moment the question lands, or before you volunteer anything unprompted. If you cannot check every box, drop to signal or decline.

Keeping the call current for your market

The framework holds across markets, but two inputs shift and are worth re-checking before a search: how networked your specific recruiter market is, and whether the person asking is agency or internal. Both change the safe default. In a denser market, treat more claims as verifiable; with an agency, treat silence as the exposure rather than the safe choice.

Verify who is on the other end rather than guessing. The example below finds internal talent-acquisition partners so you can tell them apart from agency recruiters before you answer the ask.

When the market is dense and the asker is verifiable, signal in general terms and reaffirm interest. When you hold a real offer and the company has not yet committed, send the deadline note. When you are talking to an agency, name your terms before they name a client. Everything else is a variation on those three, scored by the four dimensions - and the discipline of scoring the moment, rather than reaching for a default line, is what keeps a good process from becoming an accidental goodbye.