Context determines performance
Andy Grove, whose book High Output Management Keith Rabois frequently references, introduced the concept of task-relevant maturity: the idea that how much autonomy you give someone should depend not on their general seniority, but on whether they've done this specific task in this specific context before. An engineer with fifteen years of experience who has never worked in a distributed team is, in that dimension, a beginner. A developer with seven years who has spent most of them in remote-first setups may be far more mature for that particular role.
This is why most staffing fails. Not because the wrong technical skills were matched. But because nobody evaluated whether the candidate's experience was relevant to the specific context they were walking into.
A company defines a role, writes a job description with a list of required technologies, and hands it to a staffing partner who searches for CVs that match. The partner sends candidates. The company interviews them. Someone gets hired. Sometimes it works. Often it doesn't — because the staffing partner didn't understand how the team operates, what the real challenges are, where the organisation is headed, or what kind of person would actually thrive in that specific environment.
A technically brilliant developer who is misaligned with your pace, communication style, or working culture won't stay. Or worse, they'll stay and create friction. As we discussed in the barrels article, a barrel at one company may not be a barrel at another. The same principle applies to every senior hire. Performance is not purely individual — it's a function of the match between the person and the environment.
Understanding before staffing
Effective staffing starts with understanding the client's organisation at a level that goes far beyond a job description.
It means understanding how the company operates — team structure, roles, communication patterns, and the small friction points that determine whether a new hire integrates smoothly or struggles. It means understanding how the company is scaling — hiring pace, leadership structure, coordination overhead — because staffing for where a company is today without understanding where it's headed is a recipe for short-term matches that don't last. And it means understanding how the company builds — the tech stack, architecture, and delivery practices that determine what kind of developer will contribute from day one versus someone who merely ticks a checkbox on paper.
This kind of understanding doesn't come from reading a job spec. It comes from advisory — real conversations about operations, growth, and technology before anyone starts looking at candidates. When that understanding is in place, you can move quickly without compromising on quality. Speed and depth aren't opposites — they're sequential. Do the understanding work upfront, and the matching becomes faster and more accurate.
The two-way match
Throughout this series, we've argued that talent density compounds, that hiring fewer, better people creates more throughput than hiring more average people, and that the environment a developer works in determines whether they reach their potential.
All of these principles point to the same conclusion: staffing has to be a two-way match. The candidate needs to be right for the company, but the company also needs to be right for the candidate. Capability without alignment reduces the total output of a team. The two-way match is how you ensure both magnitude and direction are right — for the company and for the candidate.
A senior developer who has spent years working in high-performing environments won't stay in a setup that doesn't challenge them or respect their way of working. And someone who commits to a role without genuine excitement about the work will never produce at the same level as someone who is fully bought in. Retention isn't solved by contracts. It's solved by fit.
This is why it's impossible to do great staffing without first understanding the client at a deep level. You can't evaluate fit if you don't know what the environment actually looks like from the inside. And you can't attract the best talent if you can't honestly describe what they're walking into.
The principle behind it all
The best developers are made by working alongside other great developers. Every hiring decision either strengthens or weakens that dynamic. Choosing technology that gives you access to the deepest talent pools. Sourcing from markets where senior developers have been shaped by decades of high-quality work. Understanding the client well enough to match not just skills, but pace, ambition, and working style. And having the discipline to leave a seat empty rather than fill it with the wrong person.
That's why staffing — real staffing — starts long before the first CV.
