Most searches begin with a job description and a start date. The recruiter takes the spec, nods, and goes off to source. It feels efficient. It's the reason so many searches run long.
The fastest searches we run start somewhere else: with a real conversation. Thirty minutes at the kick-off, before a single CV is touched, asking the questions that surface what the job description leaves out. It's not a formality. The answers reshape the entire search, and they routinely save weeks at the back end - the difference between a hire in three weeks and a hire in three months.
Here are the five we ask in every kick-off, and why each one matters more than it looks.
1. "Who was the best person who ever did this job - and what made them great?"
Job descriptions describe a role. This question describes a person. When a hiring manager tells us about the best engineer they ever worked with in this kind of seat, we learn what "great" actually means to them - the working style, the way of thinking, the thing that made the difference. That's the real target, and it's almost never written down.
Skip this, and you source to the spec. The spec gets you "qualified." This question gets you "right."
2. "If this role is wildly successful in a year, what will have changed?"
Most briefs list responsibilities. Far fewer define success. But the answer to this question tells us whether you're hiring someone to build, to fix, to scale, or to stabilise - and those are different people. A backend engineer who thrives building greenfield is not always the one who thrives untangling years of technical debt.
Defining the outcome upfront stops the slow, expensive drift where a shortlist of genuinely strong candidates keeps getting rejected because none of them fit a goal that was never made explicit.
3. "What would make you say no to someone who looks perfect on paper?"
This is the unspoken-bar question, and it's the one that saves the most time. Almost every hiring manager has a deal-breaker they haven't articulated - a working style that won't survive their team, a background that's been burned before, a non-negotiable that lives in their head. If we don't draw it out at kick-off, we find it the hard way: by presenting a candidate who ticks every box and getting a rejection no one can quite explain.
Asking it directly, early, can save a month on its own.
4. "Where will this hire actually come from?"
Strong hiring managers usually have an instinct here - the three or four companies doing similar work, the teams whose engineers tend to thrive in their environment, the adjacent domains worth raiding. That instinct sharpens our market map enormously.
It also surfaces hard truths early. If the only people who fit are at two companies that pay 30% above your budget, that's a conversation for day one, not day forty. We'd rather recalibrate the profile or the package at the start than discover the mismatch after weeks of fruitless sourcing.
5. "How fast can you move when you meet someone great?"
The best passive candidates in Israeli hi-tech are reachable for a window, not forever. They're not running a process; they're considering one conversation. If your interview loop takes three weeks to schedule and another two to decide, you'll lose them to a company that moved in days - no matter how good your sourcing was.
Asking this at kick-off does two things. It sets a realistic expectation about pace, and it gets the hiring manager to pre-commit to a process that matches the calibre of person we're about to bring them. The search is a partnership; this question makes that explicit before the clock starts.
Why thirty minutes here saves sixty days later
Every one of these questions exists to remove a specific source of delay: sourcing the wrong profile, chasing the wrong outcome, hitting an unspoken deal-breaker, aiming at a market that doesn't match the budget, or losing great people to a slow loop. Left unanswered, each of these quietly adds weeks. Answered at kick-off, they compound into a search that points at the right people from day one and moves fast enough to actually land them.
This is why we treat the kick-off as the most important meeting of the entire engagement, not a box to tick on the way to sourcing.
How we do it at Once-HR
These five questions are asked by a founder - Inbal or Eva - not handed to a junior to work through a checklist. That matters, because the value isn't in the questions themselves; it's in the follow-ups, the reading between the lines, and the judgment to know when an answer doesn't quite add up. That's senior work.
What the founders learn then sharpens everything that follows. The calibrated profile guides our sourcing agent as it maps the market and surfaces passive candidates, so the AI is aimed at the right target from the first search rather than the third. And because the whole search runs on the Once platform, the picture we built together in that first conversation stays visible to you throughout - no drift, no guessing what we're looking for.
Thirty minutes, five questions, and a search that closes in weeks instead of quarters. It's the cheapest speed you'll ever buy.
Want a kick-off that actually sets your search up to move fast? Talk to Inbal or Eva.