Practical guide
What Makes a Good Architecture CV?
What makes a good architecture CV, including structure, project evidence, software, portfolio links and common mistakes.
On this page
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.
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.
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.
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.
For related career support, compare the architecture salary guide, set up architecture job alerts or contact Architecture Social for a recruiter’s view.
Questions people ask
Quick answers to the questions candidates ask most when they are rewriting an architecture CV.
Start with a short profile, your employment history, education and relevant software skills. Use selected projects to explain your role and responsibilities, and include a link to your portfolio. Keep the information relevant to the role you want.
Read what to include ↑You might also find useful
Connect each tool to work you have actually done. For Revit, explain whether you used it for modelling, sheets, detailing or coordination. For Rhino or Grasshopper, describe how it supported your design process.
Read the software advice ↑You might also find useful
Use your portfolio to show the work and your CV to explain the context: where you worked, your role and what you contributed. Make the dates, project names and responsibilities consistent so someone can move easily between the two.
Read the portfolio advice ↑You might also find useful
Avoid crowded layouts, generic claims and long lists of software with no examples. Make your strongest experience easy to find, explain your own contribution to projects, and check that your CV and portfolio tell the same story.
Read the common mistakes ↑You might also find useful
Still have a question? Ask in the discussion ↓
Member discussion
Start the discussion
No member comments yet. Have a question about this guide or some advice to share?
Sign in to join the conversation. Please do not post CVs or private candidate details.