Fixing the intake call to prevent hiring manager ghosting

{ "body_markdown": "## The cost of the passive intake call\n\nMost recruiters approach the intake call as a transcription exercise. They open a blank document, ask the hiring manager what technical skills are required, note the salary range, and ask for an ideal start date. This creates a one-way relationship where the recruiter is a service provider and the hiring manager is a customer. In this model, the manager feels no responsibility for the speed of the pipeline. If they get busy with a product launch or a board meeting, the recruitment process is the first thing they drop. \n\nThis breakdown in communication causes candidates to sit in the pipeline for weeks without an update. In Europe, where notice periods can be three months, every day of delay increases the risk that a candidate accepts another offer or decides to stay at their current company. In North America, where the market moves faster, a 48-hour delay in feedback can result in losing a top engineer to a competitor. \n\nTo fix this, the intake call must change from a requirements briefing to a project management kickoff. You are not just looking for a list of skills; you are building a shared operating agreement that dictates how both parties will behave for the next 45 days.\n\n## Moving from skills to selection criteria\n\nWhen a manager says they need a senior developer with Java experience, they are giving you a category, not a profile. If you accept this at face value, you will send five candidates who fit that description, only to have the manager reject them all for reasons they never mentioned during the intake. \n\nDuring the kickoff, force the manager to define the specific work the person will do in their first 90 days. If the goal is to rebuild a legacy billing system, the requirement is not just Java; it is experience with migration projects and technical debt. Once the output is defined, you can set the selection criteria. \n\nAsk the manager to rank the requirements. If they could only have three attributes, which would they be? This prevents the purple squirrel problem where a manager rejects great candidates because they lack a secondary, non-essential skill. Document these trade-offs in a shared hiring plan. If the manager later rejects a candidate for lacking a skill that was marked as non-essential, you have a written document to reference when you push back.\n\n## Mapping the interview stages and owners\n\nOne of the biggest reasons for hiring manager ghosting is a lack of clarity on who does what. A disorganized interview process leads to redundant questions and a poor candidate experience. \n\nDuring the intake call, you must map out every stage of the process before the job is even posted. This includes:\n\n1. The recruiter screen: Define the three specific knock-out questions.\n2. The technical assessment: Determine if this is a live coding session or a take-home assignment. Who will grade it, and what is the rubric?\n3. The peer interview: Identify two specific team members and define the competencies they are testing for.\n4. The final interview: Define what the hiring manager needs to see that has not already been proven.\n\nAssign a name to every step. If the manager cannot name the people who will conduct the interviews during the intake call, they are not ready to hire. By getting these names early, you can check their calendars and identify potential bottlenecks, such as upcoming vacations or heavy sprint cycles, before the candidates are in the pipeline.\n\n## The service level agreement as a contract\n\nRecruiters often hesitate to demand commitments from hiring managers because they see themselves as lower in the organizational hierarchy. However, the recruiter is the one whose performance metrics suffer when a role remains open for 100 days. \n\nYou must establish a Service Level Agreement (SLA) during the intake call. This is not a formal legal document, but a verbal and written contract of behavior. The SLA should specify that the recruiter will deliver a set number of qualified profiles per week, and in return, the hiring manager must provide feedback on those profiles within 24 to 48 hours. \n\nExplain the math to the manager. If it takes 24 hours to get feedback, the average time-to-hire might be 35 days. If it takes five days to get feedback, that time-to-hire doubles, and the quality of the hire drops because the best candidates are off the market. Use data from your Applicant Tracking System (ATS) to show how previous delays led to lost talent. When you frame feedback speed as a tool for securing better talent, the manager is more likely to comply.\n\n## Handling the feedback loop\n\nEven with a plan, managers will eventually miss a deadline. The way you handle the first missed feedback window determines the tone for the rest of the search. \n\nIf a manager misses the 48-hour window, do not just send a friendly reminder. Instead, schedule a five-minute sync or stop by their desk. Tell them that because you have not heard back on the current candidates, you have paused outbound sourcing for the role. This sounds aggressive, but it is a logical business decision. Why would you continue to fill a pipeline if the current candidates are stagnating? \n\nWhen the manager realizes that their delay has stopped the flow of new talent, they will prioritize the reviews. This reinforces the idea that the hiring process is a partnership, not a background task that the recruiter performs in a vacuum.\n\n## Setting the calendar in advance\n\nFinal stage interviews are the most difficult to coordinate. Instead of waiting until a candidate reaches the final stage, book blocks of time on the hiring manager's calendar during the intake call. \n\nAsk the manager for three two-hour blocks over the next three weeks specifically for final interviews. If you do not have candidates ready, you can release the blocks 48 hours in advance so the manager can use them for other work. Having these times pre-cleared eliminates the back-and-forth emails between recruiters, candidates, and executive assistants. It also signals to the manager that this hire is a high-priority project that requires dedicated time on their schedule.\n\n## Why this matters for the business\n\nIn organizations of 50 to 2000 people, the cost of a vacant role is significant. A missing product manager can delay a launch by months; a missing sales lead results in lost revenue. By shifting the intake call from a passive conversation to a structured kickoff, you reduce the time-to-hire and ensure that the business stays on track. \n\nRecruiters who master this partnership are no longer seen as administrators. They become consultants who help the business make better decisions. The intake call is your best opportunity to establish this authority. Do not waste it on a simple list of bullet points." }