Architecture CV Guide With Examples

An architecture CV should make your level, experience, project evidence and practical fit clear within the first scan. It is not there to show every detail of your career. It is there to help the reader decide whether to open the portfolio and invite a conversation.

Search demand suggests useful search demand around architecture CV, architecture CV examples and architecture CV template phrases. The lesson is simple: candidates want examples, not vague advice.

Watch: what makes a good architecture CV?

This Architecture Social episode fits directly because a good CV is about structure, evidence and making the reader’s first scan easier.

What an architecture CV needs to show

The best CVs answer the practical questions quickly: who are you, what level are you at, what have you worked on, what software can you use and what evidence can you show?

• Current role or target level.
• Location, availability and right-to-work information where relevant.
• Education, Part I, Part II, Part III or ARB status where accurate.
• Practice experience with project sectors and stages.
• Software and digital skills connected to real project outputs.
• Portfolio link or attachment note.

Architecture CV structure

Keep the structure predictable. Hiring managers and recruiters scan quickly, so creativity in layout should not make basic information harder to find.

• Header: name, contact details, location and portfolio link.
• Profile: two or three practical lines, not a generic statement.
• Experience: most recent first, with project context and contribution.
• Education: clear dates and qualifications.
• Software: honest, relevant and easy to verify.
• Selected extras: awards, teaching, writing, volunteering or public speaking if useful.

Architecture CV examples: weak vs better

Weak: ‘I worked on a range of residential and commercial projects.’ Better: ‘Supported planning and developed design packages for residential and workplace projects, including drawings, diagrams, consultant updates and presentation material.’

The better line gives project type, stage and contribution. It still stays concise, but it gives the reader something they can trust.

Make software believable

A software list is useful, but only if it feels credible. If you list Revit, Rhino, AutoCAD, SketchUp, Adobe, Enscape or Grasshopper, connect the tool to the kind of work you produced.

Connect the CV to the portfolio

The CV and portfolio should support each other. If the CV says you have strong technical experience, the portfolio should not only show concept images. If the portfolio leads with housing, the CV should explain your role on housing work.

What to do with an architecture CV template

A CV template can help with structure, but it cannot decide the evidence for you. Treat a template as scaffolding, then replace generic lines with real project examples.

• Keep the layout clean enough to scan.
• Remove template text that sounds like everyone else.
• Adapt the order to the role you are applying for.
• Make the portfolio link impossible to miss.
• Check that every claim can be backed up by project evidence.

Before sending the CV

Read the CV alongside the job advert. If the advert asks for Revit, residential experience and planning-stage work, those signals should be easy to find. If they are buried, reorder the CV before sending it.

This is where small edits make a big difference. You may not need a new CV from scratch. You may need a sharper first page, clearer project bullets and a portfolio link that actually works.

Go deeper with Architecture Social

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

Related audio: what makes a good architecture CV?

The podcast version goes deeper into CV and portfolio basics, including presentation, software, cover letters and mistakes that slow applications down.

You can also open the related Architecture Social podcast page.

Common mistakes

• Writing a profile that could belong to almost any candidate.
• Using a designed CV that is difficult to read on screen.
• Listing duties without project context.
• Overclaiming responsibility on team work.
• Forgetting to make the portfolio link obvious.

Architecture Social view

Stephen’s recruiter view is that a good architecture CV is not about sounding impressive. It is about being specific enough to be trusted.

Next step

Read your CV against one live role from the Architecture Social jobs board. Then tighten the first scan, check your portfolio matches the claims, and use Power Hour career coaching if you want direct feedback.