An architect moving into development is not abandoning design. Done well, it can mean applying design judgement earlier, across money, land, planning, community, delivery and long-term impact.
Russ Edwards’ route from practice into development is useful because it shows the shift clearly: the work becomes less about owning every design move and more about shaping the conditions that make good projects possible.
Watch: Architecture Social video
This Architecture Social video adds useful context before the practical guidance below.
Listen: full architect turned developer 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 development can suit architects
Architects often understand how project decisions affect people, place and delivery. In development, that understanding can be valuable if it is paired with commercial awareness and practical decision-making.
- You can influence briefs earlier.
- You can connect design quality with viability and long-term value.
- You work across land, planning, consultants and stakeholders.
- You learn how funding and delivery shape what gets built.
- You can bring a design-led voice into commercial conversations.
Go deeper with Architecture Social
These related Architecture Social episodes add more context once you have the practical framework.
Related video: moving client-side
The original Russ Edwards episode stays near the top. This related Architecture Social video adds a practical route into client-side and developer roles.
Related audio: moving client-side
This related episode expands the practical side of moving from architecture practice into developer or client-side roles.
You can also open the related Architecture Social podcast page.
What changes when you move into development
The language changes. You may talk more about risk, programme, funding, stakeholders, social value, procurement and delivery. That does not remove design, but it changes where design sits in the conversation.
You also need to be comfortable influencing through others. Developers often manage architects, consultants and contractors rather than drawing every answer themselves.
Skills that transfer well
- Understanding how projects move from idea to delivery.
- Reading drawings and spotting risk early.
- Explaining design decisions to non-design audiences.
- Balancing quality, cost, programme and stakeholder pressure.
- Holding a long-term view of place, users and impact.
How to position yourself
A developer-side CV should not look like a normal practice CV with a different job title at the top. Show the commercial and delivery relevance of your work: project scale, role, stage, coordination and outcomes.
Common mistakes
- Assuming design talent alone is enough.
- Not explaining commercial awareness.
- Using architecture language without development context.
- Underplaying coordination, stakeholder and planning experience.
- Applying for developer roles without understanding the role’s risk profile.
Architecture Social view
Stephen’s recruiter view is that the best architect-to-developer moves are not escape routes. They are deliberate career moves where the candidate can show why their design background improves wider project decisions.
Next step
Look at your last three projects and write down the commercial, stakeholder and delivery evidence, not just the design outcome. Then compare that against the client-side career move guide, live architecture jobs and the salary guides.
If you want new roles sent to you, set up architecture job alerts.
Add a comment