To shine in an architecture interview, you need to explain your work clearly, show judgement and make the practice confident you can contribute. It is not about memorising perfect answers.
The strongest candidates prepare the basics, know their portfolio, understand the practice and can talk honestly about what they did, learned and want to do next.
Watch: Architecture Social video
This Architecture Social video adds useful context before the practical guidance below.
Listen: full architecture interview episode
Prefer audio? This podcast version adds the full Architecture Social conversation for anyone who wants to go deeper.
You can also open the related Architecture Social podcast page.
Start with the role
Before preparing answers, read the job description properly. What level is the role? What sectors, software, stages or responsibilities are mentioned? Your interview examples should connect to those needs.
- For Part I roles, show potential, curiosity and clear communication.
- For Part II roles, show stronger project narrative and responsibility.
- For Architect roles, show delivery, coordination and client or consultant awareness.
- For BIM or technical roles, show process, standards and problem-solving.
Go deeper with Architecture Social
These related Architecture Social episodes add more context once you have the practical framework.
Related video: after the architecture interview
The original interview video stays near the top. This related Architecture Social episode helps you think beyond the interview and into follow-up, feedback and offers.
Related audio: what happens after the interview
This related episode covers the stage candidates often forget: follow-up, feedback, rejection and offer handling.
You can also open the related Architecture Social podcast page.
Prepare your portfolio walkthrough
Do not open the portfolio and hope the conversation finds its own shape. Choose two or three projects you can explain well. Know the brief, your role, the stage, the tools and the main decision you made.
A useful walkthrough is not a lecture. It is a guided conversation. Explain why each project is relevant to the role and give the interviewer space to ask questions.
Questions you should be ready for
- Talk me through a project you are proud of.
- What was your personal contribution?
- How do you handle feedback or changes?
- Which software are you strongest in and where are you still developing?
- Why are you interested in this practice and this role?
Salary and practical details
Salary can feel awkward, but it is part of the process. Know your current salary, target range, notice period and practical constraints before the interview. If you are unsure, use market evidence rather than guessing.
If asked about expectations, give a sensible range and explain that you are open to discussing the full role, responsibility and package.
Common mistakes
- Only researching the homepage and not the actual work.
- Rambling through every page of the portfolio.
- Being vague about personal contribution.
- Speaking negatively about a previous employer.
- Not preparing questions for the practice.
Architecture Social view
Stephen’s recruiter view is that good interviews feel like evidence-led conversations. If you can explain your decisions clearly, you immediately become easier to trust.
Next step
Pick three portfolio projects and prepare a two-minute explanation for each. Then use the interview questions guide, the portfolio guide and live architecture jobs to practise against real roles.
Add a comment