A YC-backed startup wants to make developer hiring less about résumés and more about actual code. Whether that's revolutionary or just obvious depends on who you ask.
There's a recurring frustration among technical recruiters that goes something like this: the engineers they most want to hire are often the ones least interested in keeping their LinkedIn profiles current. The best systems programmers, infrastructure specialists, and compiler engineers? They're on GitHub at 2 a.m. fixing race conditions in Tokio, not polishing bullet points about "synergistic team collaboration."
Skillsync, a San Francisco startup emerging from Y Combinator's Winter 2026 batch, thinks it has found a way through this impasse. Rather than asking recruiters to divine skill from job titles and buzzwords, the company's platform analyzes what developers have actually built in public—their open-source contributions—and translates that work into searchable technical profiles.
The pitch is straightforward, maybe even self-evident: hire people based on what they can demonstrably do, not what they say they've done.
When GitHub Becomes the Résumé
Co-founders Narayana Aaditya Ganeshkumar and Nishant Joshi know the open-source world from the inside. The pair previously grew a Rust project to more than 20,000 stars—a detail they mention not as credential-padding but as proof they understand which developers recruiters struggle to reach. These are people who treat LinkedIn the way most of us treat MySpace: a relic we vaguely remember exists.
Skillsync's core interface borrows a page from modern AI tooling. The company describes it as "Cursor-like," allowing recruiters to search using plain English rather than Boolean operators or job title matching. Type in "WASM compilers" or "deployed custom neural nets on edge devices," and the system surfaces developers whose GitHub commits actually reflect those capabilities.
This gets granular fast. A search for "Senior Rust Systems Engineer" doesn't just pull profiles listing Rust as a skill. It identifies candidates whose public repositories show work with unsafe Rust abstractions, custom memory allocators, or lock-free concurrency patterns—technical depth extracted from code, not from a checkbox.
The distinction matters more than it might seem. Anyone can list "Rust" on a résumé. Significantly fewer people have debugged lifetime issues in async code at 3 a.m. or contributed patches to the Rust compiler itself.
The X-Ray Trick
Perhaps the most immediately practical feature—and the one that feels designed for recruiters already eyeballs-deep in GitHub rabbit holes—is what Skillsync calls its "X-ray" view.
The concept is almost charmingly simple. Add the word "skills" in front of any GitHub URL ("skills github.com/username"), and you get an instant breakdown of what that developer has built. Not what they've claimed to know. What they've actually shipped.
For recruiters who spend hours manually combing through repositories, trying to assess whether someone who contributed to rust-lang/rust three years ago still writes production code, this is the kind of time-saver that might justify a subscription on its own. The platform also filters by seniority, location, and specific repos, plus generates personalized outreach messages that reference actual contributions—a tactic meant to cut through inbox noise.
Early feedback from recruiters on Reddit suggested the profiles looked polished, though the free tier has limitations that prompted some grumbling. One of the co-founders showed up in the thread to field questions directly, which is very YC: when in doubt, talk to users.
Not Exactly a New Idea, But Maybe a Better Execution
Skillsync isn't operating in a vacuum. Enterprise platforms like SeekOut already parse GitHub activity and assign "Coder Scores" to candidates. Tools like hireEZ pull data from GitHub, Stack Overflow, and Kaggle to build technical profiles. The broader trend toward code-based recruiting has been underway for years, driven by the reality that great engineers often have mediocre LinkedIn presences.
What Skillsync seems to be betting on—perhaps more than the founders expected—is that interface matters as much as data. The company positions itself not as another talent aggregator but as a search engine purpose-built for capability-first discovery. Whether that distinction holds up under competitive pressure remains to be seen.
The company has backing from Y Combinator and has worked with Character Labs, the program run by Character Capital. John Zeratsky from Character Capital announced the launch on LinkedIn (ironic, given the platform's premise) and praised the founders' work. Demo Day for the W26 batch is slated for March 24, 2026, which gives Skillsync a few months to refine its pitch and build traction before the broader investor spotlight hits.
The Platform Goes Live, Sort Of
The platform is live now at skillsync.wiki, though the company's blog section still shows a "coming soon" placeholder—a small detail that hints at a team still racing to build while simultaneously launching. Pricing tiers exist but require login to view, which is either strategic gatekeeping or a sign the company is still figuring out monetization.
That ambiguity isn't necessarily a problem. Early-stage startups often launch with more questions than answers, and Skillsync has at least identified a real pain point. Technical hiring remains brutally competitive, and GitHub's role as a professional portfolio continues to expand whether LinkedIn likes it or not.
The big question—one that won't be answered for months—is whether capability-based search represents a genuine shift in how companies source engineers, or whether it's simply a better mousetrap for a problem recruiters have already learned to work around.
For now, Skillsync is positioning itself at the intersection of two well-established trends: AI-powered recruiting tools and the growing legitimacy of open-source contributions as career currency.
Whether that intersection becomes a highway or a side street depends largely on whether recruiters believe code tells a better story than credentials. Based on how many engineers avoid LinkedIn these days, the founders might be onto something.
