How Advant thinks about matching

Matching is not a vibe. It is a system with three parts: what you retrieve, how you rank it, and who is allowed to override the rank.

Retrieval

You cannot rank what you did not find. The first job is a wide-enough, clean-enough set of people who might fit: stack, seniority, location, the kind of problems they have actually shipped.

Today that is our network plus careful search. Later it is embeddings over work, not just profiles. Same job either way: do not miss the person who never put “distributed systems” in a headline but spent four years on the thing you are hiring for.

Ranking

A staff engineer at a 10-person company and a staff engineer at a 10,000-person company are not the same candidate. Titles lie. Tenure lies. Keyword overlap lies with great confidence.

We rank on evidence of the work: repos, writing, systems, the shape of problems they have finished. The model (when we have it) proposes. A human who can read the work decides what gets an intro.

The human override

If matching is the product, the failure mode is pretending the model is the product. Models do not take references. They do not notice a 12-round loop. They do not know that this hiring manager will grind a strong mid-level into dust.

The override is not a courtesy. It is the job.

What you get

A short list. Three to five people, each with a reason that is more specific than “they look senior.” If we cannot explain the fit in a paragraph, we should not send the intro.

That is the bar. Everything else — calendars, ATS fields, email sequences — is plumbing.