Skillsync: Hiring Engineers by Code, Not Resumes

Skillsync is a San Francisco–based startup founded in 2025 and part of the Winter 2026 batch. With a compact but focused team of just two founders, the company set out to solve a problem that has quietly plagued modern technical hiring for years: the disconnect between how engineers are evaluated and how they actually work. Instead of relying on resumes, buzzwords, or self-reported experience, Skillsync is built around a simple but powerful idea—engineers should be discovered and evaluated based on their real code.

The platform helps companies find engineers directly through their open-source contributions, particularly on GitHub. Rather than asking candidates to summarize years of work into bullet points, Skillsync analyzes public code, repositories, and contribution histories to create structured skill profiles. These profiles reflect what engineers have actually built, not what they claim to know. In doing so, Skillsync challenges the resume-centric hiring model that dominates recruiting today.

The motivation behind Skillsync is deeply personal for its founders. Having experienced firsthand how much elite technical talent remains invisible to traditional hiring systems, they saw an opportunity to rebuild sourcing from the ground up—starting with code as the primary signal of capability.

Who Are the Founders Behind Skillsync?

Skillsync was founded by two engineers who lived the problem before deciding to fix it: Narayana Aaditya Ganeshkumar and Nishant Joshi.

Narayana Aaditya Ganeshkumar, often known as Nars, is the co-founder and CEO of Skillsync. His background spans engineering, product development, and organizational psychology—a combination that strongly influences the company’s philosophy. Before Skillsync, Nars helped take an open-source Rust project from zero to over 20,000 GitHub stars. Through that journey, he observed something striking: many of the most capable engineers contributing to the project had little to no traditional professional presence. They weren’t optimizing LinkedIn profiles or polishing resumes—they were shipping high-quality code.

Nishant Joshi, co-founder and CTO, brings deep technical credibility to the platform. A top 1% Rust developer, Nishant previously worked on type-safe payment infrastructure before turning his attention to people search. His transition from building critical backend systems to fixing hiring itself underscores Skillsync’s thesis: hiring is a systems problem, and it deserves the same level of engineering rigor as infrastructure or payments.

Together, the founders combine lived experience from open source, deep technical expertise, and a clear frustration with broken hiring norms—making Skillsync as much a mission as it is a product.

Why Is Hiring from Open Source So Hard Today?

On the surface, GitHub seems like a goldmine for technical talent. Millions of engineers publicly contribute to repositories, collaborate on complex systems, and leave behind a rich trail of real work. Yet in practice, hiring from open source remains surprisingly difficult.

The challenge lies in scale and interpretation. While GitHub contains vast amounts of signal, that signal is unstructured. Repositories, commits, issues, pull requests, and discussions don’t neatly map to standardized job requirements. Recruiters and hiring managers are often left manually browsing profiles, scanning commit histories, or relying on surface-level indicators like star counts—which say little about individual contribution or depth of expertise.

Even founders who ran their own open-source projects encountered this problem. Despite knowing their contributors personally and seeing their work up close, identifying and shortlisting the right engineers for full-time roles was still tedious. If hiring elite contributors from one’s own project was difficult, doing so across the entire open-source ecosystem was nearly impossible.

As a result, many companies default back to resumes and LinkedIn searches—tools optimized for visibility, not ability. Skillsync was created to close this gap and make open-source talent not just visible, but searchable.

How Does Skillsync Turn Code into Structured Skill Profiles?

At the core of Skillsync is its ability to transform raw open-source activity into structured, searchable skill profiles. The platform analyzes public GitHub contributions and extracts meaningful signals about what an engineer has actually built.

Rather than treating repositories as static portfolios, Skillsync looks at patterns: the kinds of systems engineers work on, the technologies they use, the complexity of problems they solve, and the domains they repeatedly contribute to. This analysis is then translated into a structured profile that reflects real capabilities.

For example, instead of labeling someone as a “Rust developer,” Skillsync can surface much more specific signals—such as experience building WASM compilers, deploying custom neural networks on edge devices, or designing low-level systems infrastructure. These are the kinds of nuances that rarely appear on resumes but matter deeply in advanced engineering roles.

