← Back to Guides

2026-02-01

How to Source Developers on Hacker News: A Recruiter's Complete Guide

How to Source Developers on Hacker News: A Recruiter's Complete Guide

Hacker News isn't just a content aggregation platform—it's one of the highest-concentration pools of active software developers on the internet. With 600,000+ registered users and daily submissions from engineers shipping real products, HN represents untapped sourcing gold for technical recruiters willing to put in the work.

Unlike LinkedIn where developers are passively employed and job-hunting, Hacker News attracts builders, open-source maintainers, and technical founders who are actively engaged in their craft. They're reading code, discussing architecture, and solving hard problems. That engagement signal matters.

This guide shows you exactly how to source developers on Hacker News, filter for quality candidates, and approach them in ways that actually convert.

Why Hacker News Is Worth Your Time as a Recruiter

Before we dive into the tactical how-to, let's be clear about the why. Most recruiters skip Hacker News entirely because it doesn't have a native "job search" interface. That's actually the advantage.

Lower competition: You won't be competing with 200 other recruiters messaging the same JavaScript developer. The friction of the platform keeps most sourcers out.

Higher-signal candidates: People who spend time on Hacker News are self-directed learners. They read deeply about technology, care about code quality, and engage with complex problems. These traits correlate strongly with engineering ability.

Founder and indie developer access: You'll find technical founders, CTO-level talent, and experienced engineers who've exited companies. This demographic is nearly impossible to reach through traditional channels.

Real-time skills visibility: Unlike a resume or LinkedIn profile, Hacker News posts reveal what someone is actively thinking about, building, and learning right now. This is much fresher signal than a job application.

Geographic diversity: While LinkedIn's user base skews toward specific regions, Hacker News has strong representation across EMEA, Asia-Pacific, and distributed communities worldwide.

The tradeoff is that Hacker News sourcing requires more manual work and pattern recognition than using a paid recruiter database. But the quality of conversations and the likelihood of reaching someone genuinely interested in the right opportunity make it worthwhile.

Understanding the Hacker News Community and User Behavior

Before you start sourcing, you need to understand how Hacker News actually works and who participates.

The platform basics: Hacker News is built on YCombinator's open-source software (available on GitHub). Users submit links or text posts, others vote and comment, and the algorithm ranks content by engagement velocity and age. Top posts stay visible for about 24 hours.

Peak traffic times: Most submissions and comments happen between 7am-4pm PT (US West Coast time). If you're in Europe or Asia, keep this in mind when you're looking for fresh discussions and contributor activity.

User reputation system: A user's karma score is public and visible on their profile. This reflects accumulated upvotes on their submissions and comments. Someone with 10,000+ karma has been a consistent, valued contributor over months or years. That's a meaningful signal.

Community norms matter: Hacker News has strong unwritten rules. "Ask HN" posts (direct questions) are tolerated but low-status compared to sharing builds or insights. Overt self-promotion is heavily downvoted. Recruiters who show up pitching jobs get flagged and buried.

The implication for sourcing: You can't directly recruit on Hacker News. You can't post job listings in comments. You can't DM people saying "we're hiring." What you can do is identify strong developers, research them thoroughly, and reach out respectfully off-platform.

Step 1: Identify Developer Activity Signals on Hacker News

To source effectively on Hacker News, you need to know what signals indicate a high-quality developer.

Posts and Submissions

A developer's own submissions tell you a lot:

  • Technical deep-dives: Posts about debugging a specific problem, writing a new parser, or optimizing a bottleneck indicate someone who thinks carefully and communicates clearly.
  • Tools and projects shared: If someone built an open-source library and posted it on HN, they've done work that exists in public. Check GitHub for repo quality, commit history, and documentation.
  • "Show HN" posts: These are building projects in public, sharing side projects, or announcing new tools. This is a very strong signal of someone actively shipping code.

Comments

Comments reveal character and depth of knowledge:

  • Technical credibility: Look for comments that get upvoted because they contain novel insight, correct misconceptions, or provide context no one else mentioned. These comments usually have 50+ points and 3-5 follow-ups.
  • Answering specific questions: When someone asks for advice on a tool or architecture, the best answer comes from someone with direct experience. Developers who answer these questions clearly and thoroughly are worth noting.
  • Engagement pattern: Someone who replies thoughtfully to follow-ups, admits when they're wrong, and engages in long-form debate shows communication skills and intellectual honesty.

Profile and Karma

