Hiring Disabled Employees in Architecture

Hiring disabled employees in architecture should not be treated as charity, risk or a compliance chore. Done properly, it can widen the talent pool, improve problem-solving and help practices build teams that understand more of the people they design for.

In this Architecture Social conversation, Jane Hatton of Evenbreak explains why the first step is not asking disabled candidates to fit a broken process. It is looking at the barriers inside the process itself.

Watch: Jane Hatton on inclusive hiring

Jane Hatton brings useful employer-side context to disability and recruitment, with practical points that architecture practices can apply immediately.

Listen: disability and better recruitment practice

The audio version gives more space to the recruitment barriers, flexible working lessons and assumptions that can exclude strong disabled candidates.

You can also open the related Architecture Social podcast page.

Start by questioning the assumptions

A lot of disability is not visible. That matters in architecture, because employers can make quick assumptions about site work, office work, deadlines, communication, software use or client-facing responsibility without checking what a person can actually do with the right support.

The better approach is to define the work clearly, then ask what adjustments would make the process fair. That is different from lowering standards. It is about testing the right things.

Where recruitment often goes wrong

• Job adverts list every possible duty instead of the real essentials.
• Interview formats reward confidence under pressure more than evidence of ability.
• Hybrid or flexible working is treated as a favour rather than a practical design of work.
• Reasonable adjustments are offered too late, or only when someone is comfortable enough to ask.
• Disabled students and early-career candidates are judged against a narrow idea of how a career should look.

Why this matters for architecture practices

Architecture already needs people who can notice constraints, solve problems, think spatially, communicate clearly and work around imperfect systems. Many disabled people build those skills through lived experience long before they enter practice.

That does not mean every disabled candidate is automatically right for every role. It means the hiring process should be good enough to see the evidence properly.

What practices can review this week

• Separate essential requirements from nice-to-have preferences.
• Tell candidates what the interview format will involve.
• Offer adjustments clearly, without making people justify themselves repeatedly.
• Review whether office, hybrid and site expectations are genuinely tied to the role.
• Train interviewers to assess evidence, not just confidence.

For more disability-focused employment insight, explore Evenbreak. If you are shaping an architecture role now, Architecture Social can also help with employer recruitment support.

Architecture Social view

Stephen’s recruiter view is that better hiring usually starts with better role definition. If a practice cannot explain what success looks like, it is much harder to assess any candidate fairly.

Next step

Pick one live or upcoming vacancy and rewrite the requirements into essentials, useful extras and support available. That small exercise can expose where the process is helping or blocking good people.