Topic 8 — Working with hiring managers

Goal: Build the key partnership that makes hiring succeed.

Lesson 8.1 — The relationship the whole search rests on

Yara's first week at Northwind Robotics, she watched a search die. Not from bad sourcing — from a recruiter and a hiring manager who never really got on the same page. The recruiter sent profiles; the manager rejected them one by one without ever explaining what was wrong. Six weeks, forty candidates, zero hires. The req got quietly handed to someone else.

She'd come from three years of tech-sales, hitting quota by reading people and managing accounts. So the lesson landed fast: the hiring manager — the person the new hire will work for, who makes the final call on who gets the offer — is a recruiter's single most important working relationship. Not the candidate. Not the ATS. The hiring manager.

When that partnership is strong, hiring is fast and the hires stick. When it's weak — misaligned on what "good" means, slow to give feedback, a little distrustful of each other — the search stalls no matter how sharp your sourcing is. Gartner found that when hiring managers aren't aligned with their recruiter on what the role actually needs, the requisition is far more likely to get rewritten mid-search, and time-to-fill stretches out significantly. The misalignment is the cost, every time.

A perfect candidate sourced for a role you don't truly understand is just a faster way to waste six weeks.

Yara's first req came from Marcus Beaufort, the VP of Engineering, who owned more open roles than anyone and had been burned by recruiters before. Winning him over was going to be the whole job.

Lesson 8.2 — Partner, not boss

Marcus opened their first call with a job description and a clipped "find me people who look like this." Old Yara — the SDR who'd learned to take the brief and run — almost said "on it" and hung up. Her mentor, Imani Okafor, had warned her about exactly this moment.

"He's not your boss on this search," Imani told her. "He's your partner. You don't work for him, you work the problem with him."

Here's the split that makes that true. The hiring manager is busy with their actual job — Marcus is running an engineering org, not recruiting full-time — and most hiring managers aren't hiring experts. They know their team and the role cold, but they don't know the market, the process, or what a realistic search looks like. You bring that. You're the hiring expert; they're the role expert. Treat the relationship as a partnership to advise and collaborate with, not a list of orders to fill.

This reframe is freeing for a career-changer with no coding background. Yara couldn't out-engineer Marcus, and didn't need to. Her edge was the part he was weakest at: reading the market, running a tight process, and telling him the truth about what his req would actually cost to fill. The moment she stopped trying to sound technical and started acting like a market expert, his shoulders came down a little.

Lesson 8.3 — The intake meeting, and the question that cracks it open

If there's one meeting that decides whether a search lands or stalls, it's this one. The intake meeting (also called the kickoff) is the conversation at the very start of a search where the recruiter digs into what they're really looking for. Get it right and everything downstream gets easier. Get it wrong and you source the wrong people for weeks before anyone notices.

So Yara came to Marcus's intake with a real agenda, not a blank page. She worked through:

