Sourcing and outreach tools for recruiters

Search craft: the Narrowing String

Most sourcing searches fail in one of two directions: so broad the result list is unreadable, or so narrow the one right person is excluded by their own word choice. The working method, call it the Narrowing String, goes wide on titles and tight on evidence. People describe the same job with different titles, so group the synonyms: ("data engineer" OR "analytics engineer" OR "platform engineer"). Then narrow with terms that only show up when someone has done the work, like the specific tools of the trade, and cut the noise with NOT terms for recruiters, aspirants, and adjacent roles.

The Boolean Search Builder assembles that structure without the parenthesis debugging, and the Sales Navigator Search Builder translates the same intent into Navigator filters. Feed both from the Job Description Keyword Finder, which pulls the load-bearing vocabulary out of the intake doc. One honest caveat: a search string is only as good as the intake behind it. If the hiring manager cannot say what distinguishes a good candidate, no operator syntax will.

Outreach candidates do not resent

Every in-demand candidate has a folder of identical messages: unnamed "exciting opportunity," no company, no range, no evidence the sender read past the current job title. That style fails structurally, not just aesthetically, because it asks the busier person to do the work of discovering whether the message is relevant. The reply-worthy version does the opposite. It names the role and the company, states the range if policy allows, and points at one specific thing in the candidate's history that made them the target rather than one of two hundred.

The Connection Request Writer drafts that kind of note, short and grounded in what you tell it about the person. Two constraints worth respecting. First, personalization is a courtesy, not a trick; if the role is a poor fit, a well-written message just gets you a politer no. Second, silence is data. If a well-defined role with a fair range gets no replies, the problem is usually upstream of the messaging, and the kindest thing you can do for your own pipeline is say so to the hiring manager.

Your profile is the landing page for every message you send

Candidates run the same background check on you that you run on them, just faster. Before replying to an InMail from a stranger, they click the name. What they find determines whether your carefully written message gets treated as a real opportunity or as spam with good grammar. A recruiter profile with a clear headline, a photo, a banner, and an About section that says which roles and markets you actually work reads as a professional; a skeleton profile reads as a mass mailer.

The LinkedIn Profile Score gives you the same audit your candidates get, and the profile optimization guide covers the fixes field by field. If you post occasionally, roles you are working, honest observations about your market, the Post Generator keeps that sustainable, and a lightly active profile compounds the credibility of every message sent from it.

The asking side of the interview

Sourcing gets the candidate to the door; the interview decides what happens there, and unstructured interviews are where good pipelines go to die. When every interviewer improvises, candidates are compared on different questions, which means they are not really compared at all. The fix costs one document: a shared question set drawn from the actual job description.

The Interview Questions Generator was built for candidates rehearsing, but it works identically from the asking side. Paste the posting, take the questions to the hiring manager, and agree on which ones every candidate will face. It is a small discipline that makes the eventual debrief an argument about evidence instead of an argument about vibes, and it is the part of this page most likely to improve who you actually hire.