Most failed searches are lost in the first thirty minutes, before a single profile is sourced. The hiring manager says, “I need a good backend developer, five to eight years, should join fast.” The recruiter writes it down and goes away. Six weeks later, the manager has rejected thirty profiles with comments like “not quite what I had in mind.” Nobody lied. They never had the same picture to begin with.
The intake meeting exists to fix that. It is a working conversation, not a form-filling exercise. My opinion: if it takes under twenty minutes, it was probably too shallow.
Start with the problem, not the job title
Ask what is going wrong today that this person will fix. “Our payment reconciliation takes four days and breaks every month end” tells you far more than “Java developer, Spring Boot.” Then ask what success looks like at six months and at twelve. Managers are often vague here the first time, and the vagueness itself is useful information: a role with no clear purpose is hard to hire for and hard to succeed in.
Separate must-haves from nice-to-haves
Every requisition arrives with a wish list of twelve skills. Force a ranking. Which three, if missing, would make you reject the candidate? Which could they learn in three months on the job? A role that needs four rare skills together will take a long time to fill, and the recruiter’s duty is to say so with data rather than apologise after day 45.
Challenge the numbers, too. “Five to eight years” is usually a stand-in for something else, like having handled a certain scale or led a small team. Ask for what the years are standing in for. You may find a person with four years and the right exposure is a better fit than someone with eight years and the wrong one.
Talk money in the first meeting
I will give this one real emphasis. Do not leave the budget conversation until offer time. Ask for the approved range and compare it with what the market is paying for the profile described. If a manager wants a person with a rare skill set at ₹18 to 22 lakh and the market for that profile starts at ₹28 lakh, say so now, with whatever salary data you have, and leave the manager to decide between raising the budget, narrowing the profile, or hiring someone more junior and developing them. A recruiter who stays quiet at this stage is setting up a collapsed offer later.
Agree on the process and timelines
- Who is on the interview panel, and are they actually available in the next two weeks?
- How quickly will feedback come back after each round? Agree a number, such as 24 hours, and write it down.
- How many rounds, and what is each round testing, so that panel members do not all ask the same questions?
- What notice period is acceptable? If the manager says “immediate joiners only”, explain what that does to the pool.
- Who makes the final call, and who has to approve the offer?
Hiring delays are mostly waiting time between steps, not sourcing time. A manager who agrees to give feedback within a day is worth more to your time to fill than another recruiter.
Calibrate with real profiles
Before launching the search, send three or four anonymised sample profiles, some close and some deliberately off, and ask the manager to say yes, maybe or no with a reason for each. Ten minutes on this prevents weeks of mismatch. You will often find the written requirement and the manager’s real taste differ. Better to find out now than at profile thirty-one.
Keep the criteria job-related throughout. If a manager asks for “a young, energetic candidate” or a particular community, the recruiter must steer the conversation back to skills and outcomes. That is both an ethical and a legal matter, and it is the recruiter’s job to hold that line politely.
Write it down the same day
Send a short summary to the manager within hours: the problem, the three must-haves, the budget range, the process and the timelines. Ask them to reply with corrections. Now you have a shared document that either side can point to later, politely, when things drift. It also becomes the base for the job description and the screening checklist, so the work is not wasted.
And hold a short check-in after the first five profiles go to the manager. If the first batch gets a poor response, return to the intake notes and adjust. That small loop is what separates a search that steadies and one that spirals.
Figures and names in the examples are illustrative.
Leave a Reply