Skillsync Finds Engineers by What They Have Actually Built, Not What Their Resume Says

The Macro: Resumes Are Terrible at Showing What Engineers Can Do

Technical hiring is broken in a specific way: resumes and interviews measure the wrong things. A resume tells you where someone worked and what their job title was. A coding interview tells you whether they can solve algorithmic puzzles under pressure. Neither tells you whether they can actually build the thing you need built.

The best signal for engineering ability is shipped work. What has this person actually built? What languages and frameworks did they use? How complex was the code? Did other developers find it valuable? This information exists in the open for millions of developers. Their open source contributions, pull requests, and project histories on GitHub are a detailed record of their real capabilities.

But nobody uses this data for hiring because it is unstructured and time-consuming to analyze. A recruiter cannot spend two hours reading through a candidate’s GitHub contributions for every engineering role. And GitHub’s own interface is not designed for evaluating skill profiles.

Skillsync, backed by Y Combinator, automates this analysis. They build structured skill profiles from developers’ open source contributions, then let companies search for specific technical capabilities.

The Micro: Search by Skill, Not by Keyword

Narayana Aaditya Ganeshkumar (CEO) and Nishant Joshi (CTO) built Skillsync with a Cursor-like search interface. Companies type natural language queries like “deployed custom neural nets on edge” or “built high-throughput message queues in Rust” and get a list of developers whose open source work demonstrates that capability.

The platform goes beyond keyword matching. It analyzes the actual code in a developer’s contributions to understand what they built, the technologies they used, and the complexity of their work. This creates profiles that are significantly more informative than LinkedIn descriptions or resume bullet points.

Once companies find relevant engineers, Skillsync provides tools to qualify, shortlist, and engage with them. The platform can generate personalized outreach emails that reference specific contributions the candidate has made.

At $499 per month, the pricing is accessible for most engineering teams. Customers include Bun, Ramp, and Zed, which are exactly the kind of developer-centric companies that would value skill-based hiring over credential-based hiring.

Competitors include LinkedIn Recruiter (keyword-based search on self-reported profiles), Triplebyte (standardized technical assessments), and Hired (marketplace model). Skillsync’s advantage is that their data is objective: code contributions are verifiable, not self-reported.

The philosophy resonates: “Open source software powers the internet, but the builders that make it happen often remain invisible.” There are tens of thousands of highly skilled engineers whose work is public but who are not actively job-seeking on traditional platforms.

The Verdict

Skillsync is attacking the right problem with the right data source. Open source contributions are the most honest signal of engineering ability available.

At 30 days: how many developer profiles has Skillsync indexed, and how accurate are the auto-generated skill assessments?

At 60 days: what is the response rate when companies reach out to developers found through Skillsync? Cold outreach that references specific code contributions should convert well.

At 90 days: are companies hiring through Skillsync seeing better retention and performance than through traditional channels?

I think Skillsync is building something important. The gap between what resumes say and what engineers can actually do is a real problem, and open source contributions are the best available proxy for real ability. If the skill profiling is accurate, this becomes the default tool for technical recruiting at engineering-first companies.