Architectural achievements and academic excellence can strengthen a CV, but only when they are explained clearly. A practice needs to understand what the achievement proves.
Do not just list awards, marks or impressive phrases. Translate them into evidence: project type, brief, role, skill and outcome.
Watch: Architecture CV bootcamp
This Architecture Social CV bootcamp is useful if you want to make achievements clearer without turning the CV into a sales pitch.
Listen: CV bootcamp audio
Prefer audio? This episode expands on how to make CV evidence easier for a practice to understand.
You can also open the related Architecture Social podcast page.
Decide what counts as an achievement
An achievement does not have to be a formal award. It can be a strong academic project, competition shortlist, research topic, dissertation angle, live brief, technical study or leadership role.
- Awards, scholarships or distinctions.
- High-quality academic projects.
- Competition or exhibition work.
- Research, dissertation or thesis strengths.
- Team contribution, mentoring or student society work.
Related audio: reviewing architecture CVs
This related discussion adds practical examples of how CV wording can help or hurt an architecture application.
You can also open the related Architecture Social podcast page.
Translate achievements into evidence
A strong CV line explains why the achievement matters. Instead of saying a project was excellent, explain the constraint, method, result and relevance.
For example, a sustainability project becomes stronger when you mention retrofit strategy, material research, environmental testing or the design decision it influenced.
Where to place achievements
- Put the most relevant achievement near the role or education it supports.
- Keep an awards section short if you use one.
- Mention project-based achievements in the project or experience section.
- Use the portfolio to show the work behind the claim.
- Do not let achievements replace practical evidence.
Common mistakes
- Writing achievements with no context.
- Using inflated language that sounds hard to trust.
- Hiding strong academic work at the bottom of the CV.
- Forgetting to link achievements to portfolio pages.
- Assuming a practice will understand university marking or studio context.
Architecture Social view
Stephen’s recruiter view is that achievements help when they make the candidate easier to understand. The CV should make the evidence credible, then the portfolio should prove it.
Next step
Review your strongest evidence with the architecture CV guide, the portfolio guide, live architecture jobs and the 30-60-90 day plan template.
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