Architecture interview questions are rarely just looking for the right words. They are testing whether your experience is real, whether you understand your own work and whether the practice can trust you in the role.
The strongest answers are specific. Name the project type, stage, your role, the challenge, what you did and what happened next. If you speak only in general terms, the interviewer has to do too much work.
Watch first: how to shine in an architecture interview
Watch this early because the page is about proving experience, and the video shows how to present that evidence clearly under interview pressure.
Questions about project experience
- Talk me through a project you are proud of.
- What was your role on that project?
- Which RIBA stages have you worked across?
- What changed during the project and how did you respond?
- What would you do differently next time?
Do not turn this into a long portfolio lecture. Pick one project and use it to prove judgement, responsibility and learning. Keep checking that the example matches the role you are interviewing for.
Questions about technical judgement
- How have you dealt with a technical problem?
- How confident are you with Revit or BIM workflows?
- Have you produced planning, tender or construction information?
- How do you check your own drawings?
If you are early-career, it is fine to say you are still developing. What matters is showing that you understand accuracy, coordination and consequences. A good answer can include what you checked, who you asked and how you improved the information.
Questions about teamwork
- How do you handle feedback?
- Tell us about a difficult team situation.
- How do you communicate when you are unsure?
- What kind of studio environment helps you do your best work?
Practices are hiring a colleague, not just a portfolio. Use examples that show maturity, reliability and the ability to work with other people under pressure.
Use a simple answer structure
Try this structure: context, role, action, result, reflection. It keeps you from rambling and helps the interviewer see the level you operated at.
- Context: what was the project or situation?
- Role: what were you responsible for?
- Action: what did you actually do?
- Result: what changed or what was delivered?
- Reflection: what did you learn?
Listen: interview confidence and structure
The podcast gives more room to explore interview structure, confidence and how to avoid vague answers.
You can also open the related Architecture Social episode page.
Common mistakes
- Talking about the project but not your own role.
- Giving polished answers with no evidence.
- Blaming previous employers or tutors.
- Pretending to know something when you do not.
- Forgetting to ask questions back about the role and team.
Architecture Social view
Stephen’s recruiter view is that good interview prep is not memorising scripts. It is choosing the right evidence before the meeting, so you can answer calmly and specifically.
Next step
Before your next interview, choose three projects and prepare one clear example for each. Review live architecture jobs to understand what practices are asking for, and use the architecture interview tips guide for wider preparation.
Add a comment