• The real day-to-day. Not the JD's bullet list — what will this person actually do all week? For Marcus's senior backend role, "ship and own services in Go, mostly the order-routing system."
• Must-haves vs. nice-to-haves (Topic 3). The true bar, separated from the wish-list.
• What "great" looks like. Profiles Marcus admired — two engineers already on his team, one he'd lost to a competitor.
• Team and context. Who they'd report to, the working style, what makes someone thrive on this team versus wash out.
• The pitch. Why would a strong, happy engineer leave a good job for this one? (She'd need this for every outreach message and every close.)
• Logistics. Seniority, salary range, location and remote policy, timeline, and the full interview process — who screens, who's on the panel, who decides.

Then she did the thing that separates a skilled recruiter from an order-taker: she pushed gently past the wish-list. Marcus's JD demanded five years of Go, Kubernetes, and warehouse-robotics experience. So she asked the question that cracks a wish-list open:

"If a candidate had everything except the robotics background, would you still want to talk to them?"

Marcus paused. "...Honestly, yeah. The Go matters most. Robotics they can pick up." And just like that, a "must-have" that would've shrunk her pool to almost nobody became a nice-to-have. A great intake interrogates the job description until you find the real bar, rather than taking it at face value.

Lesson 8.4 — Calibrate before you go wide

Yara sourced four candidates that first week — not forty. That was deliberate.

Before she poured days into a full search, she booked fifteen minutes with Marcus and put 3-5 real profiles in front of him: are these the right kind of people? This is a calibration review, and it's the cheapest insurance a recruiter buys. You confirm you're aiming at the right target before you fire off dozens of outreach messages at the wrong one.

It paid off immediately. Marcus loved two profiles, shrugged at one — "too junior, this person's never owned a system end to end" — and flagged the fourth: "great engineer, but pure big-tech. This person's going to hate a scrappy Series B." That single sentence reshaped her search. She wasn't looking for the most credentialed engineer; she was looking for one who'd thrive in chaos. Without calibration, she'd have spent two weeks chasing polished big-tech resumes Marcus would've quietly rejected one by one — exactly the death-spiral she watched in week one.

One of those first four was Devon Asante, a backend engineer happy in their current job but curious. Marcus's note — "this is the profile, more like this" — told Yara that Devon was worth the long, patient pursuit a passive candidate needs. She'd been right to go narrow first.

Lesson 8.5 — Advise honestly, and chase the feedback

Two weeks in, Yara had screened thirty candidates and not one hit all of Marcus's original requirements at his original salary band. A timid recruiter hides that. Yara brought it to him straight, with the data: "We've screened thirty people. Engineers with this exact stack at this seniority are scarce right now, and the ones who have it are getting paid well above your band. We can flex the seniority a notch, stretch the comp, or wait — but I want you making that call with the real numbers."

That's the heart of being a trusted advisor: advise, don't just serve. An order-taker fills the req as written and lets it quietly fail. An advisor brings the market back to the manager — what's realistic, what it costs, what to flex — and helps shape a better decision. Yara couldn't write Go, but she could tell Marcus the truth about his market, and that's what made her indispensable. He moved the band up eight percent and reframed the role to "senior" instead of "staff." The pool tripled.

The other half of the job is driving feedback. Hiring managers get slammed, and slow interview feedback quietly kills searches — a strong candidate sitting four days without a yes/no is a candidate drifting toward a competitor's offer (Topic 4). So Yara pushed, politely and relentlessly: scorecards within a day of each interview, a quick debrief after the loop, decisions that didn't sit for a week. When Devon finally interviewed, she had Marcus's scorecard the same afternoon and an offer out before the weekend. The candidate who feels the process moving is the candidate who says yes.

She kept Marcus posted constantly — a short Friday update, every week, whether or not there was news. He stopped seeing her as "the recruiter" and started looping her in before a req even opened. That's what the partnership looks like when it's working.

Worked example — Closing Devon with Marcus

Marcus opens a senior backend req. Watch the whole partnership run.

At intake, Yara doesn't take the JD at face value. She asks, "if someone had everything except the warehouse-robotics experience, would you still talk to them?" Marcus admits yes — Go is the real must-have, robotics is a nice-to-have. The bar just got honest, and her candidate pool just got real.

She sources four profiles and runs a calibration review before going wide. Marcus flags that a polished big-tech resume would hate a scrappy Series B, and points at Devon Asante's profile: "more like this one." Yara re-aims the entire search around thrives in chaos, not most credentialed.

Two weeks later, thirty screens deep with no perfect match, she advises honestly: the stack is scarce, the comp band is low for this market, here are the trade-offs. Marcus bumps comp eight percent and adjusts the level. The pool opens up.

Devon interviews. Yara drives the feedback — scorecards same day, debrief the next morning, decision by Friday. No four-day silence for Devon to cool off in. The offer goes out fast, Devon accepts, and Yara hands off to Pri Venkat in People Ops for comp paperwork and onboarding.

One hire. One req that could have died like the one Yara watched in week one. The difference was never the sourcing tool — it was a recruiter who ran the partnership instead of just filling an order.