Good architectural CV feedback should make the document clearer, more credible and easier to assess. It should not turn the CV into a private biography or a design poster.
The useful question is simple: what does the reader need to trust before they invite you to interview?
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.
Start with the practical details
Contact details, location, right to work, availability and portfolio access are not boring. They affect whether the conversation can move forward.
- Make contact details easy to find.
- Use a working portfolio link.
- State right-to-work or visa context where relevant.
- Mention location or relocation plans if useful.
- Keep availability clear and factual.
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 structure
This related episode adds a bootcamp-style view on structure, presentation and evidence.
You can also open the related Architecture Social podcast page.
Make practical details trustworthy
If you are applying internationally, be especially clear about eligibility and location. If a practice is unsure whether the basics work, strong project evidence may never get proper attention.
Photos are optional and context-dependent. In many UK architecture applications, the CV does not need one. If you use one, it should be professional and should not distract from evidence.
Questions good feedback should answer
- Can the reader understand your level quickly?
- Are practical details clear enough to avoid uncertainty?
- Does the profile say something specific?
- Is the strongest project or practice evidence easy to find?
- Does the portfolio prove the most important claims?
Tighten the professional narrative
A CV should tell a coherent story, but that story should be built from evidence. Use project type, stage, software, responsibility and portfolio proof rather than broad claims.
- Replace long summaries with short, specific profiles.
- Explain experience in plain language.
- Use accurate role titles.
- Make academic and professional work distinct.
- Cut anything that looks polished but adds no hiring evidence.
Be careful with role language
In the UK, ‘architect’ is a protected title. Do not call yourself an architect unless you are ARB-registered. Use accurate wording such as architectural assistant, Part I, Part II, architectural designer, architectural technologist or junior designer where appropriate.
Common mistakes
- Making eligibility or availability hard to understand.
- Adding a photo that changes the tone of the CV.
- Using inflated language instead of evidence.
- Letting design style reduce readability.
- Leaving the portfolio to explain everything.
Architecture Social view
Stephen’s recruiter view is that the best CV feedback improves trust. A practice should finish the first scan with fewer questions, not more.
Next step
Review your CV against the architecture CV guide, the portfolio guide, live architecture jobs and Power Hour career coaching if you want direct help.
Add a comment