An architecture CV blueprint is useful because it gives the document a job. The CV should explain your level, evidence, skills and portfolio link quickly enough for a practice to decide whether to look closer.
Make the structure work before you worry about graphic style. A beautiful CV that hides dates, project responsibility or software context will still slow the application down.
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.
Listen: full CV bootcamp episode
Prefer audio? This is the full CV and resume bootcamp episode for architecture candidates.
You can also open the related Architecture Social podcast page.
Use a simple order
- Name, contact details and portfolio link.
- Short profile matched to the role.
- Practice experience, placements or selected project experience.
- Education, Part I or Part II status and key dates.
- Software and technical skills in context.
- Awards, exhibitions or extra evidence where useful.
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: Architecture Social podcast
This related episode adds context for candidates who are building experience and need to present it honestly.
You can also open the related Architecture Social podcast page.
Build the CV around evidence
Every important claim should be supported by context. If you mention Revit, Rhino, technical packages, competitions, retrofit or residential work, the reader should understand where that evidence comes from.
Use project type, stage, responsibility and software in short bullets. Avoid long paragraphs that sound impressive but do not tell the reader what you actually did.
Example structure
- Profile: one clear sentence on level and direction.
- Experience: role, practice, dates and two to four evidence-led bullets.
- Projects: only where they add useful proof.
- Education: course, school, dates and relevant achievements.
- Software: grouped by confidence and real use.
Common mistakes
- Putting design before readability.
- Hiding the portfolio link.
- Writing a profile that could describe any candidate.
- Listing software without project evidence.
- Letting the CV and portfolio tell different stories.
Architecture Social view
Stephen’s recruiter view is that structure is not boring. It is the thing that lets good evidence get noticed faster.
Next step
Use this with the architecture CV examples guide, the CV and portfolio evidence guide, live architecture jobs and the Power Hour career coaching session.
Add a comment