Greenhouse's Sourcing Beta Mines Applicants, Not Passive Engineers

If you hire on Greenhouse, its new closed-beta sourcing tool looks like a reason to cut back on outbound. For the senior engineers most teams struggle to find, it isn't, and the reason comes down to where the profiles come from.

The tool is part of Greenhouse's new Orchestrated Hiring Ecosystem, and it searches the "millions" of job seekers who have built MyGreenhouse profiles. Who those job seekers are decides what the tool can do for you.

What did Greenhouse launch with the Orchestrated Hiring Ecosystem?

Greenhouse launched the Orchestrated Hiring Ecosystem, a bundle that puts sourcing, interviewing, scheduling and the applicant tracking system in one place, alongside the job seekers who have built MyGreenhouse profiles. The new piece is sourcing, and only select customers get it, in closed beta.

MyGreenhouse is Greenhouse's account for job seekers. It launched in April 2025. The launch packages four features around that profile base:

• Sourcing beta: search MyGreenhouse profiles from inside Greenhouse. In Greenhouse's words, it "surfaces job seekers who are actively looking and fit the role."
• Dream Job: a job seeker can flag one application per month as their top choice.
• Real Talent: already live. It launched in June 2025.
• Voice AI Interviewing: also already live. Customers have had it since May 2026.

So most of the launch is repackaged. Greenhouse pitched it as a way to break "AI's hiring doom loop," and its own research shows why that pitch works. Four in five job seekers use AI in their search, 86% of U.S. recruiters say at least half of the applications they get are AI-written, and fewer than 7% of applicants ever get an interview. The release names Anthropic, HubSpot and the NFL as customers.

Who is actually in the MyGreenhouse pool?

The pool is people who applied to a Greenhouse customer, chose to create an account, and left recommendations turned on. Searching it is closer to digging through past applicants across thousands of companies than to finding new people.

Each of those three steps narrows the pool:

1. They applied somewhere on Greenhouse. A MyGreenhouse profile exists because someone applied to a Greenhouse customer.
2. They opted in. Greenhouse's setup docs say account creation is optional for applicants, and the employer decides whether to turn the features on at all.
3. They stayed discoverable. Greenhouse tells job seekers to "keep recommendations turned on" if they want to be recommended to hiring teams with matching roles, "sometimes before the role is posted."

The pool has grown quickly. By October 2025, more than 1.5 million job seekers and 6,500 companies had joined MyGreenhouse since its April 2025 launch, and NPR, Everlane, Flexport, Guild and Huntress were among the early employers. Greenhouse says about 110,000 MyGreenhouse job seekers have been hired, and more than 5,000 companies hire through it.

None of this is a flaw. A shared, cross-company list of silver medalists (strong candidates who lost out to someone else) is genuinely useful. But the limit is built in: if an engineer never applied anywhere on Greenhouse, they can't be in the pool.

Why are senior and staff engineers missing from it?

Senior engineers rarely apply cold, so a pool made of applications will have few of them. In Refolk's index of professional profiles, only 68 of the 244,834 US engineers with Senior, Staff or Principal Software Engineer titles put "open to work" in their headline. That's about 1 in 3,600.

1 in 3,600

The more senior you go, the worse it gets:

There are two caveats. The headline match only catches public text, not the private open-to-work setting, and a few matches were noisy (one was a data analyst). The last row comes from 25 sampled profiles, so it shows a direction, not a precise figure. Of those 25, 19 were Senior Software Engineers, 1 was a Principal, and none were Staff.

Still, the direction is clear. Staff and Principal engineers make up a quarter of US senior engineering profiles but almost none of the people who say publicly that they're looking. Two reasons:

• They get approached. Staff engineers at Databricks, Google or Datadog, which are among the top employers in this segment of Refolk's index, hear from people directly. They rarely need to apply anywhere.
• They move through referrals. When they do change jobs, it usually starts with a conversation, not a form.

LinkedIn's Talent Trends survey of 18,000 professionals in 26 countries found that 75% call themselves passive candidates. Among senior engineers that share is probably higher, and by design the sourcing beta can't reach those people.

What does "millions of profiles" actually tell you?

"Millions of profiles" tells you very little about any single req. Greenhouse hasn't said how many profiles belong to people actively looking, how many agreed to be considered for new roles, how many match an open job, or how many a beta customer can actually contact.

Some rough math helps. The last published figure, 1.5 million MyGreenhouse users as of late 2025, covers every job family in every country. That's only about 6x the 244,834 US senior-plus engineers in Refolk's index. Now remove sales, operations, support and everyone outside your hiring geography, then apply the recommendations opt-in. The set you could actually match to one senior backend role in one metro is probably small.

