An architecture CV feels professional when it is clear, specific and honest. It does not need to sound corporate. It needs to help a practice understand what you have done, what you can prove and where the portfolio supports it.
Professionalism is often built through small details: dates, project context, role clarity, software evidence, spelling, file names and working links.
Also watch: original video from this article
This video was already part of the article before the rewrite, so it stays with the guide rather than being replaced by the new media.
Listen: full CV bootcamp episode
Prefer audio? This is the full CV and resume bootcamp episode for architecture candidates.
You can also open the related Architecture Social podcast page.
Continue with related Architecture Social content
If you want to go deeper, these related Architecture Social episodes add more context without getting in the way of the main guide.
Related audio: CV review discussion
This related episode adds more practical review points on how architecture CVs are read.
You can also open the related Architecture Social podcast page.
Professional does not mean generic
The fastest way to make a CV weaker is to fill it with broad claims. Phrases such as highly motivated, passionate designer or excellent team player need evidence behind them.
- Use project types instead of vague claims.
- Explain responsibility without overclaiming.
- Keep dates and job titles consistent.
- Show software in context.
- Make the portfolio link visible and working.
Tighten the project evidence
For each role or project, explain what the work was and what you did. A practice wants to know whether you were modelling, drawing, coordinating, presenting, researching, detailing or supporting a package.
If the experience is academic, say so. If it is professional, explain the stage and your contribution. Honest context builds trust.
Small details that change trust
- Consistent formatting.
- Clear dates and no unexplained confusion.
- Simple file names.
- Correct practice and university names.
- No broken links or oversized files.
A stronger professional summary
The profile does not need to tell your whole story. Two or three specific lines are usually enough: your current level, the kind of experience you have, and the direction you are applying towards.
- Weak: I am a passionate and creative architectural designer.
- Better: Part II architectural assistant with residential and retrofit project experience, confident in Revit, Rhino and Adobe Creative Suite, seeking a design-led practice role in London.
Common mistakes
- Using polished wording with no evidence.
- Overclaiming responsibility on team projects.
- Listing every software package at the same level.
- Making the CV visually busy but hard to read.
- Forgetting that the portfolio must back up the CV.
Architecture Social view
Stephen’s recruiter view is that a professional CV is easy to verify. The stronger the evidence, the less the candidate has to oversell.
Next step
Run a trust check on your CV, then use the architecture CV examples guide, the CV and portfolio evidence guide, live architecture jobs and the interview questions guide.
Add a comment