A strong architecture CV and portfolio should tell the same story. The CV gives the reader the facts: experience, education, software, project stages and practical details. The portfolio gives the evidence.
If either one feels unclear, the whole application becomes harder to trust. This guide is for candidates who have work to show, but need to make the pack sharper before applying.
Watch: what makes a good architecture CV?
This Architecture Social episode is a strong starting point because a better portfolio is easier to understand when the CV gives the right context.
Start with the first thirty seconds
Most practices will not read every line first. They scan. In the first thirty seconds, they should understand your level, location, availability, core software, recent experience and the type of work you can show.
- Put your current level and target role near the top of the CV.
- Make dates, practice names and education easy to find.
- Keep software honest and relevant to project evidence.
- Use a portfolio opening project that supports the role you want.
- Make sure the CV and portfolio use consistent project names where possible.
Make the CV explain the portfolio
A portfolio with beautiful pages can still be confusing if the CV gives no context. If you worked on a mixed-use scheme, residential retrofit, workplace interior or competition project, say what you did and which stage it reached.
The portfolio can then show selected evidence from that work. The reader should not have to guess whether a drawing was academic, professional, individual or produced as part of a team.
Choose portfolio projects with intent
Do not include projects just because they are finished. Include them because they prove something useful: concept thinking, technical ability, Revit confidence, presentation skill, client awareness, coordination or sector relevance.
Tighten the application pack before sending it
Before applying, open the CV and portfolio as if you are the hiring manager. Ask what is clear, what is missing and what feels like filler. If the strongest project appears too late, move it forward. If the CV repeats generic claims, replace them with evidence.
Use a simple review checklist
- Can someone understand your level within thirty seconds?
- Does the CV explain the project evidence shown in the portfolio?
- Does the portfolio show your strongest relevant project early?
- Are team projects labelled honestly?
- Can every page justify its place in the application?
This sounds basic, but it is where many architecture applications fall down. Candidates often keep adding more pages when the better move is to make the strongest evidence clearer.
Turn feedback into action
If you receive portfolio or CV feedback, do not try to fix everything at once. Start with the points that affect first impressions: title, layout, project order, captions, file size and the opening CV profile.
Listen: related Architecture Social podcast
The podcast version goes deeper into CV and portfolio basics, including presentation, software, cover letters and the mistakes that slow candidates down.
You can also open the related Architecture Social podcast page.
Common mistakes
- Using a designed CV that looks good but is difficult to scan.
- Sending a huge portfolio file that slows the application down.
- Hiding the best project behind a long introduction.
- Listing software without showing how it was used.
- Forgetting that the CV, portfolio and cover letter should support each other.
Architecture Social view
Stephen’s recruiter view is that the best applications make the hiring conversation easier. They do not rely on polish alone. They show the right evidence, in the right order, with enough context to trust it.
Next step
Compare your pack against live architecture jobs, then tighten your architecture CV and portfolio. If you want direct feedback, book a Power Hour career coaching session.
If you want a second opinion on your CV, portfolio or next move, contact Architecture Social.
Add a comment