Editorial

Architecture Portfolio Tips That Help You Stand Out

Practical architecture portfolio tips on project choice, page order, captions, file size and interview impact.

First published 3 min readJoin the discussion
On this page

Good architecture portfolio tips usually come back to one point: make the reader understand your value quickly. The portfolio is not just a collection of attractive pages. It is evidence for the role you want.

That means choosing projects carefully, explaining your role clearly and removing anything that looks nice but does not help the practice make a decision.

Watch: Architecture Social video

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

Ready when you are.

This YouTube video needs media cookies to play here.Enable videos and podcasts, or accept all optional cookies.

Your choice is remembered across the site. Change it any time.

Watch with YouTubeOpen on YouTube ↗

Start with the role

A portfolio for a Part I role, a Part II role, a technical role and an interiors role should not feel identical. Before editing pages, look at the job advert and ask what evidence the practice needs.

  • Project type and scale.
  • Design process and judgement.
  • Technical drawings or delivery experience.
  • Software and workflow evidence.
  • Your individual contribution.

Choose the right portfolio guide

Use the portfolio workshop for structure and captions, or the first-job portfolio guide for early-career examples of useful evidence.

Choose evidence, not just images

Beautiful images help, but they are not enough. A practice needs to understand what the project was, what you did and why the page matters.

Use short captions to explain context. If a drawing, model or render proves a skill, say what it proves. Do not expect the reader to guess.

Keep the portfolio usable

  • Keep the sample portfolio short enough to review quickly.
  • Put the strongest relevant work early.
  • Use a sensible file size.
  • Avoid tiny drawings that cannot be read on screen.
  • Label academic, professional, team and individual work honestly.

Common mistakes

  • Opening with the weakest project because it is chronological.
  • Including every page from university or practice work.
  • Letting graphic style hide unclear evidence.
  • Not explaining personal responsibility.
  • Sending one generic portfolio for every role.

Architecture Social view

Stephen’s recruiter view is that a portfolio should reduce friction. If the reader has to work too hard to understand your level, the portfolio is not doing enough.

Portfolio editing questions

Which project should go first?

Choose the strongest relevant evidence for the role rather than following project dates automatically. Make the brief, your contribution and the reason for showing the project clear near the start.

Are captions worth the space?

A short caption can explain what a drawing proves. Use it for the context, decision or contribution the image cannot communicate on its own.

Improve one project before adding another

  • Compare the opening project with one relevant job description.
  • Cut a page that repeats evidence already shown.
  • Rewrite one caption to explain your contribution or decision.
  • Check the PDF is readable on screen.

Make sure the CV and portfolio describe the same work, then compare the result with current architecture vacancies.

Keep the conversation going

What stayed with you? Join the Architecture Social community to share your experience or ask a question.