Absolutely. Our hardest-to-fill role was Senior AI Infrastructure Engineer, a hybrid of distributed systems, GPU optimization, and MLOps. The market was red-hot, and passive candidates weren't responding to generic outreach.
Our pipeline strategy had three layers, but one tactic stood out:
We launched a "Build in Public" talent community, a private, invite-only Slack channel and monthly virtual roundtable for 50-60 top-tier engineers we'd previously engaged (including those who'd declined offers or were "not looking"). We didn't pitch jobs. Instead, we shared real engineering challenges we were solving, like "How we cut LLM inference costs by 60%" or "Debugging silent data drift in production", and invited discussion.
Why it worked:
1. Value-first engagement: We positioned ourselves as peers, not recruiters. Engineers stayed because they learned something, not because they were being sold to.
2. Warm, trusted access: When the AI infrastructure role opened, we didn't blast a job post. We messaged 8 people from the community with: "Remember that scaling problem we discussed last month? We're building a team to solve it. Want to lead it?"
3. Speed and relevance: All 8 were pre-qualified, understood our tech stack, and respected our engineering rigor.
Result:
- We filled the role in 19 days (vs. 78-day average for similar roles)
- The hired candidate came from the community and had declined us 10 months earlier
- 3 others from the group joined within 6 months for adjacent roles
The most successful tactic wasn't sourcing; it was building ongoing intellectual reciprocity. Hard-to-fill roles aren't won with job ads; they're won by earning trust long before the requisition exists.