Embedded recruitment, often called RPO, is when recruitment support works closely inside a company rather than only introducing candidates from the outside. For an architecture practice, it can help when hiring has become too constant, too messy or too dependent on already busy directors.
It is not automatically the right answer. A one-off architect search, a senior hire or a confidential role may be better handled as a focused recruitment project. Embedded support makes more sense when the practice needs process, market feedback and candidate communication as much as CVs.
Watch: what really happens inside architecture recruitment
This Architecture Social video gives useful context on how architecture recruitment works behind the scenes, which helps when deciding whether to keep hiring in-house or bring in embedded support.
When embedded recruitment makes sense
The strongest reason to use embedded recruitment is not that the practice is hiring one person. It is that hiring has become a recurring operational problem.
- Several roles are open at the same time across studios or teams.
- Hiring managers are slow to review CVs because project work always wins.
- Candidate communication is inconsistent, which damages the employer brand.
- The practice needs salary, availability and market feedback while it hires.
- Interviews, feedback and offers need one clear owner.
In that situation, embedded support can bring structure. It can turn hiring from a series of reactive conversations into a managed pipeline with clearer roles, better feedback and fewer dropped candidates.
Go deeper with Architecture Social
These related Architecture Social episodes add more context once you have the practical framework.
Related audio: Architecture Social podcast
This episode is useful because embedded recruitment should still be judged like any other recruitment support: does it save time, improve quality and make the process clearer for candidates and hiring managers?
What embedded recruitment should include
Good embedded recruitment should cover more than sourcing. If all you get is a list of names, that is not really embedded support. It should improve the whole hiring flow.
- Role definition, including salary range, project context and must-have evidence.
- Candidate sourcing and response management.
- Clear screening notes so hiring managers can make faster decisions.
- Interview coordination, feedback chasing and offer support.
- Market intelligence on salaries, candidate objections and competitor activity.
The value is in the loop. The recruiter learns what the practice actually needs, the practice learns what the market is really saying and candidates get a more professional experience.
What embedded recruitment should not become
Embedded support should not become a hidden admin layer where nobody in the practice changes how they hire. If hiring managers are still unclear, interviews still drift and candidates still wait too long for feedback, the model is not doing its job.
- It should not hide weak salary positioning.
- It should not send CVs without explaining why each person fits the brief.
- It should not protect hiring managers from making timely decisions.
- It should not copy generic corporate hiring language into an architecture practice.
How to measure whether it is working
The useful measures are not only how many candidates entered the pipeline. Look at interview quality, time to feedback, offer acceptance, candidate drop-off and whether hiring managers are making better decisions by the end of the process.
Do not outsource your judgement
Embedded recruitment should support hiring judgement, not replace it. A recruiter can structure the brief, challenge unrealistic requirements and manage the market conversation, but the practice still needs to decide what good looks like.
That means being honest about project needs, team gaps, salary limits, office expectations and career progression. Vague briefs lead to vague shortlists.
Embedded support versus a normal search
- Use embedded support when the hiring workload is ongoing or multi-role.
- Use a focused search when one role is specialist, confidential or urgent.
- Use salary benchmarking when the practice is unsure whether the offer is realistic.
- Use employer-brand support when good candidates keep dropping out before interview.
Common mistakes
- Using embedded recruitment without giving the recruiter real access to hiring managers.
- Treating it as cheap admin rather than a strategic hiring layer.
- Hiding salary ranges until late in the process.
- Letting every hiring manager define the same role differently.
- Measuring only CV volume instead of interview quality, speed and offer acceptance.
Architecture Social view
Stephen’s recruiter view is that embedded recruitment works best when the practice is ready to be challenged. If a salary is off, the brief is too broad or the process is too slow, the embedded partner needs permission to say that clearly.
Next step
If you are deciding between embedded recruitment, a focused search or a simpler hiring campaign, start with Architecture Social recruitment for employers, the recruitment consultancy page and the salary survey.
Add a comment