Hiring Architecture Talent for Technical and Team Fit

Define what the role actually needs

Before judging candidates, define the problem the hire needs to solve. A Part II assistant, project architect, senior architect and BIM coordinator may all need Revit, but the real responsibilities are very different.

• Project stage: concept, planning, technical design, delivery or site.
• Responsibility: support, package ownership, client contact or team leadership.
• Sector: residential, workplace, commercial, education, healthcare or specialist.
• Communication: consultants, clients, contractors, juniors or internal teams.
• Pace and structure: busy studio, careful technical team, startup culture or mature practice.

Go deeper with Architecture Social

These related Architecture Social episodes add more context once you have the practical framework.

Turn fit into evidence

Fit should not mean hiring the person who feels most familiar. It should mean checking whether the candidate can work well in the reality of the role.

• Ask how they handle unclear feedback.
• Ask where they have taken ownership and where they needed support.
• Ask how they communicate technical risk or design changes.
• Ask what type of management helps them do their best work.
• Ask what they learned from a project that did not go smoothly.

These questions make fit more concrete. You are testing behaviour, judgement and self-awareness, not whether someone says the right buzzwords.

Use a simple hiring scorecard

A scorecard does not need to be corporate. It simply keeps the interview team honest by making everyone judge the same role.

• Technical evidence: drawings, Revit, detailing, coordination or delivery.
• Project relevance: sector, scale, stage and responsibility.
• Communication: how clearly they explain risk, feedback and decisions.
• Team fit: what environment helps them do good work.
• Motivation: why this move makes sense now.

This also helps reduce bias. If one interviewer is impressed by confidence and another cares about delivery detail, the scorecard brings the conversation back to the role.

Read the portfolio properly

A portfolio can show fit if you look beyond the images. The useful evidence is in project stage, personal contribution, constraints, decision-making and how clearly the candidate explains their role.

• Do they label individual, team and practice work honestly?
• Can they explain why a design or technical decision was made?
• Do they show process where it helps the reader understand judgement?
• Can they connect their work to the role you are hiring for?
• Is the presentation clear enough for a busy project team to read quickly?

Avoid the false choice

You do not have to choose between someone technically strong and someone good for the team. The best hiring process tests both. A technically strong candidate who cannot communicate risk may struggle. A culturally warm candidate without enough evidence may still be the wrong hire.

Common mistakes

• Using culture fit as a vague shortcut.
• Hiring for software but ignoring project responsibility.
• Overvaluing confidence in interviews.
• Not checking how the candidate handled pressure or feedback.
• Letting every interviewer judge a different version of the role.

Architecture Social view

Stephen's recruiter view is that the best hiring conversations are specific. When a practice can explain the role clearly, candidates can answer with better evidence and the shortlist improves quickly.