Preparing for an architectural job interview is not about scripting every answer. It is about understanding the practice, knowing your own evidence and being ready to explain how your CV and portfolio connect to the role.
A good interview should feel like a professional conversation. You still need structure, but the goal is simple: help the practice understand your level, your judgement, your project experience and whether you would be good to work with.
Watch: how to shine in an architecture interview
This Architecture Social episode is a strong place to start because it covers how to present yourself clearly before you get lost in over-preparing.
Start with the practice, not yourself
Before you rehearse answers, understand who you are speaking to. Look at the practice’s projects, sectors, scale, location, values and recent news. Then connect that research to the role.
- What type of projects do they win?
- Do they focus on design, delivery, retrofit, interiors, housing, workplace or another sector?
- Which RIBA stages are likely to matter?
- What software and project evidence does the job advert mention?
- Who is interviewing you, and what might they care about?
Prepare three project stories
Most architecture interviews come back to project evidence. Choose three projects you can discuss clearly. For each one, know the brief, your role, the stage, the tools used, the challenge and what you learned.
Do not claim ownership you did not have. It is much stronger to say, ‘I supported the planning package and coordinated selected drawings’ than to imply you ran the whole project when you did not.
Use your portfolio as a conversation tool
Your portfolio is not there to be admired silently. It should help you explain decisions. Open the right project quickly, talk through the role you played and point to evidence without forcing the interviewer to decode everything.
- Keep the PDF easy to navigate.
- Know where your strongest pages are.
- Prepare a shorter sample portfolio for first-stage interviews.
- Keep full project detail ready for later-stage conversations.
- Check the file opens properly before the interview.
Questions you should prepare
You do not need robotic answers, but you should have clear thinking ready for the obvious themes: why this role, why this practice, what you have worked on, where you want to grow and what kind of support helps you do your best work.
- Tell us about yourself.
- Talk us through a project in your portfolio.
- What was your exact role?
- What software have you used in practice?
- What kind of work do you want to do next?
- Why are you looking to move?
Salary and practical details
If salary comes up, stay calm and factual. Know your current salary, your expectation, your notice period, location preferences and right-to-work position. You do not need to over-share, but you do need to be prepared.
Listen: related Architecture Social podcast
The podcast version goes deeper into architecture interview confidence, presentation and the common mistakes candidates make under pressure.
You can also open the related Architecture Social podcast page.
Common mistakes
- Only researching the homepage.
- Talking through every portfolio page with no hierarchy.
- Overstating your responsibility.
- Avoiding salary, notice period or right-to-work questions.
- Forgetting to prepare questions for the practice.
Architecture Social view
Stephen’s recruiter view is that good interview preparation makes the conversation easier for both sides. Candidate-first does not mean ignoring what practices need. It means presenting your evidence clearly so the decision is fairer and faster.
Next step
Before the interview, reread your architecture CV, tighten your sample portfolio and compare the role against live architecture jobs. If you want direct preparation, book a Power Hour career coaching session.
Add a comment