An architecture portfolio review should test one thing first: does this document make your ability easier to understand? If the answer is no, the portfolio needs editing, not more decoration.
The strongest portfolios are selective. They show the right projects for the role, explain your contribution and help the practice see how you think.
Watch: making an impact with your architecture portfolio
This Architecture Social episode fits directly because it focuses on how to make a portfolio clearer, more relevant and easier to remember.
Review the portfolio against the role
Before changing layouts, read the job advert. A design-led role, technical role, interiors role, Part I position and senior architect role all need different evidence.
- Design roles need concept clarity, process and strong final outcomes.
- Technical roles need drawings, details, coordination and delivery evidence.
- Interior roles need materiality, atmosphere, plans, sections and client awareness.
- BIM roles need workflow, model evidence and coordination judgement.
- Assistant roles need potential, clarity and honest explanation of responsibility.
Make project choice more ruthless
A weaker project can dilute a strong portfolio. Keep projects that prove something useful. Remove pages that only exist because you spent a long time making them.
If two projects show the same skill, keep the stronger one or give each a different purpose. Repetition makes the document feel longer without making it more persuasive.
Use captions to remove guesswork
Captions should answer simple questions: what is this, what was the brief, what did you do, which stage is it from, and why should the reader care? Short, specific captions often beat long design statements.
Check file size and readability
A portfolio should open quickly and read well on screen. Compress it properly, check drawings at laptop size and avoid tiny text that only works in print.
Keep, cut or move
A useful portfolio review is often a sorting exercise. Keep pages that prove the role fit. Cut pages that are weak, repetitive or only there for decoration. Move strong evidence earlier if it currently appears too late.
- Keep work that proves relevant skill or judgement.
- Cut pages that need too much explanation to make sense.
- Move the most role-relevant project closer to the front.
- Split dense pages if the drawings or text become unreadable.
- Save extra material for the interview version if it has value later.
Prepare an interview version
Your application sample should be tight, but your interview version can go deeper. Keep backup pages ready for process, technical work, models, sketches and drawings that help answer questions in conversation.
Listen: related Architecture Social podcast
The podcast version goes deeper into portfolio structure, review habits and the way practices judge visual evidence during hiring.
You can also open the related Architecture Social podcast page.
Common mistakes
- Starting with a weak or overly abstract project.
- Using too many pages before the first strong piece of evidence.
- Forgetting to explain personal contribution on team work.
- Letting graphic style overpower the project content.
- Sending one portfolio version to every practice without adjustment.
Architecture Social view
Stephen’s recruiter view is that portfolio reviews should be practical. The question is not whether every page is beautiful. The question is whether the right person can understand your value quickly.
Next step
Use this alongside the architecture portfolio guide, check the evidence requested in live architecture jobs, and make sure your CV supports the same story.
Add a comment