# How to find engineers who are not on LinkedIn

Engineers who skip LinkedIn still leave their work in public, in the repos they own, the pull requests they get merged and the packages people install. So to find them, you search the work.

![How to find engineers who are not on LinkedIn](https://vamotalent.com/blog/find-engineers-not-on-linkedin/hero.jpg)

By Bolun Li, 2026-11-14.

Canonical: https://vamotalent.com/blog/find-engineers-not-on-linkedin

To find engineers who are not on LinkedIn, you search their work instead of their profiles. Engineers who skip LinkedIn still leave a public record, because they own repositories, get pull requests merged into projects other people depend on, and maintain packages that people install. So we start from the work, filter by place and history, and then match the work to a person.

## A Flutter app that needs to play audio

A Flutter developer who needs their app to play sound can install [just_audio](https://github.com/ryanheise/just_audio) or audio_service, two plugins that app developers put in their own apps to play audio. One person owns both plugins: [Ryan Heise](https://vamotalent.com/engineers/ryanheise), who is in Sydney.

On Ryan's card at the top of this post, look for just_audio and audio_service in his repositories, and check his garden to see how recently he has worked on them.

Say you need a Flutter engineer in Australia who knows audio. Most recruiters would search profiles for a Flutter title, an audio keyword and Australia, and that search misses Ryan, because he has no current title on record.

## Why your profile search won't return him

Ryan isn't unusual. Some engineers have no profile at all, and more of them have one that tells you very little. Once you start looking, you see the same cases again and again.

A lot of titles don't say much about the work. [Lahfir](https://vamotalent.com/engineers/lahfir)'s title on record is intern, and he's also the [top contributor](https://github.com/vercel-labs/agent-desktop/graphs/contributors) to agent-desktop, a command line tool from Vercel Labs that lets AI agents operate desktop apps through accessibility trees. If you search for senior engineers, he won't come up. Contractors and people at small companies often have titles that say just as little.

**Lahfir** (@lahfir): Computer Vision Research Intern at Vercel, United States. Builds vercel-labs/agent-desktop, vercel-labs/agent-browser, vercel-labs/portless. [profile](https://vamotalent.com/engineers/lahfir)

On Lahfir's card, look for agent-desktop in his repositories.

Profiles go stale, too. If someone last updated theirs three years ago when they were looking for a job, the title can be two promotions old. Recent graduates have the opposite problem, so their profile says "student" while their GitHub shows something people use.

Some builders have no title you can search at all. [Leon Lin](https://vamotalent.com/engineers/Leonxlnx) is in Munich, he has no title on record, and he builds tools for coding agents. One of them is [tastecode](https://github.com/Leonxlnx/tastecode), a desktop app for running coding agents on creative work, and he started it in July 2026.

**Leon Lin** (@Leonxlnx): Munich. Builds Leonxlnx/taste-skill, Leonxlnx/deepthink-showcase, Leonxlnx/convert-image-files. [profile](https://vamotalent.com/engineers/Leonxlnx)

On Leon's card, look for tastecode in his repositories, and check his garden for the work he has done since he started it in July 2026.

And if you only search in San Francisco and New York, you miss everyone else. [Max Schwenk](https://vamotalent.com/engineers/maschwenk), a staff engineer in Atlanta, is the most active contributor to [tsrs](https://github.com/oxc-project/tsrs), a Rust port of the TypeScript 7 type checker. That's a hard codebase, and anyone who opens the commit history can see his work.

We still use LinkedIn for work history. But it's a poor way to find engineers by what they can do, because a LinkedIn profile only holds what people chose to write about themselves. We compare the two directly on [Vamo vs LinkedIn Recruiter](https://vamotalent.com/vs/linkedin-recruiter), and we keep a roundup of [LinkedIn Recruiter alternatives](https://vamotalent.com/blog/linkedin-recruiter-alternatives).

## Five ways to look by hand, and what each way costs you

If the profile is the wrong place to start, the work is the right one. You can get to the work by hand in five ways, and each way is slower than the one before it.

**1. GitHub search.** You can filter users by location, language and followers, and it's free, but it's slow. People who post a lot collect more followers than people who ship, so the follower count can mislead you. We use GitHub search to check a hunch. There's more in [Vamo vs GitHub search](https://vamotalent.com/vs/github-search) and our guide to [GitHub recruiting](https://vamotalent.com/blog/github-recruiting).

**2. Contributor pages on the projects you depend on.** If your product runs on Postgres, Kafka or a particular framework, the people who contribute to that project already know your problems. It costs you time, because you have to check each person's location, how recent their work is, and whether they wrote real code or fixed typos.

**3. Package registries.** npm, PyPI, crates.io and similar registries list who maintains each package, which is how you would get from just_audio to Ryan. When a package has real downloads, other engineers trust the person who maintains it. Registries rarely have location data, so you spend your time matching each maintainer to a person and a place.

**4. Conference talks and papers.** Speakers and authors have usually done the work they talk about, and conferences post their programs in public. But only a small group of people speak, so you miss a lot of builders who don't present.

**5. Community spaces.** In Discord servers, forums and issue trackers, you can see who answers the hard questions. You learn a lot this way, but it's very slow, and people in these spaces didn't sign up to be recruited, so we only read there.

Pin, Noon and daily.dev have published longer roundups of these channels ([Pin](https://ghost.pin.com/sourcing-engineers-beyond-linkedin/), [Noon](https://www.noon.ai/blog/how-to-find-candidates-that-are-not-on-linkedin), [daily.dev](https://recruiter.daily.dev/resources/recruit-developers-who-never-update-linkedin)). Some of them quote statistics about how many engineers are missing from LinkedIn, and we couldn't trace those numbers to a source we trust, so we don't repeat them.

All five ways work, but each one only gets you through a handful of people a week.

## How you find him with one search

To do this at scale, you need a search where the work is already joined to the person. This request looks for Flutter engineers in Australia, ranked by their work on audio, and that's how Ryan comes up:

Ask Claude:

> Use Vamo to find Flutter engineers in Australia who build audio playback plugins, and tell me why each one fits.

```bash
curl -X POST https://api.vamotalent.ai/v2/developers/search \
  -H "Authorization: Bearer vamo_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "rank_by": ["v", "ANN", ["Embed", "Flutter audio playback plugins"]],
    "filters": ["And", [
      ["location_ids", "ContainsAny", { "place": ["Australia"] }],
      ["is_bot", "Eq", false],
      ["is_org_account", "Eq", false]
    ]],
    "rerank": "clef"
  }'
```

We left a lot out of that request: no title, no keyword list, and no requirement that anyone has a LinkedIn profile. We describe the work in a short phrase and put the place in as a filter, so you can swap in the work your role needs and the place where you hire.

You can handle the other cases the same way. Name a repository and you get its contributors, filtered by place, which is how Max comes up from tsrs. You can add employer history, school, title, seniority or languages as filters, so "worked at Stripe, lives in Denver" is one request. Once you find someone good, ask for other people who do similar work, in the same city or anywhere.

In Vamo you can run all of it from Claude, ChatGPT or Cursor over [MCP](https://vamotalent.com/mcp), in the app, or through the API. For every person, we return their [devRank](https://vamotalent.com/devrank), which is how we score their engineering work, and the repository or role that made them match. You can browse the Discover pages at [/engineers](https://vamotalent.com/engineers), or start from a project at [/repos](https://vamotalent.com/repos).

## Reading the people you found

A search gives you names, and then you still have to read each person's work. Two lessons from our course help with that:

- [The 90-second read](https://vamotalent.com/docs/learn/reading-the-profile/the-90-second-read): a fixed order for reading a GitHub profile. You look at the pinned repositories and whether each repository is original. Then you read the README of the strongest one, and then you check recent activity.
- [Verifying open source claims](https://vamotalent.com/docs/learn/reading-the-profile/verifying-open-source-claims): when a maintainer merges a pull request, the record is public and dated, and someone else has reviewed the code, so you can check a claim in about ninety seconds.

Some excellent engineers have an empty GitHub because their work is private. In [The empty GitHub](https://vamotalent.com/docs/learn/reading-the-profile/the-empty-github), we show you how to read an empty profile without treating it as a red flag.

## Appendix: run the search yourself

You can send the Flutter audio search to the API with your own key:

Ask Claude:

> Use Vamo to find Flutter engineers in Australia who build audio playback plugins, and tell me why each one fits.

```bash
curl -X POST https://api.vamotalent.ai/v2/developers/search \
  -H "Authorization: Bearer vamo_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "rank_by": ["v", "ANN", ["Embed", "Flutter audio playback plugins"]],
    "filters": ["And", [
      ["location_ids", "ContainsAny", { "place": ["Australia"] }],
      ["is_bot", "Eq", false],
      ["is_org_account", "Eq", false]
    ]],
    "rerank": "clef"
  }'
```

Each person comes back with their GitHub login, where they work and live, and the repository or role that made them match. You'll find every filter, sort and field you can send in the [search API reference](https://vamotalent.com/docs/reference/postv2developerssearch).

Get a demo: https://vamotalent.com/book-demo

## FAQ

**How do I find software engineers who are not on LinkedIn?**
Search their public work: the repositories they own, the projects they contribute to and the packages they maintain. Then filter by place and history, and match the work to a person.

**Is GitHub enough to find engineers?**
For engineers who work in public, it is the best single source. For engineers whose work is private, use referrals, employer history and the people they have worked with.

**Is there a LinkedIn Recruiter alternative for hiring engineers?**
Yes. Look for a search that ranks people by their engineering work and only uses profile data as a filter. We built Vamo to work that way, and we compare it to LinkedIn Recruiter on [this page](https://vamotalent.com/vs/linkedin-recruiter).

**Which sourcing tools reach passive engineers who are not active on LinkedIn?**
Use a search where the work is already joined to the person. In Vamo you find engineers by the repositories they own or contribute to, filter by place, employer, school or languages, and run it from Claude, ChatGPT or Cursor, in the app, or through the API.

**Is it OK to contact engineers through their open source work?**
Yes, if you're respectful. Talk about the work, keep it short, and don't message people in project spaces that aren't meant for recruiting.

If you have this problem, [connect Vamo](https://vamotalent.com/mcp) and run a search, or [book a demo](https://vamotalent.com/book-demo). We also wrote about [how to find cracked engineers](https://vamotalent.com/blog/find-cracked-engineers).