Visit a prospect's HN profile:

  • Karma threshold: Under 500 karma = very new or lurker. 500-5,000 = regular contributor. 5,000+ = trusted community member. 20,000+ = power user who's been valuable for years.
  • Post history: Scroll their recent submissions. What topics do they focus on? Are they consistent? Flaky contributors with sporadic activity are less reliable than someone who posts regularly.
  • Time on platform: Check when they joined. Someone with 5+ years on HN and consistent karma growth has demonstrated staying power and values the community.

Step 2: Use Advanced Searches and Filters to Find Candidates

Hacker News doesn't have a native advanced search, but there are tools that layer on top of it.

Algolia Search (Built into HN)

The official HN search uses Algolia's index. Navigate to https://hn.algolia.com/ and use these search strategies:

By technology and keyword: Search for specific frameworks, languages, or tools. For example: - "PostgreSQL performance tuning" — finds engineers deep in database work - "Rust async runtime" — targets Rust specialists - "React Server Components" — targets React experts - "Kubernetes networking" — finds infra/DevOps engineers

By username: If you know someone's HN handle, search for all their posts and comments to see their full activity pattern.

By domain: Search "site:github.com" combined with a language or framework to find GitHub projects discussed on HN.

By date range: The Algolia interface lets you filter by date. This helps you find recent discussions and trending topics where active developers cluster.

Specialized Tools

Several third-party tools index and analyze Hacker News data:

Tool Use Case Cost
HN Digest Email digest of top posts by category Free
Hacker News API Programmatic access to all posts/comments Free (rate-limited)
Whoishiring.com Extracts "Who is Hiring" and "Freelancer" threads monthly Free
HN Trending Shows trending topics and discussions in real-time Free
NexusHN Search and filter HN by technology, date, and engagement Paid tier available

For sourcing specifically, the Hacker News API is most useful. The API is free and doesn't require authentication for basic queries. You can write a simple script to pull comments and posts mentioning specific technologies, then filter by user karma and engagement.

Manual Scrolling Method (Still Effective)

Don't discount the simple approach: spend 15 minutes each morning scrolling the front page and the "newest" section of Hacker News. As a sourcer, you'll start to recognize patterns:

  • Which users consistently submit quality content
  • Which technologies are trending (hiring signal: if everyone's talking about Go, there's likely strong demand)
  • Who leaves thoughtful, detailed comments
  • Which GitHub projects are gaining traction

Keep a running list of usernames that stand out. Revisit their profiles every 2-3 weeks.

Step 3: Evaluate and Research Candidates Found on Hacker News

Finding an active, high-karma Hacker News user is not the same as finding a hire. You need to validate:

Verify Technical Skill

Check their GitHub profile: Almost every developer on HN has a GitHub link in their profile. Look for:

  • Contribution frequency: Regular commits indicate active development work, not just a resume project. Someone with commits in the last week is currently coding.
  • Repository quality: Read a few of their repos' READMEs. Is documentation clear? Are there tests? Is the code organized? These reflect engineering maturity.
  • Collaboration: If they contribute to open-source projects with other developers, how collaborative are they? Do they respond to pull request reviews? Do they file good issues?
  • Languages and frameworks: Does their GitHub activity align with your open roles? If you're hiring for React specialists but they write mostly Python, that's a signal.

Read their recent HN comments: Pull up their last 20-30 comments. Do they write about technology thoughtfully? Do they get upvoted for technical insight? Do they help others? This reveals communication style and depth.

Assess Seniority and Fit

Use HN discussion participation to gauge level:

  • Juniors often ask for advice, share learning projects, and ask "why" frequently. They're valuable if you're building junior programs.
  • Mid-level engineers answer questions, contribute to infrastructure discussions, and deploy projects to production. Most hireable segment.
  • Senior engineers and architects discuss trade-offs deeply, reference past experience, and think about scalability and team dynamics. Harder to hire but most valuable.

Seniority often correlates with comment depth and karma, but not always. Someone with 2,000 karma might be more senior than someone with 8,000—karma reflects consistency and community participation, not pure technical ability.

Geography and Timezone

Check the HN profile bio and comment history for location clues: - Do they mention their city or country? - Do their post times cluster around specific hours (suggesting a timezone)? - Are they discussing local tech communities or conferences?

If you need someone in a specific timezone or region, this matters.

Employment Status Signals