"Probably" matters here, because Greenhouse hasn't published the numbers. Before you shift budget, ask your Greenhouse rep:

• How many profiles have recommendations turned on today?
• How many of those match my open job families and locations?
• How many can I message from inside the beta?
• What share of them have Staff-level or above titles?

If they can't answer, assume the passive senior engineers are still out there on GitHub and the open web, not in the beta.

That's the work Refolk is built for. You describe the engineer you need in plain English, and I search GitHub, professional profiles and the open web to return the people who fit, whether or not they've ever filled out an application.

How should you read the MyGreenhouse Dream Job signal?

Dream Job is a strong intent signal that arrives late. Because a candidate gets one flag per month, the flag means something, but it only shows up on an application, so it ranks people already in your funnel and can't bring in anyone new.

The scarcity is real. At the June 2025 launch, more than 1,200 Greenhouse customers had turned on Dream Job applications and received over 10,000 submissions. That works out to roughly 8 per company. Greenhouse CEO Daniel Chait describes it as a way to "zero in on high-intent, high-likelihood candidates," and for the roles it covers, that's a fair description.

Look at Greenhouse's own showcase story, though. Martin Nguyen, a Dream Job user, was hired at Ping Identity after getting a reply the next day and an offer within a week. It's a great result, and it's also an active applicant doing what active applicants do. Dream Job made him easier to spot among other applicants. It didn't find someone who wasn't looking.

Dream Job tells you who wants your job most. It can't tell you about the engineer who never applied.

Use the flag as a priority lane. A Dream Job applicant should get a human reply within a day and go straight to a hiring manager call where you can. Just don't expect it to fill your Staff platform search.

Greenhouse sourcing beta vs outbound: which finds passive candidates?

Outbound finds passive candidates. The Greenhouse beta isn't designed to: it shows you active seekers with stated intent, while GitHub and the open web show you evidence of real work from people who aren't applying anywhere.

Passive candidate sourcing means finding and approaching people who aren't currently applying for jobs. Here's how each channel fits:

The 68 people in Refolk's index who announce they're looking are easy to find on any channel. The other 244,766 are the ones you need to reach, and they show up in work evidence, not in applicant pools.

How do you run the beta and outbound together?

Point the Greenhouse sourcing beta at high-volume roles, where filtering for real intent saves time, and keep outbound sourcing for scarce senior roles. Splitting by req keeps the beta from quietly eating your outbound budget.

1. Sort reqs by how scarce the candidates are. Mid-level, support, sales and other high-volume roles go to the beta first. Staff and Principal engineering roles start with outbound.
2. Filter for intent where AI-written applications are piling up. When 86% of recruiters say at least half their applications are AI-written, verified identity and real intent signals are worth having on roles that attract hundreds of applicants.
3. Give Dream Job flags a one-day reply standard. The flag is rare, so treat it that way.
4. Build senior lists from work evidence. For the roles applicant pools can't fill, start from what people have built. Refolk turns a plain-English description of that person into a shortlist drawn from GitHub, professional profiles and the open web, so outbound doesn't take a week of Boolean searches.
5. Get opt-in numbers before moving budget. Until Greenhouse publishes how many profiles are contactable by role and location, plan as if the senior engineering pool is small.
6. Re-test when the beta opens up. If Greenhouse publishes Staff-level coverage, check your mix again. Until then, the fewer-than-7% interview rate it reports is a reminder that applicant pools are already crowded.

FAQ

Can the Greenhouse sourcing beta replace outbound sourcing?

Not for senior or passive roles. The beta searches MyGreenhouse profiles, and those only exist because someone applied to a Greenhouse customer, created an account and left recommendations on. Greenhouse says the tool surfaces people "actively looking." In Refolk's index, only 68 of 244,834 US senior-plus engineers say in their headline that they're looking, so most of the people you need are outside any applicant-built pool.

What is MyGreenhouse Dream Job?

Dream Job lets a job seeker flag one application per month as their top choice, which the employer sees as a high-intent signal. It launched in June 2025, when more than 1,200 customers had turned it on and over 10,000 submissions had come in. It's useful for prioritizing applicants, but it only appears on candidates who already applied.

How many profiles are in MyGreenhouse?

Greenhouse's last specific figure was more than 1.5 million job seekers and 6,500 companies as of October 2025. The Orchestrated Hiring Ecosystem release says "millions." Greenhouse hasn't said how many profiles are open to outreach, match open roles, or can be contacted by beta customers, and those are the numbers that tell you whether it's worth your time.

Who can use the Greenhouse sourcing beta?

Sourcing is in closed beta and only available to select Greenhouse customers, as part of the Greenhouse Orchestrated Hiring Ecosystem. Other pieces of the launch are already live: Real Talent since June 2025 and Voice AI Interviewing since May 2026.