LinkedIn Post Ideas for Recruiters

400 resumes, one senior engineering role, six-second average glance per resume in my first pass. Here's exactly what earned 30 seconds instead of six. Specific impact numbers over responsibility lists. "Reduced deploy time from 45 minutes to 6" got a real read. "Responsible for CI/CD pipeline improvements" got the six-second treatment and a pass. A project description matching our actual tech stack's real problems, not just keyword-matching our job posting's buzzwords. One candidate described debugging a specific class of race condition we'd genuinely struggled with. That single line moved them to the top of my pile. Career narrative coherence. A resume that explained why someone moved from a big company to a startup, in one clean sentence, read as intentional. The same move with no context read as a red flag I had to investigate, which cost them time I didn't always have to spend. What ended reads early: generic objective statements, a skills section listing every technology ever touched with no depth signal, and formatting so dense I couldn't scan it in the six seconds I actually have per resume in round one. 400 resumes taught me: specificity beats breadth every single time, and the resumes that got 30 seconds all did one thing the six-second ones didn't — they answered "so what" before I had to ask.

A rejected candidate from four years ago is now a hiring manager. He remembered exactly how our process treated him, and it nearly cost us a partnership that mattered. We'd ghosted him after a final-round interview. Not maliciously — a req got frozen, and nobody on our team closed the loop. He found out by watching the role quietly disappear from our careers page. Four years later, his company became a potential client for one of our portfolio businesses. He recognized our company name in the deal room and told the other side, casually, "just so you know how they treat candidates." The deal still closed. It shouldn't have been that close. I only know this story because he told me directly, at a conference, years after the fact, not angry, just matter-of-fact about the impact. The math recruiters never see: every ghosted candidate is a future hiring manager, founder, board member, or reference-checker who remembers exactly how you treated them when you didn't need anything from them yet. The cost isn't the one hire you lost. It's every future interaction with someone who now has a reason to remember your name unfavorably. A two-line rejection email costs ninety seconds. I've started sending them for every single candidate who reaches a final round, no exceptions, expired req or not.

40% reply rate from cold outreach to senior engineers, a group notoriously immune to recruiter messages. Here's the exact template, annotated. Subject line: "Question about [specific project/tool they've written about]" — never "exciting opportunity." Specificity in the subject line alone roughly doubled my open rate compared to generic hooks. Opening line, always referencing something real: "Saw your post about [specific technical decision] — we hit a similar tradeoff building [specific thing] and I'm curious how you'd have approached ours." This isn't flattery. It's a genuine technical question, which signals I actually read their content instead of mail-merging a template. Middle: two sentences on the actual role, framed as a problem, not a job description. "We're trying to solve [specific technical challenge], not just fill a headcount number." Close: a low-commitment ask. "Open to a 15-minute call, no pressure either way" outperformed "let's schedule an interview" by a wide margin — the second framing implies commitment before any real interest exists. The line that does the most work is the opening reference to something specific and real. Generic personalization ("I saw your profile") gets ignored. Specific personalization ("I saw this exact thing you built") gets read, because it proves I did the homework most recruiters skip.

50 placements, tracked for 90-day attrition against time-to-fill. The tension between these two metrics is real, and my own data surprised me. Placements filled in under 21 days: 90-day attrition rate of 14%. Placements filled in 22-45 days: 90-day attrition rate of 6%. Placements filled in 45+ days: attrition rate back up to 11%, likely reflecting a different problem — roles that took that long usually had a fuzzy success profile to begin with. The pattern: speed alone isn't the enemy. Speed without a properly calibrated intake process is. My fastest fills were often reqs where the hiring manager had crystal-clear requirements from day one, letting me move fast without cutting corners. My slowest, messiest fills were usually reqs where nobody had actually agreed on what "great" looked like before I started sourcing. What I changed based on this data: I now refuse to start active sourcing until an intake meeting produces a written, specific success profile, even if that adds three or four days upfront. Those three days have measurably paid for themselves in the attrition numbers since. Time-to-fill and quality-of-hire aren't actually opposed. A good intake process is the variable that determines whether you get both or neither.

A candidate turned down a competing offer paying 30% more than ours. I asked her directly why, expecting a vague answer about culture. She gave me a specific one that changed how I pitch every role since. The competing offer came from a larger, better-known company. Ours was smaller, less prestigious on a resume, and paid meaningfully less. Her actual reason: she'd spoken to the hiring manager at the competing company for exactly 20 minutes across the entire process, versus over two hours with our hiring manager across multiple conversations. "I know exactly what I'd be walking into with you. I have no idea what I'd be walking into there, and the money doesn't fix not knowing." The manager relationship, not the compensation, won. She specifically cited one moment: our hiring manager had shared a real, current team problem she'd be inheriting, unprompted, before the offer was even extended. What changed in how I pitch roles since: I now push every hiring manager to have at least one substantive, unscripted conversation with finalist candidates before an offer goes out, not just a polished "sell" call. The pitch that wins isn't the one promising the most. It's the one that removes the most uncertainty about what the job will actually feel like.

