First Architecture Job Portfolio Examples

Build the portfolio and interview together

Use the Part I portfolio guide to explain academic work and the first-interview guide to practise discussing it. The evidence should tell the same story on the page and in the conversation.

What practices look for first

Most practices scan quickly before they read deeply. They are looking for signs that your work is relevant, understandable and useful for the role they are hiring.

• A strong opening project that matches the kind of practice you are applying to.
• Clear drawings with captions that explain what the reader is looking at.
• Process work that proves judgement, not just a wall of sketches.
• Evidence of your personal contribution on group or studio projects.
• Enough technical and detail awareness for the level of role.

Examples of portfolio evidence that works

• For a Part I role: one strong academic project, one technical drawing or detail, one short page showing model-making or process, and one page proving software competence.
• For a Part II role: a clearer project narrative, more responsibility, stronger drawings, some technical thinking and evidence you can present work in a mature way.
• For a BIM or technical role: model screenshots, coordination examples, drawing sets, clash or issue thinking and a plain explanation of what you did.
• For an interiors role: concept, material logic, FF&E thinking, user journey, technical details and visuals that match the sector.

How to choose projects

Do not choose projects only because they are your favourites. Choose them because they prove something the employer needs to believe.

• Lead with relevance, not chronology.
• Cut weak projects that need a long explanation to make sense.
• Show fewer projects properly rather than many projects badly.
• Use captions to explain brief, scale, role, software and outcome.
• Put the most employer-relevant project near the front.

Common mistakes

• Starting with a beautiful but confusing image.
• Showing too much process without explaining the decision.
• Letting layout style hide the work.
• Not saying what you personally did.
• Sending a huge file that is slow to open.

Architecture Social view

Stephen’s recruiter view is that the best first-job portfolios are generous to the reader. They do not make a busy practice decode your project. They guide the reader through the evidence.

First-job portfolio questions

What can I show without much practice experience?

Use the academic, technical and process work you can explain confidently. Show the brief, the decision and your contribution rather than trying to sound more senior than you are.

Can a group project still be useful?

Yes, if you make the shared context and your own work clear. Label what you contributed and choose evidence you can discuss honestly in an interview.

Test the portfolio against one role

Choose a relevant architecture vacancy. Check whether your opening project shows evidence for that role, then practise explaining your contribution with the portfolio presentation guide.