Importantly, engineers don’t need to sign up, maintain profiles, or optimize for discoverability. Skillsync works entirely on public data, allowing talent to be found based on work rather than self-promotion.

What Makes the Search Experience Different from Traditional Recruiting Tools?

Skillsync introduces a Cursor-like interface designed for intent-driven search. Instead of filtering by job titles, years of experience, or keyword-stuffed skills lists, users can search directly for capabilities.

A hiring manager might type: “engineers who have experience with WASM compilers,” and Skillsync returns a shortlist of engineers who have demonstrably worked on that exact problem. This flips the traditional sourcing workflow on its head. Rather than guessing which keywords might correlate with a capability, companies can search for the capability itself.

The result is a faster, more precise hiring process. Teams can qualify candidates based on real work, shortlist engineers already operating in their domain, and engage them directly—without requiring those engineers to ever touch a resume.

This approach is particularly powerful for roles where precision matters and false positives are costly.

Why Is Skillsync Especially Valuable for Hard Engineering Domains?

Not all engineering fields are equally represented in traditional hiring platforms. While some domains reward visibility and networking, others reward deep focus and technical rigor. Fields like low-level systems, infrastructure, robotics, and compilers often fall into the latter category.

In these areas, the strongest engineers frequently prioritize building over branding. Many don’t maintain polished LinkedIn profiles, and some avoid resumes altogether. Their real signal lives in code, design decisions, and long-term contributions to complex systems.

Skillsync is uniquely well-suited to surface this hidden talent. By grounding its analysis in actual work, the platform uncovers engineers who would otherwise remain invisible to recruiters relying on conventional tools. This makes it especially valuable for companies hiring for niche, high-impact technical roles where quality matters more than volume.

How Does Skillsync Change the Power Dynamics of Hiring?

Traditional hiring often rewards those who are best at presenting themselves rather than those who are best at building. Skillsync shifts that balance by making output—not self-description—the primary currency.

For engineers, this means their work speaks for itself. They don’t need to constantly update profiles, tailor resumes, or optimize keywords to stay discoverable. For companies, it means access to a broader and more authentic talent pool—one that includes engineers who may never apply through conventional channels.

This dynamic also reduces noise. Instead of sifting through hundreds of loosely matched resumes, teams can engage a smaller number of highly relevant candidates whose work aligns closely with their needs.

What Is the “Skills” GitHub URL Feature and Why Does It Matter?

One of Skillsync’s most distinctive features is its lightweight “X-ray vision” tool for GitHub profiles. By simply adding the word “skills” to a GitHub URL—such as skillsgithub.com/username—users can instantly view a structured summary of an engineer’s unique capabilities.

This feature makes qualification dramatically faster. Recruiters and hiring managers can quickly understand what an engineer has worked on, how their experience maps to open roles, and whether it’s worth starting a conversation.

Crucially, this happens without friction. Engineers don’t need to opt in, and companies don’t need to run complex analyses. It’s an elegant example of Skillsync’s broader philosophy: reduce overhead, increase signal.

What Does Skillsync Reveal About the Future of Hiring?

Skillsync reflects a broader shift in how talent is discovered and evaluated. As work becomes more public, more collaborative, and more output-driven, resumes are increasingly misaligned with reality. The future of hiring favors evidence over assertions.

By building a system that maps real technical work to real opportunities, Skillsync points toward a hiring ecosystem where capability is easier to find and harder to fake. It suggests a future where open source is not just a community resource, but a primary talent graph for the world’s most demanding engineering roles.

Why Does Open Source Represent a Long Tail of Hidden Capability?

Open source is vast, decentralized, and quietly powerful. Beneath the surface of popular repositories lies a long tail of contributors doing exceptional work without recognition. These engineers may never appear in recruiter searches, yet they build the systems that power modern software.

Skillsync exists to surface this hidden capability. By treating open source as a signal rather than a hobby, the platform unlocks access to talent that has always been there—but was simply too hard to find.

In doing so, Skillsync doesn’t just help companies hire better. It helps redefine what merit looks like in engineering, grounding opportunity in actual work and making the invisible visible at last.