Read between the lines:

  • Recent "Show HN" posts about a side project: Might indicate someone with bandwidth to explore new opportunities.
  • Comments about frustrations at current job: "We're using ancient tech" or "management doesn't value engineers" — soft signal they might be interested in moving.
  • Statements like "I just shipped X": If it's a personal project, might be side work. If it's company work, they're actively employed.
  • Hiring announcements in their posts: If they mention "my startup is hiring," they're founder or early employee.

Important: Never use employment status assumptions as a reason to contact someone. Use them as context. Employment status isn't a predictor of fit or interest.

Step 4: Find Contact Information and Reach Out Responsibly

This is where most sourcers fail. They identify a great candidate on Hacker News and then blow the outreach.

How to Find Contact Information

Check their HN profile: Many developers link to personal websites, blogs, or Twitter accounts. These often have email or contact forms.

GitHub profile: If they have a GitHub link, their GitHub profile often lists email, website, or Twitter. Some developers specifically list contact info for professional inquiries.

Personal website or blog: Visit the URL if it's in their profile. Blogs often have "Contact" pages. Personal sites frequently have email addresses.

LinkedIn: Search for the person's name + key details (city, company name if visible) on LinkedIn. It's not always the same person, so verify by checking their GitHub and HN handles.

Twitter search: Many developers use the same username across platforms. A Twitter search for their HN handle often surfaces their account, which includes location and sometimes email.

University or company website: If they mentioned their employer or alma mater in comments, check those websites for faculty/staff directories.

Email finder tools: Clearbit, RocketReach, or Hunter.io can sometimes surface work email addresses, but they're less reliable for personal emails.

Crafting the Outreach Message

This is critical. Your message will be received by someone skeptical of recruiters.

Do this: - Personalize heavily: Reference something specific they posted or built. "I saw your HN post about optimizing PostgreSQL for time-series data—our backend team is tackling the exact same problem." - Explain why you found them specifically: "We're hiring mid-level Go engineers. I noticed your consistent contributions on HN discussing Go performance tuning, and your open-source library has 2K stars on GitHub." - Be transparent about the ask: "I'm not going to DM you a job posting. I think there might be a genuine fit based on your interests, and I'd love a 15-minute conversation to see if it makes sense." - Respect their time: Keep it short (under 200 words). Don't attach a job description. Don't ask for a call immediately. - Add value or genuine interest: "I found a post you made in 2023 about WASM performance that influenced our architecture decision. That kind of thinking is what we're looking for."

Don't do this: - Generic "We're hiring!" messages - Irrelevant opportunities (don't pitch iOS roles to a backend engineer) - Multi-page job descriptions - Requests to connect on 3 platforms before talking - Guilt or pressure ("We've been looking for weeks") - Overly casual tone if it doesn't match their communication style

Where to Send It

Email is still best for a cold outreach. It's less intrusive than DM and signals you put effort into finding contact info.

If you can only find Twitter, DM is acceptable with a very brief note: "Hi [name], I found your work on [specific topic] through HN. Would you be open to a brief conversation about an opportunity? Let me know if email is better: [email]."

Don't rely on LinkedIn InMail unless it's actually connecting to their LinkedIn—many strong developers don't maintain active LinkedIn profiles.

Response Rate Expectations

Be realistic. If your outreach is good and highly personalized:

  • 5-15% response rate is normal from cold outreach to developers on Hacker News
  • 10-20% of responses will translate to actual conversations
  • 1-3% of conversations will convert to interviews

This means you need to source 20-30 strong candidates for every 1-2 interviews you land. The quality of those conversations is much higher than typical LinkedIn sourcing.

Step 5: Systematic Sourcing—Build a Repeatable Process

Ad-hoc sourcing on Hacker News works, but it's inefficient at scale. Build a system.

Weekly Sourcing Routine

Monday mornings (15 minutes): - Scroll HN front page and "newest" section - Note 3-5 usernames with interesting activity - Add to your tracking spreadsheet

Wednesday (20 minutes): - Check Algolia for trending keywords in your hiring stack - Run 2-3 searches for relevant technologies - Identify 5-8 candidates from results - Quick GitHub scan for obvious no-fits

Friday (30 minutes): - Dig deeper on 5-8 candidates you shortlisted - Find contact info - Draft personalized outreach for 2-3 strongest fits - Send them

This is about 1 hour per week for a systematic process that generates 10-15 qualified candidates per month.

Tracking Spreadsheet Structure

HN Username GitHub Profile Technologies Karma Last Activity Contact Info Outreach Date Status Notes
john_dev github.com/johndev Go, Rust, PostgreSQL 4,200 2 days ago john@website.com 2026-02-15 Replied Interested in DevOps roles
alice_builds github.com/alicebuilds React, TypeScript, Node 2,800 1 week ago alice.twitter 2026-02-20 No response Strong React contributor

