An architecture CV has impact when it is clear. A clean layout helps, but the real work is in the wording: who you are, what you have done, what evidence supports it and what kind of role you are targeting.
If a practice cannot quickly tell whether your experience is academic, freelance, practice-based or personal, the CV is asking too much of the reader.
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.
Sharpen the profile
A profile should explain your level and direction in plain language. Avoid broad claims about passion or creativity unless you immediately connect them to real project evidence.
- Current level or qualification.
- Role type you are targeting.
- One or two relevant sectors, tools or project strengths.
- Availability or location if it matters.
- Portfolio link near the top.
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: honest CV evidence
This related episode adds context on explaining early or limited experience without overclaiming.
You can also open the related Architecture Social podcast page.
Separate academic and practice evidence
Academic projects can be powerful, but they need context. Practice work, freelance work and university work should not blur together. Make it clear what setting each piece of experience came from.
If a project was part of a course, say so. If it was freelance or practice work, explain the role, scope and responsibility. Honesty makes the CV more credible.
Use examples without copying them
CV examples are useful as prompts, not templates to paste. Look at what the example is doing: clearer section order, better evidence, sharper role language or stronger practical detail. Then rewrite your own experience in your own words.
Make Revit and software claims useful
If Revit, Rhino, AutoCAD, Adobe tools or BIM workflows matter, connect them to specific work. A practice is not just checking whether you have seen the software. They want to know what you can do with it.
Improve impact with evidence
- Replace vague claims with project examples.
- Use short bullets with role, task and outcome.
- Move the strongest relevant evidence higher.
- Remove lines that sound impressive but prove nothing.
- Check whether the portfolio backs up the CV.
Keep the tone professional but human
A CV does not need to sound like a corporate brochure. Use plain language. If you worked on drawings, say what drawings. If you supported a project, say what you supported. If you are still learning, show progress without pretending to be senior.
Common mistakes
- Writing a personal statement that says nothing specific.
- Mixing academic, freelance and practice work without labels.
- Overloading the CV with software logos.
- Leaving practical details until the end.
- Forgetting that the first reader may only scan for a few seconds.
Architecture Social view
Stephen’s recruiter view is that clarity is commercial. If the evidence is easy to understand, it is easier to recommend the candidate and easier for a practice to say yes to a conversation.
Next step
Use this guide with the architecture CV guide, the portfolio guide, live architecture jobs and career coaching if you want direct feedback.
Add a comment