What Makes a Good Architecture CV?

A good architecture CV makes your experience easy to understand. It should show your level, project exposure, software, education and practical fit for the role without forcing the reader to decode it.

The portfolio shows the work visually. The CV explains the context: where you worked, what you did, what tools you used and why your experience is relevant.

Watch: Architecture Social video

This Architecture Social video adds useful context before the practical guidance below.

Listen: full architecture CV episode

Prefer audio? This is the podcast version of the original CV workshop, kept with the video for this article.

You can also open the related Architecture Social podcast page.

Start with clarity

Recruiters and hiring teams often scan CVs quickly. If the first page is cluttered, vague or overloaded with graphics, your strongest evidence may be missed.

• Name your current level and target role clearly.
• Keep contact details easy to find.
• Show education and professional experience in a logical order.
• Use project bullets that explain scale, stage, software and responsibility.
• Keep design restrained so the content can be read quickly.

Go deeper with Architecture Social

These related Architecture Social episodes add more context once you have the practical framework.

Related video: CV mistakes to avoid

The original Architecture Social CV workshop stays near the top. This related video adds a sharper look at the CV mistakes that slow applications down.

Related audio: CV tips and mistakes

This related episode goes further into CV mistakes and the practical fixes that make an application easier to judge.

You can also open the related Architecture Social podcast page.

What the CV should include

A good architecture CV normally includes a short profile, key software, education, employment history, selected project experience and a portfolio link. You do not need a long personal statement.

For each role, write bullets that prove what you did. Assisted on residential projects is weak. Supported planning-stage drawing production for a residential scheme using Revit is much clearer.

Software and technical evidence

Software lists are useful, but they are stronger when connected to work. If you say Revit, explain whether you used it for modelling, sheets, detailing, coordination or presentation. If you say Rhino or Grasshopper, show how it supported the design process.

Relationship with the portfolio

Your CV and portfolio should feel connected. If the CV mentions a project, the portfolio should help the reader see it. If the portfolio shows strong work, the CV should explain your role and responsibility.

Common mistakes

• Using a heavily designed CV that is hard to read.
• Listing responsibilities without project context.
• Leaving software evidence too vague.
• Writing a profile full of generic enthusiasm.
• Sending a CV and portfolio that tell different stories.

Architecture Social view

Stephen’s recruiter view is that a good CV helps both sides. It helps the candidate present properly and helps the practice make a quicker, fairer decision.

Next step

Rewrite three project bullets so they include project type, stage, software and your role. Then compare the CV against the Architecture CV guide, the portfolio guide and current architecture jobs.