Update this weekly. It becomes your sourcing pipeline.

Scaling with Automation

If you're hiring multiple roles, you can automate parts of this:

  • RSS feeds: Subscribe to HN job-related threads using an RSS reader. Set keywords for your tech stack.
  • Hacker News API scripts: Write a simple script that queries the API for posts/comments containing your keywords, then ranks by karma.
  • GitHub API: Once you have a list of usernames, batch-query their GitHub profiles to check for activity and skills.

You still need to manually review and personalize outreach, but automation handles the initial filtering.

Common Mistakes Recruiters Make on Hacker News

Mistake 1: Direct Recruitment on the Platform

Posting "We're hiring" in threads or comments gets flagged. Don't do it. Hacker News has dedicated monthly "Who is Hiring" threads—use those if you want a job board presence, but they're less useful for sourcing because you're competing with hundreds of other employers.

Mistake 2: Contacting Based on One Good Comment

One thoughtful comment doesn't mean someone is a good hire. You need to see a pattern. Spend 10 minutes on their profile before reaching out.

Mistake 3: Not Reading What They Actually Write

If you reference something they posted that shows you didn't actually read it, they'll know. "I saw your post about machine learning" followed by a backend role is disqualifying for many developers.

Mistake 4: Treating HN Sourcing Like LinkedIn

The people here are different. They value deep technical knowledge, intellectual honesty, and being treated with respect. Generic recruiter templates don't work. Personalization isn't optional; it's everything.

Mistake 5: Giving Up After Low Response Rates

Sourcing on Hacker News is a numbers game, but the quality is higher. Expect lower response rates than LinkedIn, but expect better conversations with people who are genuinely interested in the right role.

Tools and Resources for HN Sourcing

How Zumo Complements HN Sourcing

While Hacker News is excellent for identifying active, engaged developers, it doesn't show the full picture of someone's engineering output. Zumo analyzes developers' GitHub activity to reveal:

  • Real shipping velocity: Commit patterns, pull request frequency, and code review participation
  • Technical depth: Repository complexity, language distribution, and contribution patterns
  • Collaboration style: How developers work with teams on open-source and private projects
  • Growth trajectory: Skill expansion over time across languages and frameworks

You can combine HN sourcing (for community signal and recommendation discovery) with Zumo (for GitHub-based technical validation) to build a two-signal sourcing approach that's incredibly effective.

FAQ

Can I post job listings on Hacker News?

Hacker News has a dedicated "Who is Hiring?" thread posted on the first day of each month. You can post there, but it's more of a job board listing than targeted recruiting. For sourcing specific candidates, direct outreach off-platform is more effective.

What's a good response rate for HN outreach?

5-15% response rate is normal from well-personalized cold outreach. If you're getting under 5%, your messages aren't personalized enough. If you're getting above 15%, you've found an especially receptive audience or are sourcing for very in-demand skills.

Should I reach out to developers I see arguing in HN comments?

Use caution. Someone engaging in a heated technical debate is active and engaged, but reaching out immediately after a conflict they're in feels opportunistic. Wait a few days and reference their substantive points, not the argument itself.

How do I verify someone's actually a good developer before reaching out?

Check three things: (1) GitHub contribution history for active commits, (2) Repository quality and documentation, (3) Upvoted HN comments that show technical depth. If all three check out, they're worth contacting.

Can I source for roles on other platforms the same way?

Similar principles apply to Stack Overflow, GitHub discussions, Reddit (r/learnprogramming, language-specific subreddits), and Discord communities. Each has different norms. Reddit and Discord tend to be more open to casual conversation. Stack Overflow is more professional. Always respect each community's culture before outreaching.

Next Steps: Build Your HN Sourcing Pipeline

Hacker News sourcing takes more work than LinkedIn spray-and-pray, but the quality of candidates is dramatically higher. You're reaching engineers who actively engage with their craft, think deeply about technical problems, and are likely to have real conversations about opportunities that excite them.

Start with one week of daily scrolling to get comfortable with the community. Then implement the weekly routine outlined above. Track everything in a spreadsheet so you can iterate on what messaging works.

The developers on Hacker News are worth the effort. Make sure your outreach reflects that respect.

Want to validate candidates you source on HN with GitHub-based signals? Explore how Zumo shows the full technical picture of developers you're considering.