Most job boards recycle the same listings. You've seen it — the same "Senior React Developer" posting on LinkedIn, Indeed, and Glassdoor, all pointing to the same ATS portal where your application disappears into a void.

The developers who find the best roles — the ones with interesting work, fair pay, and actual growth — aren't always grinding job boards. They're fishing in different waters. GitHub repos, HackerNews threads, Discord servers, and niche developer communities surface opportunities that never make it to mainstream job sites.

This guide breaks down exactly how to tap those channels. And if you're pairing community outreach with traditional job boards, use our Job Search Query Builder to craft precise Boolean queries that cut through the noise on every platform.

Why Mainstream Job Boards Miss the Best Tech Roles

A significant chunk of tech hiring happens outside the standard posting pipeline:

Startups post on HackerNews because their audience is already there
Open source projects recruit contributors who become employees
Remote-first companies post in Discord and Slack communities where their team already hangs out
Agencies and consulting shops fill roles via referral networks, not job boards

These aren't scraps — they're often the roles with the most autonomy, the most interesting problems, and competitive pay that doesn't get benchmarked against a bloated corporate band.

HackerNews "Who's Hiring" Threads

Every month, HackerNews runs a "Who's Hiring?" megathread. It's one of the most reliable sources of direct, unfiltered job posts from actual founders and hiring managers.

How to use it:

Go to news.ycombinator.com and search "Who is Hiring" or bookmark the monthly thread directly
Use Ctrl+F in your browser to search for your stack (e.g., TypeScript, Rust, Go) or desired location (remote, Berlin, NYC)
Look for posts that include salary ranges — a strong signal the company is serious and transparent
Reply directly in the thread to express interest; many founders prefer this over formal applications

What to look for in a listing:

Direct contact (email or a Calendly link) — skips the ATS entirely
Tech stack details — shows the team knows what they're building
Team size and funding stage — sets expectations on role scope
"REMOTE" in all caps — typically means genuinely remote, not "remote flexible" (which usually means hybrid)

The HN community skews toward engineering-heavy startups and YC-backed companies. If that's your target, this thread alone is worth checking every first Monday of the month.

GitHub: From Contributor to Employee

GitHub isn't a job board, but it's one of the best places to get hired in tech. Companies watch their contributors.

Find Companies by Their Stack

Search GitHub for repos in your domain:

topic:react stars:>500 language:TypeScript
topic:machine-learning stars:>1000
topic:kubernetes language:Go

Find repos that are actively maintained (recent commits, open issues being responded to). These are teams with velocity — and often hiring.

Check the "Jobs" Section and README

Many open source projects include a link to their company careers page in the README or a JOBS.md file. Look for:

CTRL+F: "hiring" "careers" "jobs" "join us" "we're looking for"

Contribute First, Apply Second

This is the long game, but it works. A well-crafted pull request to an active repo puts your name in front of the engineering team in the most credible way possible — you've already shipped something useful.

Even small contributions (fixing docs, resolving a good first issue) get you on the radar. If a role opens up, you're not a cold applicant. You're someone they already know.

Developer Discord and Slack Communities

Dozens of active communities post jobs in dedicated #jobs or #opportunities channels. These are often roles posted by members — people you've already been talking to.

High-signal communities to join:

Reactiflux (React) — one of the most active frontend communities; #job-board channel
Python Discord — large and active; has a jobs channel
The Programmer's Hangout — general dev community with a jobs board
BotsOnDiscord / Indie Hackers Discord — great for startup and solo founder roles
Remote|OK Discord — remote-only roles, curated

Search for "[job]" or "[hiring]" in channels — many communities have tagging conventions so posts don't get lost.

The advantage here: you can ask follow-up questions in real time, see how the hiring manager or founder engages with the community, and build a warm connection before you apply.

Reddit: r/forhire and Niche Subreddits

Reddit has a surprisingly strong job market hiding in plain sight.

Key subreddits:

r/forhire — general freelance and contract work; filter by [HIRING] flair
r/cscareerquestions — not a job board, but company-specific threads often surface via search
r/remotejobs — curated remote listings
r/webdev — small but active jobs thread in the monthly megathread
Niche subreddits: r/devops, r/MachineLearning, r/golang — check pinned posts and monthly threads

Use Reddit search with precise terms: "hiring golang engineer" subreddit:golang or just use Google:

site:reddit.com "hiring" "senior engineer" "remote" 2026

That's a Boolean search pattern — and if you want to build variations fast, the Job Search Query Builder handles these kinds of multi-keyword, multi-platform strings in seconds.

Pairing Community Search with Job Boards

Community channels surface roles that job boards miss — but job boards still have volume. The smart move is to run both in parallel.

When you do hit job boards, bring the same precision you'd use in a GitHub search. Vague keyword searches return vague results. Build tight Boolean strings:

("staff engineer" OR "principal engineer") AND ("distributed systems" OR "platform") AND remote

Pair your community leads with a targeted board search using our Job Search Query Builder to make sure you're not leaving roles on the table while you wait for a GitHub contribution to bear fruit.

The Meta-Skill: Staying Visible

The best developers don't just apply to jobs — they're findable. A few habits that compound over time:

Keep your GitHub green. Activity signals you're currently building
Comment on HN threads in your domain — your username becomes searchable
Write one thing publicly per month — a short blog post, a Twitter/X thread, a detailed Stack Overflow answer
Update your LinkedIn headline with your actual stack, not just your job title

This isn't self-promotion for its own sake. It's making sure that when a founder or hiring manager is looking for someone with your exact background, they find you — even when you're not actively searching.

Quick Reference: Where to Look by Goal

| Goal | Channel | |---|---| | YC / funded startup | HackerNews Who's Hiring | | Open source adjacent role | GitHub topics + contribution | | Async remote culture | Remote-focused Discord communities | | Freelance / contract | r/forhire, Indie Hackers | | Volume + variety | Job boards with Boolean search |

Wrapping Up

Job boards aren't going away — but they're one layer of a deeper search. The developers landing the most interesting roles are doing a mix: precise Boolean searches on traditional boards, combined with direct community engagement where companies are hiring without posting formally.

Start with one channel you're not currently using. Spend 30 minutes in the next HN Who's Hiring thread, or find one GitHub repo in your domain and open your first issue. The compounding effect of showing up in the right places is real.

And when you're ready to sharpen your board searches, the Job Search Query Builder builds the exact Boolean strings you need — no syntax memorization required.

Further reading: Boolean Search Tips for Indeed Job Listings | LinkedIn X-Ray Search: Find Profiles Google Indexes But LinkedIn Hides

How to Find Tech Jobs Using GitHub, HackerNews, and Developer Communities