Architecture CV Examples Guide

Architecture CV examples are useful when they show how to arrange evidence clearly. They are not scripts to copy. A strong CV helps a practice understand your level, project experience, software, education and portfolio link quickly.

The best examples feel practical. They remove doubt and make the next step easier: open the portfolio, invite the candidate to interview, or ask a sharper follow-up question.

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 review discussion

Prefer audio? This is the full Architecture Social CV review conversation in podcast form.

You can also open the related Architecture Social podcast page.

What a good CV example proves

A good example does not try to impress with vague language. It gives the reader facts they can use.

• Current level and target role.
• Project type, stage and responsibility.
• Software used in real project or academic settings.
• Education, Part I or Part II status and key dates.
• A portfolio link that is easy to open.

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: candidate presentation

This related episode adds another Architecture Social angle on community, presentation and how candidates show their work.

You can also open the related Architecture Social podcast page.

Make evidence easy to scan

Most practices scan before they read. That means section order matters. Put the most useful information where someone will naturally look first.

For each role or project, use plain language: project type, what you did, what software or drawings were involved, and what the work proves.

Better CV wording examples

• Weak: Worked on design projects.
• Better: Developed planning-stage drawings and presentation material for a residential studio project, including plans, sections and Rhino modelling.
• Weak: Strong Revit skills.
• Better: Used Revit to prepare drawing updates and model changes during a practice placement, with selected work shown in the portfolio.

Quick checklist before sending

Before you send the CV, check it like a recruiter or practice would. You are looking for friction: anything unclear, hidden, overdesigned or unsupported.

• Can someone see your level in the first few seconds?
• Is the portfolio link visible and working?
• Do project bullets explain what you actually did?
• Are software claims backed by examples?
• Does the CV point towards the kind of role you want next?

Common mistakes

• Starting with a profile that could describe anyone.
• Listing software without project context.
• Hiding practical details such as location, availability or right to work.
• Making the CV and portfolio tell different stories.
• Using design styling that makes the CV harder to read.

Architecture Social view

Stephen’s recruiter view is that clarity beats decoration. A CV can still look good, but it must first help a practice make a quicker and fairer decision.

Next step

Use this guide with the architecture CV guide, the CV and portfolio examples guide, the architectural CV structure guide and live architecture jobs.