Architecture CV Top Tips and Mistakes to Avoid

A good architecture CV is not a design poster. It is a clear professional document that helps a practice understand your level, project experience, software, sectors and direction quickly.

The best CVs do not make the reader decode your career. They make the important evidence easy to find, then let the portfolio add depth.

Watch: architecture CV top tips

This Architecture Social video is a useful starting point because it shows how recruiters and practices scan CVs in real time.

Listen: what makes a good architecture CV

Prefer audio? This Architecture Social episode gives the CV advice more room, including structure, presentation and mistakes to avoid.

What to put near the top

The top half of the first page does most of the work. It should tell the reader who you are, what level you are at and why the application is relevant.

• Name, location and contact details.
• Role title or target level, such as Part II Architectural Assistant or Architect.
• A short profile with specific experience, not a generic personality statement.
• Key software, only where you can genuinely use it.
• Most relevant practice or project experience.

Write a profile that says something

A weak profile says you are passionate, creative and hard-working. A stronger profile says what kind of architecture experience you have, what project stages you have touched and what role you are looking for next.

Keep it short. Three or four lines is usually enough. The profile should set up the evidence below, not repeat the whole CV.

Example CV profile: weak vs better

Weak: I am a passionate and motivated architectural designer looking for an exciting opportunity where I can grow.

Better: Part II Architectural Assistant with UK residential and mixed-use experience, including planning-stage drawings, Revit model updates and presentation material. Looking for a London practice where I can keep developing design and delivery experience.

The second version is not longer for the sake of it. It gives level, project context, software, stage and direction. That is what makes it easier to judge.

Project evidence matters more than duties

Practices are not only reading job titles. They are looking for project scale, sector, stage, software and responsibility. A role that only says ‘assisted the team’ does not help enough.

• What was the project type?
• What stage did you work on?
• What did you personally do?
• Which software supported the work?
• What was the outcome or next project stage?

How the portfolio should support the CV

The CV and portfolio should work together. If the CV claims Revit, planning, technical packages, competitions or client presentations, the portfolio should contain evidence that supports those claims.

• Use the deeper Architecture Social CV guide for structure.
• Use the sample portfolio guide if your portfolio is too long or unfocused.
• Pair the CV with a concise architecture cover letter when the application needs context.

Formatting basics that still matter

A CV can look designed without becoming hard to read. Keep the hierarchy clear, use enough white space and do not make the reader zoom in to understand basic information.

• Use one or two pages unless you have a strong reason for more.
• Export as a PDF unless the employer asks for another format.
• Keep file names professional and searchable.
• Make the portfolio link visible and test it before sending.
• Check the CV on a phone as well as a laptop.

Short email to send with your CV

Try a simple note like this: Hi [Name], I am applying for the [role title] position. I have attached my CV and sample portfolio, with relevant experience in [project type, stage or software]. I would be very happy to discuss how my background could fit the team. Best, [Name].

Keep it specific. Replace the bracketed parts with evidence from the role, not generic enthusiasm.

Common CV mistakes

• Opening with a vague profile that could fit any candidate.
• Using too many columns, icons or tiny text.
• Listing software without project evidence.
• Hiding dates, locations or role levels.
• Writing long duties instead of useful project evidence.
• Making the CV and portfolio tell two different stories.

Architecture Social view

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

Next step

Open your CV and rewrite the top half first. Then compare the evidence with live architecture jobs so you can see whether your CV matches the market you are applying into.