A good first-job architecture portfolio is not a catalogue of everything you have ever designed. It is a short argument that says: I can think, draw, explain, learn and contribute in a studio.
For Part I, Part II and graduate candidates, the best portfolio examples usually show clear project thinking, tidy process, honest contribution and enough technical awareness to make a practice confident you can join the team.
Watch: portfolio review lessons
This related Architecture Social video is useful because it shows how portfolio advice changes when real candidates, tutors and employers are part of the conversation.
Listen: Clubhouse portfolio conversation
The Clubhouse conversation gives the original audio context behind this guide, including portfolio mistakes, early-career pressure and practical first-job advice.
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.
Next step
Before sending your next application, open your portfolio and ask: what does this prove in the first 30 seconds? Then compare it against current Part I roles, Part II roles and the wider Architecture Social guides.
Add a comment