Architecture CV industry expectations are practical. Practices want to understand your level, evidence, software, project experience and how quickly they can connect your background to the role.
A CV can be well designed and still miss the point if it does not answer those basic questions.
Watch: are universities keeping up
This Architecture Social conversation is useful because CVs often have to bridge the gap between education, early experience and what practices need.
What practices scan first
- Current level and target role.
- Relevant project experience.
- Software used in context.
- Education and Part I or Part II status.
- Portfolio link and availability.
Related audio: architecture education and practice
This related episode adds context on the relationship between universities, future architects and practice expectations.
Translate your evidence into practice language
Academic work is useful, but it needs context. Explain the brief, scale, tools, outputs and what the project proves about your thinking.
Practice experience should be even clearer: project type, stage, team, responsibility and software usually matter more than generic descriptions.
Common mistakes
- Assuming a practice understands the studio brief.
- Using education language without practical translation.
- Listing every software package equally.
- Not explaining project responsibility.
- Making the portfolio link hard to find.
Architecture Social view
Stephen’s recruiter view is that candidates do better when they help practices make the translation. The CV should show why your background is useful now.
Next step
Use this with the CV market guide, the practice applications guide, live architecture jobs and the free student membership.
Add a comment