Architecture CV Review Examples

Architecture CV examples are useful when they show the thinking behind the edit. A good CV is not only tidy. It helps a practice understand your level, evidence, software, project experience and portfolio link quickly.

This Architecture Social CV review is worth using as a practical check. Instead of asking whether your CV looks nice, ask whether every section helps the reader decide if you are worth interviewing.

Watch: Architecture Social reviews CVs

This CV review is useful because it shows the small details that change how quickly a practice understands a candidate’s level and fit.

Listen: CV review lessons for architecture candidates

Prefer audio? The episode gives the longer CV discussion, including structure, presentation and the mistakes that make a strong candidate look unclear.

You can also open the related Architecture Social podcast page.

What a CV reviewer looks for first

A recruiter or practice will usually scan the top half first. That means your current role, level, location, portfolio link and strongest relevant evidence need to be visible without a hunt.

• Can the reader understand your current level?
• Does your profile say something specific, or could it belong to anyone?
• Are project examples linked to scale, sector, stage and responsibility?
• Does the software list match real project evidence?
• Is the portfolio link obvious and working?

Turn claims into evidence

Most weak CVs overuse claims like passionate, creative, motivated and detail-oriented. Those words are not useless, but they do not prove much on their own. Evidence is stronger.

Instead of saying you are experienced in design development, name the project type, stage, software and responsibility. Instead of saying you work well in teams, show coordination, consultants, client contact or drawing package contribution.

What to move up

• Portfolio link, especially if your work is strong.
• Relevant sector experience for the role.
• Live project stages and responsibilities.
• Software used on real work, not only listed as a skill.
• Recent achievements that show responsibility or progression.

Common mistakes

• Writing a profile that sounds like a student statement when applying for a professional role.
• Listing every software package at the same level.
• Making education more prominent than current role evidence when experience should lead.
• Leaving project scale, stage and responsibility vague.
• Letting the CV and portfolio tell different stories.

Architecture Social view

Stephen’s recruiter view is that the CV’s job is to create confidence quickly. It should not try to tell every story. It should make the most relevant story obvious, then send the reader to the portfolio for proof.

Next step

Open your CV and highlight every sentence that is a claim. Then ask whether the line beneath it gives proof. If it does not, rewrite it with a project, responsibility or measurable detail.