A good architecture CV and portfolio review is not about making the document prettier for its own sake. It is about finding out whether the reader can understand your level, judgement and project evidence quickly.
This RIBA Gulf Chapter session brought together Stephen Drew, Andy Shaw and Jennie Binchy to look at CVs, portfolios, cover letters and how candidates approach practices. The useful lesson is still current: clarity beats noise.
Watch: RIBA Gulf CV and portfolio review
This session is useful because it shows how CVs and portfolios are read in practice, not just how candidates hope they will be read.
Go deeper with Architecture Social
These related Architecture Social episodes add more context once you have the practical framework.
Listen: RIBA Gulf career context with Andy Shaw
This related Architecture Social episode adds Gulf-region career context with Andy Shaw, useful if you are thinking beyond the UK market.
What reviewers are really scanning for
Most reviewers do not read your application like a dissertation. They scan for fit, level, software, sectors, project stage, responsibility and whether the portfolio supports the CV claims.
- Role level: Part I, Part II, architect, technician, designer or specialist.
- Project type and scale.
- Your personal contribution, not only the studio output.
- Software and technical evidence.
- Whether the sample portfolio makes them want to see more.
CV lessons from a review session
The CV should make the portfolio easier to read. If the CV says you worked on planning, technical design, Revit coordination or client presentations, the portfolio should contain evidence that supports that claim.
- Use the Architecture Social CV guide if the structure is unclear.
- Keep the profile short and specific.
- Put relevant project experience above generic responsibilities.
- Avoid long software lists with no proof.
- Make dates, role titles and locations easy to scan.
Portfolio lessons from the session
The sample portfolio should act like a confident introduction, not a full archive. It needs enough evidence to earn a conversation without making the reader work too hard.
- For the difference between formats, read sample portfolio vs full portfolio.
- Lead with your strongest relevant project.
- Use captions that explain brief, role and outcome.
- Show process where it proves judgement.
- Cut pages that only repeat the same skill.
Approaching practices
A direct approach works better when it is specific. The message should explain why that practice, what you can offer and what you are asking for. A vague email with a heavy PDF attached is easy to ignore.
- Use a clear subject line.
- Keep the email short.
- Mention a relevant project, sector or studio direction.
- Attach a sensible sample portfolio size.
- Follow up politely if there is no reply.
Common mistakes
- Designing the portfolio for another student instead of a busy practice.
- Letting beautiful layouts hide weak project explanation.
- Forgetting to connect CV claims with portfolio evidence.
- Sending too many pages too early.
- Approaching every practice with the same message.
Architecture Social view
Stephen’s recruiter view is that getting noticed starts with respect for the reader. If someone can understand your value quickly, they are more likely to keep reading.
Next step
Open your CV and sample portfolio side by side. If the first 30 seconds do not prove level, role, project evidence and direction, use the Architecture Social resources before sending another application.
Add a comment