A strong architectural CV structure makes the document easier to scan. It should show who you are, what level you are at, what evidence you have and where the portfolio proves it.
You can refine the graphic style later. First, make the order work.
Also watch: original video from this article
This video was already part of the article before the rewrite, so it stays with the guide rather than being replaced by the new media.
Continue with related Architecture Social content
If you want to go deeper, these related Architecture Social episodes add more context without getting in the way of the main guide.
Related audio: early-career CV evidence
This related episode adds early-career advice on presenting experience honestly when your professional history is still developing.
You can also open the related Architecture Social podcast page.
Build the CV in this order
There is no single perfect template, but most architecture CVs are easier to read when the main sections follow a simple order.
- Name, contact details and portfolio link.
- Short profile matched to the role.
- Practice experience, placements or relevant project experience.
- Education and qualifications.
- Software and technical skills.
- Awards, exhibitions or extra evidence where useful.
Write project bullets properly
Each bullet should make the reader more confident, not just fill space. Include project type, stage, responsibility and software where relevant.
A good bullet might explain that you supported planning drawings for a residential scheme, prepared Rhino models for concept options or updated Revit information during a placement.
What to cut
- Generic profile claims with no evidence.
- Software you cannot discuss confidently.
- Old school details that no longer help.
- Repeated responsibilities across every role.
- Portfolio links that are hard to find or broken.
Simple structure example
A practical order is profile, experience, selected project evidence, education, software, then additional achievements. For students or very early-career candidates, education and project evidence may sit higher, but the logic is the same.
The reader should never have to hunt for the basics. If the basics are clear, the portfolio can do the visual work.
Common mistakes
- Putting design before readability.
- Making the first page too dense.
- Hiding dates or role level.
- Using the same CV for every role.
- Forgetting that the portfolio should prove the claims.
Architecture Social view
Stephen’s recruiter view is that structure is not boring. It is what lets the better evidence get noticed.
Next step
Rebuild the CV order first, then use the architecture CV examples guide, the CV professionalism guide, live architecture jobs and the Power Hour career coaching session.
Add a comment