Picture this: you want to hire someone who has genuinely woven AI into how they work every day. You open LinkedIn, type “AI native,” and see thousands of profiles. The problem: they all say exactly the same thing.
LinkedIn is a network of declarations, not evidence. The best AI practitioners rarely have up-to-date profiles there — they’re too busy building things. A recruiter who searches only on LinkedIn is browsing a fraction of the available market.
Below you’ll find six categories of places where AI talent actually congregates — with specific platforms and outreach strategies for each.
Where They Show Their Code and Models
Places where candidates leave traces of real work — long before anyone thinks about recruiting. Here you find proof, not claims.
Search by topic, not by name. Commit frequency and README quality say more than a list of tools in a CV. The Stars tab reveals what a candidate actually cares about.
The GitHub of the AI world — over a million open-source models. Filter by task (RAG, text classification) and check the authors. A published fine-tuned model is better verification than any certificate.
15M users with a public ranking: Novice → Grandmaster (fewer than 300 people worldwide). Completed competitions are a concrete, verifiable signal of real skill.
The platform for tracking ML experiments. Public reports show how someone thinks about evaluation — what they measure, how they document, how they iterate on results.
Where They Debate in Real Time
When OpenAI drops a new model, serious practitioners are analysing it within hours — on Discord and Slack, not LinkedIn. These are the places to watch if you want to see who actually understands what’s happening.
Key Discord Servers
Hugging Face Discord — tens of thousands of members, channels organised by topic: NLP, computer vision, audio, new models. Active commenters in the technical channels are candidates worth having a deeper conversation with.
Latent Space Discord — a more selective community built around the Latent Space podcast and newsletter. The level of technical discussion is higher than average, and the signal-to-noise ratio is noticeably better.
OpenAI Developer Forum — the official developer forum. People who regularly help others with technical problems (not just asking questions themselves) are a solid signal of real depth.
AI Tinkerers — a network of local AI meetups with its own Discord. Worth checking whether there’s a chapter in your city or region.
Slack Communities
MLOps Community Slack — tens of thousands of engineers and data scientists focused on deployment, not just research. A strong channel for finding people who bridge AI and production systems.
Rands Leadership Slack — over 20,000 engineering managers and senior technical people. Not strictly an AI community, but that’s exactly where AI-savvy decision-makers sit — both those looking for them and those who are them.
How to approach candidates on Discord
Opening with a job offer is the fastest way to burn a contact. Instead: observe for a few weeks, identify people who consistently add value, then send a private message that references something specific they said or built.
Where They Write and Think — Newsletters, Substack, and X
People who build public knowledge about AI are often the most advanced practitioners. Writing forces you to organise what you know — it’s a natural filter for deeper understanding. Their content is a better CV than their CV.
Substack
There are hundreds of active AI newsletters on Substack — ranging from deeply technical to product-focused and strategic. Authors who regularly publish practical content — analyses of specific models, descriptions of their own experiments, real deployment case studies — are exceptionally valuable candidates. They have both the knowledge and the ability to communicate it.
How to find them: use Substack’s search by topic (AI, LLM, machine learning, prompt engineering). Pay attention to authors with 1,000–10,000 subscribers. They’re advanced enough to write substantively, but not yet so prominent that they receive a hundred job offers a week.
X / Twitter — #buildinpublic
The #buildinpublic hashtag brings together creators who document their projects publicly — including a large number of people building AI tools. It’s a unique source because you can see both the product and the thinking process behind it.
How to search effectively: instead of scrolling the hashtag wholesale, search by specific tools and frameworks. Tweets mentioning LangChain, Claude API, Cursor, or Anthropic in the context of someone’s own project — not just sharing news links — are the signal of a practitioner, not an observer.
Towards Data Science and Medium
Towards Data Science (a Medium publication) is the largest platform for technical AI and data science writing. Authors with many regularly updated posts who describe their own projects and experiments — not just explain tutorials — are solid candidates worth reaching out to.
How to tell depth from surface-level content: A valuable article describes decisions and trade-offs, not just steps. “Why I chose RAG over fine-tuning and when I regretted it” — that’s depth. “Top 10 AI Tools for 2026” — that’s not.
Where They Compete — Hackathons and Competitions
AI hackathons are a natural competence filter. They show who can ship a working prototype under time pressure, with limited resources, in an unfamiliar team. That’s verification no interview can replicate.
Hackathon Platforms
Lablab.ai — one of the largest online AI hackathon platforms. Every project has a public page with a description, demo, and team listing. It’s a ready-made database of candidates with confirmed practical experience.
Devpost — a hackathon aggregator with filters by AI topic. After each event, projects remain publicly accessible — you can browse participants and even reach out through their profiles.
Kaggle Competitions — not hackathons in the classic sense, but weeks- or months-long contests with a publicly visible leaderboard. Anyone in the top 10% of any competition is an unusually credible candidate.
Local meetups and hackathons — in most major cities there are now regular AI gatherings. Smaller scale, but easier direct contact and the ability to build relationships before you ever have a role to fill.
Three Strategies for Recruiting from Hackathons
Sponsor the event
Access to the participant list, judging projects, a natural reason to talk to finalists. The cost is a fraction of what a recruitment agency charges.
Review after the fact
Most hackathons publish recorded demo days and project repositories. You can browse them weeks after the event and reach out to the builders at your own pace.
The one revealing question
“What would you have done differently with a week instead of a weekend?” — the answer reveals the candidate’s level of reflection and technical maturity.
Where They Teach and Learn — Course Communities and Academia
The best students from deeplearning.ai or fast.ai are often ready to work — they’re just looking for somewhere to apply what they know in a real context.
Education Platforms with Active Communities
deeplearning.ai community — Andrew Ng built not just courses but an entire community around them. The forum and Discord groups are active, and people who’ve completed the specialisations and remain engaged on the forum are often candidates at a solid level of practical capability.
fast.ai forums — a more technical and niche community, focused on practical deep learning. The level of discussion is high. Active forum members who share their own projects are strong candidates for engineering roles.
Reddit r/learnmachinelearning — 600,000+ members at varying levels. Less useful for sourcing than the more technical r/MachineLearning, but good for observing the trajectory of people actively learning and documenting their progress publicly.
The Academic Angle
Several universities have active AI and machine learning student groups running their own projects, hackathons, and workshops — often with access to real data from partner companies.
Partnership strategy: instead of waiting for graduates, get in earlier. Sponsoring a thesis project, running a workshop, or giving a student group a real problem to solve builds a talent pipeline 12–18 months before anyone else knows these people exist.
One important distinction: an AI course certificate is not the same as practical experience. How to tell them apart is covered in our article on candidate verification. The academic world gives you access to people who often have deep theoretical knowledge but need mentoring in applied contexts — that’s a completely different profile from the self-taught practitioner you find on GitHub.
Where Nobody Is Looking — Sources That Give Recruiters an Edge
This section is for recruiters who want to stay one step ahead. The sources below are all publicly accessible, but rarely treated as recruiting channels.
Product Hunt
Product Hunt is where creators launch new digital products. Every day, dozens of tools appear — and increasingly, many are AI applications built by one or two people.
Why it matters for recruiting: someone who shipped their own AI tool on Product Hunt has completed a full practical test — from idea, through implementation, to public launch and real user feedback. That’s more than most candidates have done in any job.
How to use it: filter products by the AI tag, sort by popularity, browse creator profiles. Outreach: reference their product with a genuine question or observation — don’t open with a job offer.
Indie Hackers
Indie Hackers is a community of people building their own products and micro-businesses. Many recent ones are AI-powered. Creators publish revenue reports, descriptions of technical challenges, and product retrospectives.
What this gives a recruiter: someone who built and maintains their own AI product — even one generating $500 a month — has operational competence no course teaches. They understand the full cycle: idea, implementation, deployment, users, iteration. That’s rare.
Outreach approach: integrate with the community before you look for candidates. People on Indie Hackers are generally open to conversation if you approach with genuine interest in their project, not a ready-made offer.
Reddit — r/MachineLearning and r/LocalLLaMA
r/MachineLearning — 3 million members, discussion at research and engineering level. People who regularly comment with substantive contributions — analysing papers, sharing experiment results — are potential candidates for roles requiring deep technical knowledge.
r/LocalLLaMA — a fast-growing community focused on running models locally, without APIs. Members often have very deep knowledge of model architecture, optimisation, and on-device deployment. Rarely visited by recruiters — which makes it all the more valuable.
YC Alumni and AI Grant
Y Combinator Alumni Network — YC graduates have been through intense vetting and built a product. Many YC companies from the last two years are AI-native. Some didn’t survive or got acquired — their founders and early employees are back on the market.
AI Grant — a grant program supporting researchers and builders working on open AI projects. The list of recipients is a public database of highly advanced candidates who’ve already passed substantive selection.
Buildspace graduates — Buildspace was an educational program for AI product builders, which wrapped up in 2024. Its alumni, who completed intensive cohorts of AI product building, are a publicly accessible talent pool — search on LinkedIn for “Buildspace s4/s5” or look in alumni communities.
How to Make This a System, Not a One-Time Search
The biggest mistake in sourcing AI-native talent is treating it like a one-off recruitment campaign. You open LinkedIn or GitHub, search for a week, close the tab, and come back in a year. Meanwhile, the best AI talent is passive — they’re not looking for work until they have a reason to.
Building a real pipeline means maintaining a consistent presence in the places described in this article. Three levels of engagement you can roll out gradually:
Observing — you subscribe to newsletters, follow a few Substacks, monitor one or two Discord servers. You don’t engage, but you see who stands out. Time investment: 30–60 minutes a week.
Building presence — your company has a GitHub account with open projects, sponsors a local AI meetup, has employees writing technical posts on a blog or LinkedIn. This isn’t mass employer branding — it’s a signal to a narrow community that you know what you’re doing.
Active sourcing — you regularly browse Product Hunt’s AI tag, attend hackathons, reach out to specific project authors or article writers. You have a list of people you’re building a relationship with before any specific role opens up.
Instead of a Summary: One Test for the Recruiter
Before you send your next LinkedIn message, ask yourself: does the candidate you’re looking for even have an active LinkedIn profile? If they’re genuinely AI-native — they probably spend time in half the places described in this article, and last updated their LinkedIn profile sometime last year.
AI-native talent isn’t waiting for your job posting. You have to find them where they are. And where they are is where things are being built — not where they’re being talked about.
Also read: How to Verify Whether a Candidate Actually Works with AI — a practical protocol with interview questions, a live task, and a downloadable checklist.
