A client brief arrives, and most of us do the same thing with it. We pull out the job title, the seniority band, and the list of must-have skills, then we turn that into a search string and start sourcing. It feels like progress. It is also how a shortlist ends up full of people who match the words on the brief and none of the reality behind it. The brief describes a title. The role is a problem. The gap between those two is where good candidates get missed and weak ones slip through.
This is a framework for closing that gap. It turns a client brief into a shortlist by matching on trajectory fit, the career triggers that prove someone has already solved the problem you are hiring for, rather than on titles and keywords. It is six repeatable steps, and it ends with a worksheet you can copy straight out of this page and reuse for every brief.
The trajectory-matching framework is a repeatable process for turning a client brief into a candidate shortlist by first extracting the single hardest problem the role exists to solve, translating that problem into three to five concrete career triggers, and then sourcing, reading, and interviewing against those triggers. It matches candidates on the journey they have already completed rather than on the titles or keywords on their profile.
Step 1: Extract the single hardest problem, phrased as a problem
Read the brief and ignore the title for a moment. Ask the hiring manager one question: what is the single hardest thing this person has to accomplish in their first year, and what happens to the business if they fail at it. The answer is your anchor. "Take us from ten to forty enterprise logos without the founder in every deal" is a problem. "VP of Sales" is a title. You match against the problem.
Most briefs bury the hardest problem under a list of responsibilities that are all roughly equal in weight. They are not equal. One of them is the reason the role exists, and the rest are context. Your job in step one is to find that one and write it down in a single sentence a candidate could actually recognize from their own experience.
Step 2: Translate the problem into three to five career triggers
Now turn the problem into markers you can look for in a career history. A career trigger is a specific, evidence-backed thing a person would carry if they had already solved your problem. If the problem is scaling enterprise revenue past founder-led selling, the triggers might be: owned the first repeatable sales motion at a company under a hundred people, hired and ramped a first sales team, and personally closed deals in the same buyer segment. This is the discipline behind trigger-based matching, and it is the step that decides whether the rest of the framework works.
Keep it to three to five. Fewer than three and your screen is too loose to filter anything. More than five and you have written a wish list that describes nobody. Three to five forces you to name what genuinely matters and leave the nice-to-haves off.
Step 3: Build the screen from the triggers, not the title
With the triggers written down, build your sourcing screen from them directly. Instead of a Boolean string full of title synonyms, you are looking for career shapes: the stage a company was at when the candidate joined and left, the size of the team they built, the sequence of moves that shows they drove a transition rather than inherited one. The the Seed-to-Series-A sourcing guide walks through exactly how to translate a stage-transition trigger into a set of profiles worth reading, using a real example end to end.
The screen will feel less precise than a keyword search at first, because triggers do not live in a single field. That is the point. A keyword search is precise about the wrong thing. A trigger screen is fuzzy about the right one.
Step 4: Read profiles for the triggers, not the buzzwords
When you open a profile, read it for evidence of your triggers and nothing else. The signal is almost always in the dates, the company stage at the time, and the order of the moves, none of which a summary line or a skills tag will hand you. A candidate who joined a fifteen-person company and left it at two hundred carries a trajectory signal that no title on the profile spells out. A candidate who joined a household name at ten thousand people probably joined a machine that already worked, however senior the title reads.
Score each profile against your three to five triggers as present, partial, or absent. You are not ranking people yet. You are deciding who has enough trigger evidence to be worth an interview, and who does not.
Step 5: Use the interview to confirm what the candidate personally owned
A profile can only get you to a plausible match. The interview is where you confirm it, and the single most important thing you are confirming is the line between what the candidate personally owned and what the team around them did. "We scaled from ten to forty logos" is a sentence a whole go-to-market team could say. Your job is to find out which part of that this specific person drove, decided, and would do again.
This is where the interview record matters. What a candidate actually owned comes out in specifics, in the decision they made when the plan broke in month two, and those specifics are easy to lose to memory by the time you write the debrief. Capturing the interview as structured evidence keeps the trajectory claims attached to the exact words the candidate used, so your shortlist rests on what was said rather than on what you half-remember. This is what a purpose-built interview intelligence tool is for.
Step 6: Assemble the shortlist with the evidence attached
The last step is to build the shortlist so that every name carries its evidence. For each candidate, list the three to five triggers and, next to each, the specific thing from their history and their interview that satisfies it. A shortlist that reads "strong candidate, great culture add" tells the client nothing. A shortlist that reads "trigger two satisfied: personally hired and ramped the first four sales reps at a Series A company in the same segment, confirmed in interview at 14:20" gives the client a decision they can actually make and defend. For a full worked example of a shortlist assembled this way, see a worked case study.
The Trajectory Match Worksheet
Here is the worksheet, laid out inline so you can copy it. There is no download and no form. Paste these fields into a document, fill one in per brief, and reuse it. Honesty about the tool matters: the "template" is exactly this list of fields, written out below.
- The hardest problem. One sentence, phrased as a problem, not a title. What must this hire accomplish in year one, and what breaks if they fail?
- Triggers (3 to 5). The concrete career markers a person would carry if they had already solved the problem. One line each, checkable against a profile.
- Screen. The career shapes and stage signals you will source for, derived from the triggers. Company stage at join and exit, team built, sequence of moves.
- Profile read. For each candidate, mark every trigger present, partial, or absent, with the evidence from their history. Dates, stage, order of moves, not the summary line.
- Interview confirmation. For each trigger, what the candidate personally owned versus what the team did, in their own words. Cite the moment in the interview record.
- Shortlist entry. Name, plus each trigger and the specific history-and-interview evidence that satisfies it. No adjectives, only evidence.
Where Numi fits, and where it does not
Numi is an EU-hosted interview intelligence tool. It records, transcribes, and structures your interviews on European infrastructure so that the trajectory evidence, the specific triggers a candidate confirmed and the decisions they said they owned, is captured as a comparable record instead of fading into a debrief three days later. That is steps four and five made easier.
It does not do the rest for you, and that is deliberate. Numi does not score candidates, rank them, auto-match them to a brief, or build the shortlist. Trajectory matching is a judgment a recruiter makes on the evidence, and it should stay that way. The framework is yours to run, and the worksheet above is how you run it. If you want to see how this fits into a wider recruiting workflow, our page for recruiting teams lays out where structured interview evidence changes the way a shortlist gets built.