Every failed search I've run traces back to the intake meeting, not the market. Three specific mistakes, all mine at some point. Mistake one: accepting a vague success profile. "We need someone strong technically who's a good culture fit" tells me nothing actionable. I now require the hiring manager to describe what this person's first 90 days actually look like, in specific tasks, before I'll open the req. Mistake two: uncalibrated must-haves. A hiring manager once listed "8+ years experience" as a hard requirement, then hired a candidate with 4 years I'd pushed through anyway, because the actual requirement was skill depth, not tenure. Now I ask, for every "must-have": "if someone had everything else but not this, would you truly reject them?" Half the time, the honest answer reveals it's a preference, not a requirement. Mistake three: skipping the "who's done this well before" question. Now I open every intake with: "think of someone who's excelled in a similar role, what specifically made them excellent?" This single question surfaces the real success profile faster than any other part of the meeting. The question that now opens every intake I run: "if this search fails, what will the reason turn out to be?" Hiring managers usually already know. Getting them to say it out loud upfront saves months later.

Our ATS uses AI to screen resumes. A growing number of candidates use AI to write them. I've started to wonder what signal actually survives when both sides are automated. The uncomfortable pattern I've noticed: AI-optimized resumes increasingly all read the same way — strong keyword density, perfectly structured bullet points, impact metrics that sound impressive and are occasionally difficult to verify in interview. The screening AI likely scores these well, precisely because they're optimized to be scored well, not because they reflect the strongest candidate. Where I think human judgment has to re-enter, deliberately: the interview itself, specifically unscripted follow-up questions. I've started asking candidates to walk me through the actual context behind a claimed metric on their resume, in their own words, live. The gap between a polished bullet point and someone's real, unrehearsed explanation of it is where the signal still lives. What I've stopped trusting as much: resume screening scores as anything more than a rough first filter. What I've started trusting more: a short, specific, unscripted conversation early in the process, before either side has over-optimized their presentation. The arms race isn't going to resolve by picking a side. It resolves by moving the signal to the place neither side can fully automate yet.

The behind-the-scenes life of one req, start to signed offer. Candidates never see any of this. They just experience the delays. Week 1: hiring manager submits the req. Finance pushes back on headcount, a two-week approval fight candidates will never know caused their first-round delay. Week 3: intake meeting, finally, after approval clears. Success profile defined, sourcing begins. Week 4-6: sourcing and screening. Fourteen candidates screened, five advanced. Week 7: first-round interviews. One candidate's second-round gets delayed nine days because a key panelist is on unplanned leave — invisible to the candidate, who just experiences radio silence and assumes disinterest. Week 9: final round. Two finalists. Week 10: internal debate over which finalist, three days of hiring-committee back-and-forth candidates never see, framed to them simply as "we're finalizing our decision." Week 11: offer approval, another internal delay, this time compensation-committee review. Week 11, day 4: offer extended, ten weeks after the req was submitted, four weeks of which were pure internal friction invisible to every candidate in the pipeline. Candidates rate the "silence" as the worst part of hiring. Most of it isn't recruiter neglect. It's stakeholder friction happening entirely behind a curtain candidates never get to see.

Five questions I wish more candidates asked me, because the answers reveal things a job description never will. 1. "How did the last person in this role spend their first month?" The answer reveals whether onboarding is a real program or a sink-or-swim improvisation. 2. "What's a decision this team made recently that didn't work out, and what happened?" Reveals whether mistakes get discussed honestly or buried. 3. "What would make someone unsuccessful in this specific role, six months in?" Almost nobody asks this. The answer is usually more honest than any list of "requirements," because it forces the hiring manager to describe real failure modes, not aspirational ones. 4. "How has this role changed in the last year?" Reveals whether the job description matches current reality or is stale. 5. "What's the hardest part of this job that doesn't show up in the posting?" Hiring managers who answer this thoughtfully are usually the ones running a genuinely well-managed team. Most candidates ask questions designed to make them look good: "what growth opportunities exist here." These five questions instead extract real signal about what the job will actually feel like day to day, which is the information that actually prevents a bad-fit hire six months down the line.

Salary ranges in every job posting: yes or no, recruiters? I'll go first with data, not just opinion. We added ranges to every posting eight months ago, in markets where it wasn't yet legally required. Application volume dropped roughly 15% in the first month — fewer people applying speculatively, hoping the number would work out. What improved: application quality rose noticeably. Candidates who applied were self-selecting into a range they'd actually accept, which cut our "great candidate, wrong comp expectations" late-stage drop-off by more than half. Time saved in later-stage negotiation: significant. Comp conversations that used to happen awkwardly in round three now happen, or don't, before round one even starts. The counterargument I hear most from peers who still resist ranges: "it removes negotiation flexibility." My honest response after eight months of data: the flexibility we lost was mostly the flexibility to waste three interview rounds before discovering a mismatch that a single line in the posting would have prevented. I'm firmly in favor now, based on our own numbers, not just the transparency argument. Recruiters still resisting: what's your data actually showing, or is this still a gut call for your team?