The mistake isn't in the sourcing. It starts much earlier.
A search goes sideways at the kickoff meeting, when the recruiter accepts a vague job description, fuzzy criteria, and an ill-defined process. Then come the usual symptoms: unconvincing profiles, contradictory feedback, drawn-out searches, and excuses about talent shortages that actually mask a shortage of information.
Many articles discuss the right questions to ask in a job interview from the candidate's perspective. This one takes a different angle. If you recruit for third parties, the interview that actually determines your results is the one you conduct with the client before launching the search.
A good kickoff isn't for "alignment." It's for data extraction. Data to decide what signals to look for, which filters to apply, what biases to spot, which objections to anticipate, and how to translate all of that into effective searches inside tools like HeyTalent. Without that foundation, AI just accelerates the wrong things.
Serious recruiters don't start with a vacancy. They start with an aggressive, precise checklist. They look for business context, real requirements, salary bands, risk tolerance, decision speed, and past success patterns. That turns a commercial conversation into an intelligence-gathering mission for sourcing, filtering, and prioritization.
Here are the 10 questions to ask your client so you leave the meeting with clear criteria and an executable search strategy.
1. What does your typical process look like for filling a role in your organization?
Start with the process, not the profile. If you don't know how the company decides, you won't know when to present, when to push, and when to wait.
One client can claim urgency and then take days to give feedback. Another might run several interviews in parallel but have a single final decision-maker. Another can get stuck because HR, the hiring manager, and leadership are all evaluating different things. If you don't map that from the start, you'll end up confusing a process problem with a talent shortage.
What you need to extract from the conversation
Don't settle for "we do three rounds of interviews." You need sequence, owners, and timelines.
- Real stages: initial screen, technical interview, business interview, assessment, final sign-off.
- Owners per stage: who interviews, who advises, and who decides.
- Response cadence: how long each person takes to review profiles and give feedback.
- Typical blockers: holidays, packed calendars, internal approvals, shifting priorities.
A clear example: a startup can move fast if the founder and manager are aligned. A large corporation might have more layers and more friction. Neither model is inherently better. The problem appears when the client promises agility but operates with silent multi-approval layers.
Practical rule: if the client can't describe their process with clear steps and owners, your search starts at a disadvantage.
How to use this in sourcing and outreach
This data shapes your whole approach. If the process is slow, don't fire all your outreach in one week. Reserve pipeline and pace your contact cadence. If the process is fast, have candidates ready before the formal briefing lands.
This also helps you decide how to automate follow-up. In HeyTalent, for example, it makes sense to sync your outreach sequences with the client's decision rhythm. If you know profile reviews happen on Thursdays, present before then. If the technical director only evaluates on Mondays, don't burn candidates late on a Friday.
Also get the names and email addresses of every stakeholder. Not for protocol. For operational control.
2. What are the non-negotiable requirements for this role?
If you don't force this conversation at the kickoff, you'll end up chasing ghosts.
Clients typically arrive with an inflated list. It mixes requirements that genuinely affect hiring with team preferences, habits, and recycled text from an old job description. Your job isn't to copy that list. It's to strip it down to a useful sourcing filter.
Rank the briefing by real impact
Ask a simple question and then push: "If a candidate meets this criterion but fails here, would you still interview them?" That follow-up cuts a lot of noise.
Classify each requirement into one of these:
- Non-negotiable: if it's missing, the candidate is out.
- Desirable: adds value, but isn't a blocker.
- On-the-job learnable: can be picked up quickly with context and support.
- Historical baggage: it's there because nobody questioned it.
This classification isn't cosmetic. It changes how you build searches, prompts, filters, and outreach messages in tools like HeyTalent. If you lump sector experience, a specific tool, and immediate availability into the same bucket, the AI will return a narrower, less useful market. Separate the critical from the secondary, and you gain precision.
A clear example: in a data analysis role, being able to work with databases independently and communicate findings to the business might be essential. Mastering a specific platform could be secondary if the candidate already shows strong analytical judgment and a track record of solid reporting.
The follow-up that prevents miscalibrated searches
Use this phrase directly: "Does this need to be resolved from day one, or can it be developed in the first few weeks?"
Contradictions surface here. The hiring manager calls a skill mandatory. Then they admit the team can teach it. Good — so it doesn't belong in the hard filter. It belongs in the later evaluation or the onboarding plan.
If there are several stakeholders, get explicit alignment. Don't accept vague answers or endless lists. Demand real prioritization. Five well-defined criteria are worth more than twenty requirements nobody can defend in an interview.
Your goal at this stage isn't to fill out a document. It's to turn a generic conversation into operational data for better searching. If the client can't say which requirements kill a candidacy and which ones just improve it, they're not ready to receive profiles yet.
3. Is there a pattern or trait that has worked well in past candidates?
Every client has patterns, even if they say they're looking for "the best." Your job is to surface those patterns before they contaminate the process in an uncontrolled way.
You're not asking about discrimination here. You're asking about trajectories, contexts, and environments where the client has already seen success. Startup people. Consultancy people. Profiles from highly structured organizations. People used to autonomy. Managers who've already built a team from scratch.
Don't ask for opinions. Ask for examples
The useful question isn't "what profile usually fits here?" It's this: "Thinking about your best recent hires, what did they have in common?"
Then drill into specifics:
- Background: startup, SME, corporation, consultancy.
- Type of previous challenge: growth, structure-building, transformation, expansion.
- Work style: autonomy, reporting, cross-functional coordination, technical focus.
- Repeated soft signals: clarity, resilience, ability to influence, rigor.
If the client says "people from high-growth companies have worked really well," you have a sourcing signal. If they say "we need people who don't freeze when things are ambiguous," that affects both the filter and your pitch.
Sometimes the best insight from a kickoff isn't a skill. It's the type of context in which that skill already worked.
How to convert the pattern into a useful filter
Don't copy the bias blindly. Interpret it. If a client values ex-startup backgrounds, they might not actually want "startup brand." They might want speed, autonomy, and less hierarchy. That lets you open the search to profiles that didn't come from that exact type of company but show the same behaviors.
In tools like HeyTalent, this information feeds custom AI variables. You're not just filtering by job title. You're filtering by signals in a professional history that match the success pattern the client already recognized.
If you skip this question, you'll get the classic objection later: "Good profile, but I don't see them fitting our context." That phrase almost always means the pattern existed, but nobody articulated it at the start.
4. What's the approximate budget for this search, and is there time pressure?
Some recruiters avoid talking about money and urgency at the start. That's a mistake. Budget sets expectations. Urgency sets effort.
If the client won't talk clearly about salary range, fee, or timing, you don't have a search. You have a hypothesis. And poorly funded hypotheses consume more hours than well-defined projects.
Real budget, not political budget
Ask two questions, not one. "What's the ideal range?" and "What's the maximum if the right person appears?" Those are different things.
Also distinguish between hiring budget and search budget. A company might have salary room but zero tolerance for a long process. Another might want to optimize the fee but require high speed. You need to know which variable you can work with.
A simple example: if the need stems from an unexpected departure, a leave, or a project deadline, the time pressure completely changes the strategy. In that scenario, you don't want an open search with generic messages and slow review. You want fast contact, a short shortlist, and near-immediate feedback.
Urgency needs to be demonstrated
Don't accept "we need it as soon as possible." Ask what happens if the role isn't filled. That's where real urgency surfaces.
- Operational urgency: work is blocked.
- Political urgency: someone promised a hire.
- Apparent urgency: the client wants to move but hasn't aligned on a decision.
- Selective urgency: one vacancy is pressing harder than others.
In the Spanish market, asking for context isn't optional. Talent supply and demand remain significantly misaligned. In 2024, 65% of Spanish companies reported difficulty filling vacancies, with particular tension in technical and specialized profiles, according to Hays Spain on key interview questions.
That data doesn't tell you how much to charge or how long it'll take. But it tells you something more useful: if talent is scarce, accepting a blurry brief is even more expensive.
5. Who else will interview or evaluate the candidate? What are their priorities?
If you don't map the evaluators from the start, the search goes off track even when the candidate is strong. The failure usually isn't about talent. It's about a process where each interviewer is looking for something different and nobody's said so out loud.
Your job in the intake isn't just to collect names. It's to build a decision map that's useful for sourcing. If you're going to use AI to identify profiles, write prompts, prioritize LinkedIn signals, or prepare candidate summaries, you need to know who's judging what. Without that, the technology accelerates the error.
Map the real decision-making power
Ask for this information explicitly:
- Who interviews and at which stage: screening, technical, hiring manager, leadership.
- What each person validates: technical ability, judgment, communication, leadership, business fit.
- What weighs most in their decision: sector experience, functional depth, autonomy, stakeholder management.
- Who can block the process: even if they're not the main interviewer.
- What objections each evaluator repeats: lack of structure, low commercial energy, inflated seniority, profile too tactical.
This completely changes how you search and present. If the CTO wants technical depth but the CEO penalizes overly specialized profiles, you can't send a flat list of "valid" candidates. You need to segment. Some profiles open the process; others close it.
Turn fuzzy priorities into criteria the AI can use
This is where a mediocre intake becomes a serious search. Don't accept phrases like "good fit" or "knows how to navigate." Force the client to define observable behavior.
Ask questions like:
- What makes a candidate convince the hiring manager in 20 minutes?
- What usually creates doubt in the final interview?
- What kind of profile looks good on paper but doesn't pass?
- What type of experience builds immediate trust with each interviewer?
The answers let you tag, filter, and rank talent more precisely in tools like HeyTalent. They also help you write outreach with the right angle. You don't present a profile the same way to a manager who prioritizes execution as you do to a founder who buys into vision.
Get names, roles, and priorities. If the client shares LinkedIn context or professional background on each evaluator, even better. Not for protocol — because every data point sharpens your read of the process and reduces avoidable rejections.
A strong candidate can fall early if they're put in front of the wrong person with the wrong narrative.
Don't underestimate this. Many processes break here — not from a lack of candidates, but from a lack of alignment among evaluators. Your job is to catch that before the search goes live.
6. What has been the biggest challenge with previous candidates in similar roles?
Don't look for generalities here. Look for scar tissue.
When a client has experienced a bad hire, a quick departure, or a string of rejections, they tend to reach poor conclusions. "We don't want consultancy people." "We don't want very senior profiles." "We don't want someone from a corporate background." That doesn't help. You need to decompose the problem.
Get them to tell the full story
Ask about a specific situation: what they expected, what they found, and where the friction appeared. Sometimes the problem was the person. Often it was the role.
Common patterns:
- Senior without the ability to delegate: the client needed real leadership, not just expertise.
- Great profile who left quickly: the proposition wasn't well defined.
- Technically strong candidate who didn't convince the business: the communication failed, not the technical base.
- High turnover in the role: the issue might be the manager, scope, or expectations.
The lesson for recruiters: if the client speaks in abstractions, you learn nothing. When they get concrete with facts and outcomes, you can spot the real pattern behind the failure.
Convert the pain into an operational criterion
Don't copy the client's complaint. Translate the experience into observable sourcing signals.
If the problem was a lack of autonomy, don't exclude an entire sector. Look for signs of excessive dependency in the career trajectory. If delegation was the failure point, prioritize people who've coordinated work or led teams before. If turnover came from rhythm mismatch, look for trajectories that show adaptation to similar environments.
The key: don't filter by trauma. Filter by what you've learned from it.
7. How does this role compare to other open positions? Is there internal competition?
Not all vacancies carry the same weight. The client will almost never tell you that upfront. You have to draw it out.
A company might have several open processes and only one that's truly critical. There might also be two departments competing for similar profiles. If you don't understand that hierarchy, you spread effort inefficiently and end up pitching contradictory messages into the same market.
Real priority vs. declared priority
Ask directly: "If we could only close one vacancy this month, which one would it be?" That answer clarifies more than any org chart.
Then broaden the scope:
- Which vacancies are critical right now
- Which roles can wait
- Which profiles share the same talent pool
- Whether internal teams are competing for the same type of candidate
This matters especially for scarce profiles. If two managers want nearly the same person with slight differences, you need to decide from day one where to position each candidate and how to avoid clumsy overlaps.
How this affects your strategy
If the role has low priority, don't give it the same credits, research time, and follow-up cadence as a vacancy that's blocking the business. If there are several similar searches, define exclusions and distinct messaging from day one.
In practice, this question also helps you manage client expectations. If the vacancy is competing internally for attention, don't promise fast closure. Promise visibility, market coverage, and an actionable shortlist.
A good agency doesn't just find talent. It also organizes client priorities when the client hasn't done so internally yet.
8. What LinkedIn or professional network information is most important to validate in candidates?
This is where the recruiter who browses profiles separates from the recruiter who builds a useful shortlist.
The right question for the client isn't "what do you like to see on LinkedIn?" It's: "what signals make you advance or drop a candidate before the first interview?" If you don't define this in the kickoff, your team collects noise. And noise slows down sourcing, screening, and outreach.
Validate signals, not fields
LinkedIn doesn't just confirm job titles. It reveals whether the profile holds up under real scrutiny.
Ask the client to prioritize what they need to verify in this search:
- Real trajectory: progression, lateral moves, stability, explainable gaps.
- Role scope: whether they led, executed, or just participated.
- Visible stack or technical context: tools, methodologies, environments, project types.
- Public credibility signals: recommendations, publications, portfolio, professional activity.
- Useful contact data: email or phone, if the process requires fast coordination.
For technical or analytical profiles, this matters a lot. A well-written headline doesn't compensate for a lack of evidence on tools, impact, or level of autonomy. Your job is to force the client to articulate what proof they consider sufficient.
Questions that sharpen the intake
Be direct. No theory.
"When you open a profile, what are the first three things you look at?"
"What builds immediate confidence, and what creates doubt?"
"What data do you want validated before approving an interview?"
"Which parts of the profile do you treat as decoration, and which do you take seriously?"
These answers give you operational criteria. They also let you configure searches better in AI tools like HeyTalent. When you know which signal actually matters, you filter earlier, enrich smarter, and reduce pointless reviews.
One more point many clients confuse: visibility doesn't equal fit. A very active profile might look better than it actually is for the vacancy. So it's worth agreeing on how much weight they give to personal brand versus demonstrable experience. If you want to think through that conversation, Ploot explains the SSI and helps separate professional presence from actual fit.
What changes in your strategy
If the client prioritizes public credibility, review activity, recommendations, and projects before reaching out. If they prioritize speed, get verified contact data from the start. If they prioritize technical depth, don't launch bulk outreach with half-validated profiles.
The idea is simple: don't fill in the candidate profile out of habit. Define with the client what information speeds up a decision — then use that as your search, filter, and presentation criterion.
9. How open are you to non-traditional profiles or career-changers?
This question defines the real width of your market.
Some clients say they're open but reject any non-linear trajectory. Others think they want an exact match, when in reality they'd accept an adjacent profile with a strong learning curve. If you don't clarify this, you might search too narrow or too wide.
The right answer isn't yes or no
What's useful is knowing which transitions they'll accept and which they won't.
- Sector change with same functions
- Move from consultancy to an in-house role
- Step down from a more senior position to an individual contributor role
- Hybrid career across business and technical functions
Ask about past cases that worked. If there are none, ask which transition would be the least risky they'd consider. That converts an abstract idea of flexibility into a real market criterion.
This also connects to how a company values professional visibility and positioning. If you do a lot of LinkedIn sourcing, understanding the weight of personal brand and social indicators can help. If that angle interests you, Ploot explains the SSI and why some profiles appear more visible than they actually are in terms of fit.
When to open up and when not to
Open the search when the client can train context, sector knowledge, or tool usage. Close it when the learning risk is too high for the urgency of the role.
The type of vacancy matters too. If the role is in transition, ask whether it's a new position, how it evolved, or what happened to the previous person. Many guides recommend this but explain little about how to read those answers. That's the difference between presenting an "interesting" profile and presenting one that's actually hireable.
Don't use this question to sound progressive. Use it to decide between surgical precision and intelligent breadth.
10. How do we communicate? How often do you want progress updates?
The client communication cadence defines the real speed of the search. If this point stays vague, the process degrades fast. Messages arrive out of context, feedback comes in late, and criteria changes go undocumented.
In the intake meeting, close on a small operational protocol. It doesn't need to be complicated. It needs to be written down and used from day one.
What to lock in before launching the search
Define these three variables:
- Frequency: weekly, biweekly, or at process milestones.
- Channel: email, call, WhatsApp, or a brief meeting.
- Format: what data goes into each update and in what order.
Don't leave it at "we'll see how it goes." That just creates friction.
Your update should help drive decisions, not fill space. Always include: pipeline status, profiles presented, pending feedback, blockers, market signals, and the client's expected next action. If you're using AI for sourcing or prioritization, say so. The client needs to know what inputs you'll need to refine searches, adjust prompts, or correct criteria inside tools like HeyTalent.
What to agree on in advance
Define what counts as urgent. A counteroffer qualifies. A candidate who goes dark, too. A salary change, a new hiring manager requirement, or a last-minute interview cancellation all warrant immediate notice.
Everything else can wait for the agreed update.
Ask one more question, and ask it literally: "What do you need to see in each update to make decisions faster?" That answer gives you highly useful operational insight. If they ask for CVs without context, you know you'll have to educate the process. If they ask for comparisons, market signals, or rejection rationale, you already have the reporting format that will serve them best.
Also agree on who responds and how quickly. If the client takes four days to give feedback, you don't have a sourcing problem. You have a process problem. And if you don't catch that in the kickoff, you'll compensate with more messages, more pressure, and less control.
Communication isn't courtesy. It's search infrastructure. Design it well and you improve feedback quality, train the client better, and feed the AI more useful data.
Comparison: 10 key questions to ask in a job interview
| Question | Implementation complexity | Resource requirements | Expected results | Ideal use cases | Key advantages |
|---|---|---|---|---|---|
| What does your typical process look like for filling a role in your organization? | Moderate (coordinate stakeholders and document processes) | Interview time, process docs, stakeholder mapping | Optimized hiring cycle and synchronized outreach timing | Searches with multiple approvals or long processes | Avoids presenting candidates at the wrong moment; identifies decision-makers |
| What are the non-negotiable requirements for this role? | Low to moderate (gather clear criteria) | Hiring manager validation, requirements docs | More precise filters and fewer false positives | Searches with critical technical requirements | Reduces Boolean search noise; improves candidate-to-interview conversion |
| Is there a pattern or trait that has worked well in past candidates? | Moderate-high (historical pattern analysis) | Hiring history, performance data, interviews | Better prediction of cultural fit and candidate quality | Roles where cultural fit or historical patterns matter | Improves retention; enables AI variables based on past success |
| What's the approximate budget and is there time pressure? | Low | Clear budget and deadline information | Resource prioritization and adjusted outreach speed | Urgent searches or searches with limited margin | Optimizes credit usage and determines sourcing velocity |
| Who else will interview/evaluate the candidate? What are their priorities? | Moderate | List of evaluators, priorities per stakeholder | Candidate presentations aligned to each evaluator | Hires with multiple decision-makers | Enables personalized messaging; reduces interview surprises |
| What's been the biggest challenge with previous candidates in similar roles? | Moderate | Concrete examples and red flags | Filtering of problematic profiles, lower risk of bad hires | Roles with a history of problems or high turnover | Reduces failed hires; enables more selective searches |
| How does this role compare to other open positions? Is there internal competition? | Moderate | Hiring roadmap and internal priorities | Vacancy prioritization and candidate reuse | Organizations with multiple simultaneous openings | Optimizes credit allocation; avoids talent conflicts |
| What LinkedIn or professional network information is most important to validate? | Low | Enrichment and contact verification tools | Verified contacts and effective outreach channels | Roles requiring direct contact or verification (HR, sales) | Improves connection rates; reduces time-to-hire by validating key data |
| How open are you to non-traditional profiles or career-changers? | Moderate | Past examples, evaluation criteria, compensation | Wider candidate pool and greater diversity | Markets with talent scarcity or creative searches | Access to undervalued talent; reduces direct competition |
| How do we communicate? How often do you want progress updates? | Low | Cadence agreement, preferred channels, report templates | Aligned expectations and less communication friction | Freelancers/agencies managing external searches | Enables automated reporting; improves client-recruiter relationship |