Getting a job in architecture is easier when you treat the search like a focused project. You need a clear CV, a relevant portfolio, a sensible shortlist of practices and a follow-up rhythm that does not feel desperate.
This guide is for candidates who want a practical route into their next architecture role, whether that is a first Part I position, a Part II role, a junior architect job or a move into a new type of practice.
Watch: Architecture Social video
This Architecture Social video adds useful context before the practical guidance below.
Listen: full job-search episode
Prefer audio? This is the podcast version of the same conversation about getting a job in architecture.
You can also open the related Architecture Social podcast page.
Start with the role you actually want
A weak job search starts with anything available. A better one starts with a target: practice type, location, role level, software expectations, project type and salary range.
- Write down the job titles you are realistically suited for.
- Look at live adverts and note repeated skills.
- Compare your CV and portfolio against those requirements.
- Decide what is essential and what is flexible.
- Keep a simple tracker so you know who you have contacted.
Go deeper with Architecture Social
These related Architecture Social episodes add more context once you have the practical framework.
Related audio: architecture job-search habits
This related Architecture Social episode gives another practical angle on using your time well during the job search.
You can also open the related Architecture Social podcast page.
Build a focused application list
Do not apply to every practice in London with the same message. A smaller list of relevant practices usually works better than a huge list of lazy applications.
For each target, check the type of work they do, the software they mention, the level they hire at and whether your experience makes sense for them. Then adapt your CV, portfolio sample and email accordingly.
Make the CV and portfolio work together
The CV should make the reader understand your experience quickly. The portfolio should prove it visually. If they tell two different stories, the application feels confused.
- Put the most relevant experience near the top.
- Use clear role titles and dates.
- Show project scale, stage and responsibility.
- Keep the portfolio sample tight and easy to open.
- Explain your contribution on team projects honestly.
Follow up properly
Following up is useful when it is polite, specific and timed well. It is not useful when it becomes a daily chase or asks the practice to do the thinking for you.
Common mistakes
- Sending a huge portfolio before anyone asks for it.
- Applying for roles that do not match your level.
- Hiding software gaps instead of addressing them honestly.
- Using a generic cover email for every practice.
- Only searching when you are already under pressure.
Architecture Social view
Stephen’s recruiter view is that a good candidate makes the decision easier for the practice. Clear evidence, sensible targeting and good communication beat vague enthusiasm every time.
Next step
Start with live architecture jobs, then tighten your architecture CV, prepare your portfolio and use the interview guide before you apply at scale.
Add a comment