# Connected Apps Earn Up to 2.9x the Messages. Source Who Skipped Them

_LinkedIn Hiring Assistant 2 boosts verified, receptive profiles with Connected Apps, so shortlists overlap. Here is how to find the engineers it ranks last._

- Canonical URL: https://www.refolk.ai/blog/linkedin-hiring-assistant-2-connected-apps-source-the-rest
- Published: 2026-11-06
- Reading time: 9 min
- Keywords: LinkedIn Hiring Assistant 2, LinkedIn connected apps recruiters, LinkedIn Hiring Assistant sourcing limitations, find engineers not on LinkedIn Recruiter, source GitHub developers outside LinkedIn

Once your Hiring Assistant seat updates in November, its shortlist will favor verified, responsive profiles with Connected Apps, which are the same profiles every other customer's agent pushes up. The senior engineers who ignore InMail and keep their work on GitHub get ranked last.

Hiring Assistant 2 reaches existing English-language Hiring Assistant customers automatically, at no extra cost. LinkedIn says members with a connected app get "up to 2.9x more recruiter messages." Below is how the shortlist is built, why your competitors' shortlists look like yours, and where to find the engineers at the bottom.

## What does LinkedIn Hiring Assistant 2 actually change?

Hiring Assistant 2 is an update to LinkedIn's paid AI sourcing agent. It adds three things to how candidates are ranked: trust signals (verification and Connected Apps), receptiveness indicators, and a memory of your past hires. Dan Reid, VP Product at LinkedIn Talent Solutions, announced it on September 29, 2026, and it rolls out from November.

Some details in the launch coverage are easy to misread:

- **It is free only if you already pay.** Hiring Assistant is a paid add-on. The November update is free only for global customers who already use Hiring Assistant in English.
- **"20,000 companies" is not 20,000 seats.** LinkedIn says over 20,000 companies use its agentic hiring products, including AMD, Cisco, Palo Alto Networks, and Zillow. That number covers all of LinkedIn's agentic products, not just Hiring Assistant.
- **"Up to 2.9x" means recruiter messages, not InMail replies.** The "up to" matters. It is a ceiling, not an average.
- **GitHub is not a confirmed partner.** LinkedIn's own announcement names Chess.com, ElevenLabs, and Medium, with work from Behance and Replit also displayable. Reports on GitHub conflict, so check inside the product before you assume it's live.

A **Connected App** is a third-party account (Replit, JetBrains, Medium and so on) that a member links to their LinkedIn profile so their activity shows up as a badge. HR Briefing counts 26 partners in the menu right now.

## How does Hiring Assistant 2 rank candidates?

It ranks on three kinds of signal: whether the profile can be trusted, whether the person is likely to reply, and whether they look like people you hired before. None of the three measures engineering skill directly.

1. **Trust.** LinkedIn says the agent combines verification status, ATS insights, pre-screening responses, and relevant experience. LinkedIn has 115 million verified members, so a verified profile is real but far from rare.
2. **Receptiveness.** The agent shows indicators of how receptive a candidate might be, based on platform engagement, Open to Work details, and InMail responsiveness.
3. **Memory.** LinkedIn's example: the agent "will now find one close to the office, in the retail industry and with mid-level experience, because those are all the things you've hired for in the past."

The ranking matters because recruiters act on it. LinkedIn says recruiters are 4x more likely to contact candidates sourced by Hiring Assistant than candidates found through traditional methods. Whatever the agent puts at the top gets messaged. Whatever it puts at the bottom mostly doesn't.

## Is the 2.9x figure proof that connected profiles are better engineers?

No. The 2.9x most likely reflects who opts in, not how good they are. People who connect apps tend to be active on LinkedIn, often job-seeking, and quick to answer InMail, and that is exactly what the receptiveness score rewards.

The loop works like this:

- An engineer who is already engaged and looking connects Replit or JetBrains.
- That same engagement raises their receptiveness score.
- The agent ranks them higher for every recruiter whose search they match.
- They get more messages, and the "up to 2.9x" figure grows.

The badge itself doesn't claim skill either. JetBrains says plainly that its badge "represents your practical use of JetBrains tools, not a ranking or certification of skill level." A Connected App shows that someone uses a tool and opted in to show it. Merged pull requests, maintainer roles, and conference talks show what they can actually do.

Opting in is also uncommon. LinkedIn said in June that more than a million members had activated Connected Apps. That's about 0.1% of LinkedIn's 1B+ members, compared with roughly 11.5% who are verified. A ranking boost tied to a 0.1% behavior focuses attention on a very small group.

## Why do competing shortlists converge?

They overlap from two directions. Every company's agent applies the same trust and receptiveness boosts, and each company's memory pushes its searches toward the profiles it has hired before. The result is that thousands of employers end up messaging the same visible, verified, responsive engineers.

Look at the receptiveness signals from the other side. The senior engineer who ignores InMail, never turns on Open to Work, and has no reason to post scores low on responsiveness. Those are often the people most worth a careful, personal message. This is the main limitation of Hiring Assistant as a sourcing tool: it puts them last.

Memory makes the overlap worse over time. If your last three backend hires came from fintech in Austin, the agent leans toward the next fintech engineer in Austin. That's reasonable for one company. Across thousands of companies on the same agent, everyone ends up searching more and more narrowly in the most crowded part of the market.

> An agent that ranks on who replies will always put the engineers worth chasing at the bottom.

