A good architecture CV is not a design manifesto. It is a clear evidence sheet that helps a busy practice understand your level, experience, location, availability and whether it is worth opening your portfolio.
That does not mean it should be dull. It means the design should support the information rather than hide it. Your portfolio can carry the visual depth. Your CV should remove doubt quickly.
Watch: practical advice from Architecture Social
What a good architecture CV needs to do
Most reviewers do not read a CV from top to bottom at first. They scan. They are looking for level, current role, education, project exposure, software, right to work, location, dates and whether the portfolio looks relevant to the role.
If those basics are hard to find, the CV is making the application harder than it needs to be. A clean CV gives the reader confidence before they open the sample portfolio.
The best order for an architecture CV
- Name, email, phone number, location and portfolio link.
- Short profile that says your level, route and strongest evidence.
- Education, including Part I, Part II or relevant technical route.
- Practice experience, internships, placements or relevant project work.
- Selected project types, responsibilities and stages.
- Software, shown honestly and specifically.
- Awards, exhibitions, teaching, mentoring or useful additional experience.
Your profile should be short
The profile is not a place to write a life story. Two or three lines is usually enough. Say what level you are, what kind of work you have done, and what you are looking for next.
For example: Part II Architectural Assistant with experience across early-stage residential and mixed-use projects, confident in Revit, Rhino and Adobe Creative Suite, looking for a London practice where I can develop design and delivery experience.
Show experience with evidence
Avoid vague lines such as worked on a variety of projects. Say what you actually touched: planning drawings, concept options, Revit model updates, presentation packs, site research, coordination notes, schedules or technical details.
If you were part of a team, be honest about it. The useful line is not we delivered a project. It is my role focused on model development, drawing updates and preparing presentation material for client meetings.
Software should be honest
Do not rate yourself 8 out of 10 in Revit unless the practice already knows what that means. It is more useful to say how you used the tool. Did you build concept models, amend sheets, produce planning drawings, coordinate details or prepare visual material?
Years of exposure can help, but only when paired with context. Revit, used for drawing production and model updates during a six-month placement is clearer than Revit: advanced.
How the CV and portfolio work together
Your CV gives the facts. Your sample portfolio proves the judgement. If your CV says you have residential experience, your portfolio should show the most relevant residential project. If your CV says Revit, your portfolio should not only show renders with no technical or drawing evidence.
For more detail on portfolio structure, use the Part II CV and portfolio guide alongside this page.
Common mistakes
- Hiding dates, locations or role levels.
- Making the CV too graphic to scan quickly.
- Listing software without evidence of how it was used.
- Repeating portfolio captions instead of explaining responsibilities.
- Using architect as a title if you are not ARB-registered.
- Sending a full portfolio when a tight sample portfolio would work better.
Architecture Social view
Stephen Drew is the founder of Architecture Social, a recruiter and industry voice with a Part II background. His practical view is that a CV should make the reviewer faster. The best CVs are not the loudest. They are the clearest.
Candidate-first does not mean ignoring what practices need. A good CV respects both sides: it helps the candidate present properly, and it helps the practice make a quicker, fairer decision.
Listen: related Architecture Social podcast
This episode goes deeper into CV and portfolio basics, including presentation, software, cover letters and the mistakes that slow candidates down.
You can also open the Architecture Social podcast page for this episode.
Common questions
Should an architecture CV be one page?
One page can work for students and early-career candidates, but two pages is fine if the information is useful. The real issue is whether the CV is easy to scan.
Should I include a photo on my CV?
Usually no. Let the work, experience and portfolio do the talking. A photo can introduce bias and rarely helps an architecture application.
Should I send my full portfolio with the CV?
For first contact, a small sample portfolio is usually better. Keep it focused, relevant and easy to email. Save the full portfolio for later in the process.
What should Part I and Part II candidates show differently?
Part I candidates should show potential, clarity and willingness to learn. Part II candidates should show more judgement, responsibility, project narrative and readiness for practice.
Next step
If your CV is not getting replies, tighten the sample portfolio next, then review live roles on the Architecture Social jobs board. If you want direct feedback, book a Power Hour career coaching session.
For practical next steps, compare the architecture salary guide, browse current architecture jobs, set up architecture job alerts or contact Architecture Social for tailored advice.
Add a comment