An architectural assistant CV and portfolio should work together. The CV tells the reader what to look for, and the portfolio proves it with selected project evidence.
If the two documents feel like separate stories, a practice has to work too hard. The toolkit is simple: clear level, relevant evidence, useful project order and a clean next step.
Watch: reviewing architecture CVs together
Start here if you want to see how small CV decisions change the way an architecture application lands with a reader.
Listen: CV review discussion
Prefer audio? This episode expands on the CV review points that sit behind the toolkit approach.
You can also open the related Architecture Social podcast page.
What the toolkit needs to do
Most assistant applications are not rejected because the candidate has nothing useful. They are rejected because the useful evidence is hard to find.
- Show your current level and the role you want.
- Make the portfolio link obvious and easy to open.
- Use CV bullets that explain project type, stage, software and responsibility.
- Put the strongest relevant portfolio work early.
- Remove pages that look good but do not support the application.
Related audio: sample portfolio choices
This related episode helps you decide what belongs in a sample portfolio and what should wait for the interview.
You can also open the related Architecture Social podcast page.
Connect the CV and portfolio
The CV should not list skills that the portfolio never shows. If you mention Revit, Rhino, model making, planning work, competition experience or residential projects, give the reader somewhere to see that evidence.
The same applies the other way round. If a portfolio project is strong, the CV should explain the context: academic or professional, individual or group, concept or technical, early-stage or detailed.
Use a simple application check
- Can someone understand your level in ten seconds?
- Can they open the portfolio without requesting access?
- Can they see your strongest project before page five?
- Can they tell what you personally did?
- Can they match your evidence to the role advert?
Common mistakes
- Treating the CV as admin and the portfolio as the only creative document.
- Using the same sample portfolio for every practice.
- Listing software as logos with no context.
- Letting page design hide the project information.
- Forgetting that the first reader may be a recruiter, coordinator or director scanning quickly.
Architecture Social view
Stephen’s recruiter view is that the best assistant applications are generous to the reader. They do not shout, overclaim or bury the point. They make it easy to say, yes, this person is worth speaking to.
Next step
Use this toolkit with the architecture CV guide, the portfolio guide, the sample portfolio guide and live architecture jobs.
If you want a second opinion on your CV, portfolio or next move, contact Architecture Social.



Add a comment