Editorial
Architecture CV Review Examples
Architecture CV review examples showing what practices scan first, how to structure evidence and how to connect CV claims to portfolio proof.
On this page
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.
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.
This Transistor podcast needs media cookies to play here.Enable videos and podcasts, or accept all optional cookies.
Your choice is remembered across the site. Change it any time.
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.
as-source-card:cv-review-check
CV review checklist
Use this quick check before sending the next application.
- Read more Architecture Social CV and portfolio resources
- Browse live architecture jobs to compare requirements
- Book a Power Hour if you want direct CV feedback
/as-source-card:cv-review-check
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.
as-reader-action:cv-review-next-step
Make your CV easier to trust
The fastest improvement is usually not a redesign. It is clearer evidence and better section order.
- Move role-fit evidence higher.
- Connect CV claims to portfolio proof.
- Use live roles to decide what to prioritise.
/as-reader-action:cv-review-next-step as-holistic-seo-end:architecture-cv-review-examples-11280
For related career support, compare the architecture salary guide, browse current architecture jobs, set up architecture job alerts or contact Architecture Social for a recruiter’s view.
Keep the conversation going
What stayed with you? Join the Architecture Social community to share your experience or ask a question.