> **Senior engineering roles open now** - [see the open roles](https://www.refolk.ai/jobs/search?family=engineering&seniority=senior)
>
> Live senior engineering postings, for a sense of which employers are competing for the same people.

## How much of an engineer's real work does LinkedIn show?

Very little. In Refolk's index of professional profiles, only 5% of US software engineers list GitHub as a skill, and GitHub itself says most day-to-day work happens in private projects that no profile can show anyway.

I counted US profiles with Software Engineer, Senior Software Engineer, or Staff Software Engineer titles in [Refolk](/)'s index. Here is what they say about their public work:

| Segment | Count | Share of base |
|---|---|---|
| US profiles with SWE, Senior SWE or Staff SWE titles | 563,051 | 100% |
| ...listing GitHub as a skill | 28,223 | 5.0% |
| ...with "open source" in the headline | 380 | 0.067% (about 1 in 1,480) |
| GitHub developers in the US (Octoverse 2026) | 38.3M | Different definition |

The first three rows come from Refolk's index. The last row is GitHub's Octoverse 2026 count, which uses a broader definition of "developer," so treat it as a sense of scale rather than a matching denominator. Even so, the gap is clear: the US is GitHub's largest developer community (India is second with 32 million), and almost none of that activity appears in LinkedIn's fields.

> **95%** of US software engineer profiles don't list GitHub as a skill
>
> In Refolk's index, 28,223 of 563,051 US SWE, Senior SWE and Staff SWE profiles name GitHub.

Engineers don't treat LinkedIn as their portfolio. Their portfolio is the commit log, the issue tracker, and the RFC thread. So a filter on GitHub, open source, or a Connected App badge finds people who curate their LinkedIn profile, not the people with the most to show.

## Where are the engineers Hiring Assistant ranks last?

They're in project communities, maintainer files, and commit histories, and they're often listed under the project rather than a company. In Refolk's index, the 380 US engineers with "open source" in their headline include people whose listed employer is OpenTelemetry, "Open Source," Red Hat, or Guardrails AI.

That detail is what breaks title-and-company filtering. A company filter for observability vendors won't return someone whose employer field says "OpenTelemetry." A keyword search for "open source" catches 380 headlines, while 28,223 profiles list GitHub as a skill. That's 74 to 1. Most people who do open-source work don't put it in their headline.

To find engineers who aren't surfacing in LinkedIn Recruiter, look for:

- **Maintainer and CODEOWNERS files** in the projects your team depends on.
- **Merged PRs and review activity** on those repos, not just star counts.
- **Project names in employer fields**, such as OpenTelemetry instead of a vendor.
- **Conference talks and RFC authorship** that link back to a GitHub handle.
- **Commit email domains** that tell you where someone works now, even when their LinkedIn is out of date.

Doing this by hand means moving between GitHub, LinkedIn, and talk archives, and matching handles to names one at a time. That cross-referencing is what Refolk handles for you: you describe the engineer in plain English and get back a ranked list matched across GitHub, LinkedIn, and the open web.

> **Example search:** "Find US-based engineers who have merged PRs or maintainer roles in OpenTelemetry collector repos in the last year, whether or not their LinkedIn mentions it." - [run it on Refolk](https://www.refolk.ai/s/4abp1t6d2g)
>
> You get a ranked shortlist with each person's GitHub handle, recent merged work, and matched LinkedIn profile where one exists.

## How do you source GitHub developers outside LinkedIn?

Start from the code your team actually runs, work backward to the people who maintain it, and only then match them to profiles. Do it in the reverse order and you end up with the same verified pool as everyone else.

1. **List your dependencies.** Pull the 10 to 20 open-source projects your stack relies on most. For an observability team, OpenTelemetry is the obvious first one.
2. **Read the maintainer files.** Note who owns which directories and who reviews other people's PRs. Reviewing is a stronger signal than merging, because a project only hands review to people it already relies on.
3. **Filter by recency.** Keep people who have been active in the last 6 to 12 months. Someone whose last commit was years ago has probably moved on.
4. **Resolve identity.** Match handles to real names, current employers, and locations using commit emails, personal sites, and talk bios. Confirm the person is real by comparing several independent footprints, not one badge.
5. **Only now check LinkedIn.** Treat the profile as a contact channel, not the evidence. Many of these people will be verified with no Connected Apps. Some won't have a usable profile at all.

Steps 1 to 4 are the slow part. Repeating them for every open role is what eventually pushes teams back to whatever the agent puts in front of them.

The engineers you find this way are less likely to show up in your competitors' Hiring Assistant results, because none of the signals that put a profile there come from their work. When you write to them, open with one specific PR, subsystem, or talk, name the problem your team has rather than the job title, and use the channel they actually use. A low receptiveness score usually means someone is tired of messages that could have gone to anyone, not that they're unreachable.

## FAQ

### Does LinkedIn Hiring Assistant 2 cost extra?

Not if you already pay for Hiring Assistant. LinkedIn is rolling out Hiring Assistant 2 from November as a free automatic update for global customers who currently use Hiring Assistant in English. Hiring Assistant itself is still a paid add-on, so teams without it don't get the update.

### Is GitHub a LinkedIn Connected App?

Its status isn't settled. LinkedIn's Hiring Assistant 2 announcement names Chess.com, ElevenLabs, and Medium as partners, with Behance and Replit work also displayable. TechRadar described GitHub as "on the horizon" in June 2026, while ppc.land listed it among about thirty partners. Check the Connected Apps menu inside the product before you build a sourcing process around it.

### Do candidates with Connected Apps make better hires?

There's no evidence that they do. LinkedIn's figure is that members with a connected app receive up to 2.9x more recruiter messages, which measures recruiter attention, not candidate quality. JetBrains says its badge reflects tool usage, not skill certification. Opting in also tends to go with being active and responsive, which the agent already rewards, so the boost largely feeds itself.

---

_From the Refolk blog. More posts: https://www.refolk.ai/blog/index.md_