Using English well in your architecture job search is not about sounding posh, academic or perfect. It is about making your experience easy to understand.
This matters for CVs, portfolio captions, emails, cover notes and interviews. Clear English helps a practice see what you did, what you know and whether you are right for the role.
Watch: language and better applications
This Architecture Social video is relevant because better wording helps your application stand out without turning it into corporate noise.
Clear beats complicated
Some candidates try to sound more professional by making sentences longer. That usually makes the application harder to read. Short, specific sentences often feel more confident.
- Say what the project was.
- Say what stage it reached.
- Say what you personally did.
- Say which tools or judgement were involved.
- Say what the outcome or learning was.
Related audio: standing out in a crowded job market
This related episode adds a wider job-market angle, especially if you are trying to make your application clearer and more memorable.
You can also open the related Architecture Social podcast page.
Where better English helps most
Your CV profile and portfolio captions are the biggest quick wins. These are the places where a few clearer words can change how the whole application feels.
Instead of writing that you developed strong communication skills, show the context: presented design options to tutors and peers, coordinated group work and explained project decisions through drawings and models.
Simple wording rules
- Use active verbs such as produced, coordinated, researched, modelled and presented.
- Avoid vague phrases such as helped with, worked on and involved in.
- Use plain project descriptions before design theory.
- Keep email introductions short.
- Read captions out loud to see if they sound natural.
Interview language
In interviews, clear English helps you answer without rambling. Use a simple structure: situation, action, result and what you learned. You do not need to memorise a script, but you do need a route through the answer.
Common mistakes
- Trying to use impressive words instead of clear evidence.
- Leaving the reader to guess your role on a project.
- Writing portfolio captions as if they are university essays.
- Apologising for English when the actual issue is structure.
- Not asking someone to proofread the final version.
Architecture Social view
Stephen’s recruiter view is that practices are not judging a grammar exam. They are judging whether they understand your experience, your judgement and your fit for the role.
Next step
Take one project in your portfolio and rewrite the caption in plain English. If you need more structure, read the architecture portfolio guide, the CV guide and the Power of Language episode.
Add a comment