Your architecture CV is a decision-making document. It helps a practice decide whether your level, experience, location, availability and portfolio are worth a closer look.
That means it should be clear before it is clever. A beautiful CV that hides dates, responsibilities or software ability can slow an application down. Your portfolio can carry the visual depth. The CV should remove doubt.
What practices scan first
Most reviewers do not read a CV from top to bottom at first. They scan for level, current role, location, right to work, relevant project types, software, dates and whether the portfolio matches the role.
If those basics are hard to find, the application has already become more work than it needs to be.
- Current level and target role.
- Location, availability and right to work.
- Recent practice experience and project types.
- Software used in real project settings.
- Education, Part I or Part II status and key dates.
A practical CV order
Start with a short profile of two or three lines. Then list recent experience in reverse order, followed by education, software, selected achievements and practical details.
For each role, explain what you actually did. Phrases such as worked on projects or assisted the team are too vague. Practices want to know whether you prepared planning drawings, built Revit models, coordinated with consultants, produced visuals, supported tender packages or worked on site information.
Better phrasing
Instead of saying assisted on residential projects, say supported planning and technical drawing packages for a 40-unit residential scheme, including Revit modelling, drawing updates and consultant coordination notes.
How the CV and portfolio should work together
The CV should tell the reader where to look. The portfolio should prove it. If the CV says you have strong Revit experience, the portfolio should include project evidence that supports that claim.
Do not let the CV and portfolio tell different stories. If one is highly technical and the other is purely conceptual, the reader may be unsure what kind of role you are really targeting.
Common mistakes
- Designing the CV so heavily that it becomes hard to scan.
- Listing every software package without showing working confidence.
- Leaving unexplained gaps, unclear dates or missing locations.
- Writing a profile that could describe almost any candidate.
- Making the CV and portfolio feel like separate applications.
Architecture Social view
Stephen has a Part II background and sees architecture applications from the recruitment side every day. The strongest CVs are not the loudest. They are the ones that make the candidate’s level and evidence easy to understand.
A good CV should make a practice think: this person fits the brief enough to speak with.
What good looks like
For architecture candidates at student, part i, part ii, architect, technologist, bim and interior design level., good looks like a clear, specific decision rather than a generic career move. The CV is not a design poster. It is a practical hiring document that should remove doubt fast.
The reader should be able to understand the problem quickly: they need a cv that supports the portfolio and makes their level, experience and fit obvious quickly. Keep the evidence practical, check it against the role or situation in front of you, and remove anything that makes the next step harder to see.
How to use this in a real job search
Open one live role, one current application or one recent conversation and apply the advice to that specific situation. Do not treat the guide as abstract career theory. The point is to make the next email, CV, portfolio page, interview answer or profile edit sharper.
If you are not sure what to change first, start with the part that a busy practice or recruiter would scan quickest. In most cases that means the title, opening paragraph, project caption, software claim, salary expectation or next-step message.
Quick checklist before you move on
- Have I made the audience, role or situation specific?
- Can I prove the claims with my CV, portfolio, profile or project examples?
- Have I removed generic language that could describe almost anyone?
- Is the next action clear for me and for the person reading it?
- Does this still sound like a real person in the UK architecture market?
When to get a second opinion
Get another view when the stakes are high, the role is especially relevant, or you keep receiving silence after applications. A small adjustment to the framing can make a big difference, especially when your experience is stronger than the way it is currently being presented.
Useful next links
- Architecture cover letter templates
- Part II CV and portfolio guide
- Architecture jobs
- Power Hour career coaching
Next step: Rewrite the CV around clarity first, then use the cover letter and portfolio guides to make the full application consistent.
Add a comment