A job opening goes live. A first interview gets scheduled. Simple enough from the outside.
But between those two moments, there is a process that most people on either side of it have never fully seen. Clients hand over a brief and wait for profiles. Consultants get a message and wonder how they ended up on a shortlist. What happens in between is rarely explained.
This is what actually happens.
It starts with the brief, and it’s never complete
When a client sends a job description, it’s a starting point, not a finished picture. The role title, the stack, the seniority level. Useful, but not enough to find the right person.
The first thing the recruitment team does is go back to the client or hiring manager. Not to challenge the brief, but to fill in what a written document cannot carry. What is the team dynamic like? Is this a greenfield project or a legacy codebase that needs patience? Is the client looking for someone to lead technically, or someone who executes well within an existing structure?
Those details change everything. A senior engineer who thrives in ambiguity is a different profile from a senior engineer who delivers best with clear scope. On paper, both fit the job description. In practice, only one of them fits the team.
The conversation behind the brief is where recruitment actually begins.
Then comes the search, and it is not a database query
Once the brief is sharp enough to act on, the search starts. And this is where the difference between a team extension partner and a CV-forwarding service becomes visible.
A database query returns everyone who matches a set of keywords. That is a list, not a shortlist. Turning it into a shortlist requires reading between the lines of a profile, understanding what a person’s career trajectory says about how they work, not just what they have worked on.
A consultant who has moved between three long-term embedded projects tells a different story from one who has cycled through short contracts. A profile that shows progression within the same tech domain tells a different story from one that shows breadth without depth. Neither is better by default. What matters is which story fits the client’s situation.
That reading takes time. It also takes familiarity with the market, knowing who is genuinely available, who is passively open, and who is happy where they are but worth a conversation anyway.
What consultants experience on the other side
From a consultant’s perspective, the process can feel opaque. A message arrives. There is a project, a stack, a vague description of the partner behind it. It is easy to wonder how seriously the recruiter has thought about the fit, or whether this is just volume outreach.
At We Are META, the approach is different. When a consultant is approached for a specific role, it is because someone has read their profile carefully enough to believe the fit is real. The message names why. The project detail is specific. The ask is small, a 30-minute conversation, not a CV submission into the unknown.
That specificity is not a courtesy. It is how good recruitment works. A consultant who understands why they are being considered for a project is better placed to assess whether it’s right for them. That conversation is more useful for everyone than a generic pitch followed by a generic reply.
The shortlist is a recommendation, not a selection
When profiles land in a client’s inbox, they represent a recommendation. Not a list of everyone who matched the keywords, but the people the recruitment team believes are genuinely worth the client’s time.
That distinction matters because it changes how the client should approach the conversation. The question is not just “does this person have the right skills?” It is “does what I know about this person’s way of working fit what my team needs right now?”
The recruitment team has already filtered for skills. The client’s job in the interview is to filter for fit, and to trust that the profiles in front of them have been put there for a reason.
At We Are META, the goal is to have profiles in a client’s inbox within 48 hours of a confirmed brief. That’s possible because the groundwork happens before the brief is even confirmed, in the market knowledge, the existing relationships with consultants and the conversations that sharpen the brief before the search begins. For more niche or specialised roles, where the available pipeline is naturally smaller, that timeline can shift, but the groundwork behind it doesn’t change.
Why both sides benefit from understanding this
Clients who understand what goes into a shortlist engage with it differently. They ask better questions in interviews. They give more useful feedback when a profile is not quite right. And they trust the process enough to move quickly when the right person appears.
Consultants who understand how they are selected show up to conversations better prepared. They know the fit has been thought about. They can focus on whether the project is right for them, rather than trying to figure out whether the recruiter has done their homework.
The process works best when both sides can see it clearly. That is what this article is for.
Find out how We Are META’s team extension model works in practice: Team Extension at We Are META
