How Architects Move Client-Side

Moving client-side can make sense if you want to sit closer to commercial decisions, land, funding, delivery and the bigger project picture. It is not simply a better-paid version of practice.

The move usually works when you can translate architecture experience into risk, programme, stakeholder management, viability, consultant coordination and decision-making.

Watch: Architecture Social video

This Architecture Social video adds useful context before the practical guidance below.

Listen: full client-side career move episode

Prefer audio? This podcast version adds the full Architecture Social conversation for anyone who wants to go deeper.

You can also open the related Architecture Social podcast page.

Why the move appeals

Architects often look at developers, real estate teams and main contractors because they want broader influence. Instead of only responding to a brief, they want to understand how the brief is made, funded, tested and delivered.

• Closer exposure to commercial decisions.
• More involvement in land, feasibility and programme.
• A wider view of consultants, contractors and stakeholders.
• Potentially different salary structures and progression routes.
• A chance to use design judgement in a broader business context.

Go deeper with Architecture Social

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

Related video: in-house design leadership

The original client-side episode stays near the top. This related Architecture Social conversation adds another view from an in-house design leadership role.

Related audio: client-side insight

This related episode adds a practical example of how architecture experience can transfer into a developer-side environment.

You can also open the related Architecture Social podcast page.

What client-side employers look for

Client-side employers are rarely hiring someone just because they can design. They want evidence that you can manage information, understand project risk, communicate with different parties and make practical decisions.

Your CV should explain project scale, stage, responsibility, coordination and commercial awareness. Your portfolio can still help, but it needs to support the story rather than behave like a pure design application.

How to frame your CV

• Show project value, scale, sector and stage where you can.
• Explain consultant, client, contractor or stakeholder exposure.
• Name planning, feasibility, delivery or technical experience clearly.
• Use plain language around programme, risk and coordination.
• Avoid making the application look like a standard practice move.

Interview questions to prepare for

Expect questions about why you want the move, what you understand about the client-side role and where your experience is genuinely transferable. If the answer is only money or frustration with practice, it will sound thin.

Common mistakes

• Sending a design-heavy portfolio with no commercial context.
• Using practice language without explaining the client-side relevance.
• Applying too broadly across every developer or contractor role.
• Underplaying stakeholder and coordination experience.
• Not understanding what the role actually does day to day.

Architecture Social view

Stephen’s recruiter view is that client-side moves are strongest when the candidate can prove judgement, not just ambition. The practice background is useful, but only if it is translated properly.

Next step

Rewrite your CV profile for a client-side reader, then compare it with live architecture and design jobs, the Architecture CV guide and the David Drews client-side episode.