The sourcing gap between channels is not marginal. Referral data compiled for 2026 shows about 34% of referred candidates get hired against just 2–5% of candidates sourced from job boards, and companies under twenty years old lean on referrals harder than anyone — roughly 30% of their hires. For a US startup trying to reach a second-year student at an IIT, NIT or IIIT, that ratio decides everything: you do not have the engineering hours to filter a job-board flood. Here are the six channels that actually work, in rough order of signal density.
Key takeaways
- Referrals convert at roughly 34% against 2–5% for job boards — signal density, not volume, is the constraint for a small team.
- Open-source contributor graphs are the highest-signal cold channel: the artefact and the candidate arrive together.
- Campus routes are built for final-year volume hiring and are the wrong shape for one remote part-time role.
- Whatever the channel, verification of identity has to be separate from evaluation of ability.
Why the obvious channels disappoint
Two routes look right and mostly are not. The first is the campus placement cell, which is designed around final-year students, fixed placement seasons and companies hiring in batches — the wrong shape entirely for one part-time remote role, and it puts you in a queue behind employers with recognisable names. The second is the mass internship job board, which delivers exactly the problem the wider market already has: LinkedIn has reported roughly 11,000 job applications a minute, a flood that is now AI-assisted on the candidate side — we covered what survives it in our guide to screening developers in the AI résumé flood. Neither channel is useless, but both invert the ratio you want — maximum volume, minimum signal — and a small team pays for that inversion in engineering hours. The methods below cost less time per qualified candidate.
The six channels, ranked by signal density
1. Open-source contributor graphs. Find the repositories adjacent to your stack, read the recent merged pull requests, and email the contributors whose work you liked. The evaluation is already done — you saw the code before you saw the person. India makes this unusually productive: GitHub’s Octoverse reports India now has the world’s largest open-source contributor base. 2. Verified student networks. Curated pools where identity and institute are already confirmed, which removes the impersonation risk that makes cold hiring feel unsafe. 3. Referrals from engineers you have already hired. One good Indian hire compounds into a network; referral hires also reach full productivity around 25% faster. 4. Competitive programming and hackathon rosters. Public, ranked and easy to verify, though they measure a narrower skill than shipping. 5. Student developer communities and campus tech clubs. Reaching organisers directly beats posting into a group. 6. Inbound from your own content. Publish something students want to read and a slow trickle of self-selected candidates arrives — the highest-quality channel and the slowest to build.
Running any channel without wasting a fortnight
- Write the ticket before the outreach. One real issue from your backlog, scoped to about a week. It is your job description, your test and your onboarding, all at once.
- Pick two channels, not six. Open-source outreach plus one verified pool is enough for a single role. Running all six produces a pipeline you cannot service.
- Verify identity before you evaluate ability. Institute email confirmation linked to the GitHub account. This is the step that makes remote hiring across borders feel ordinary.
- Cap the funnel at ten candidates. A small team can genuinely assess ten people. Beyond that you are skimming, which reproduces the job-board problem you were avoiding.
- Screen on artefacts in twenty minutes. One merged PR, one live project, 200 words of their writing. Our case for hiring 2nd-year Tier-1 developers covers why this segment repays the twenty minutes.
- Pay for the trial and state the overlap hours. A paid week on a real ticket, with two to four hours of live overlap defined in writing — the IST↔US playbook has the scheduling.
- Keep the runners-up warm. The second-best candidate for this ticket is often the best candidate for the next one, six months from now.
Where Tierones fits
Channel two on that list is the one we built. Tierones is an invite-only network of students verified through their institute email at IITs, NITs and IIITs, where Tier Rank converts commits, reviews and shipped projects into a signal you can read without knowing anything about Indian engineering colleges. It exists because the sourcing maths above is unforgiving for a small team: you need a pool where identity is already settled and the artefacts are already attached, so your engineering hours go into reviewing a trial ticket rather than filtering an inbox. Post what you need and we will surface the students whose work already looks like it.
FAQ
Can we just post on an Indian internship job board?
You can, and you will get volume rather than signal. Job boards convert at roughly 2–5% from application to hire against about 34% for referred candidates, and an unknown US startup posting a remote role in India attracts a very large, largely unfiltered response. If you post, pair it with at least one narrower channel.
Do we need to open an Indian entity to hire a student remotely?
For a part-time student contractor, generally no. The common structure is a direct contractor agreement covering scope, hourly rate and IP assignment, paid through a standard international remittance service against a monthly invoice. Take local advice before converting anyone to full-time, but a scoped paid trial does not require an entity.
How do we avoid fake GitHub profiles and inflated résumés?
Verify identity separately from ability. Institute email verification ties a person to a real campus, and linking that identity to the GitHub account closes the impersonation gap. After that, read one merged pull request and its review conversation, then finish with a paid trial ticket in your own repository.
Hiring remote engineering help this quarter? Tell us what you need — we’ll show you the right 40, not the loudest 4,000.