Behavioural interview questions ask how you acted in a real situation. In architecture interviews, they are used to test judgement, teamwork, communication, pressure and how you learn from mistakes.
The trick is not to sound perfect. The trick is to answer clearly, use a real example and show what changed because of your actions.
Watch: online or in-person interviews?
This related short video is a useful reminder that interview context matters. In person, online or hybrid, the aim is still to help the practice trust your judgement.
Listen: related Architecture Social podcast
The related podcast goes deeper into architecture interview preparation, portfolio presentation and how to make the meeting easier for everyone.
You can also open the Architecture Social podcast page for this episode.
Why practices ask behavioural questions
A portfolio shows the work. Behavioural questions show how you work. That matters because architecture is collaborative, deadline-driven and full of judgement calls. A practice wants to know how you handle pressure, feedback and ambiguity.
Common behavioural interview questions
- Tell me about a time you worked under pressure.
- Describe a project where you had to manage conflicting feedback.
- Give an example of a mistake you made and what you learned.
- Tell me about a time you supported a team member.
- Describe a situation where you had to explain a technical issue clearly.
- Tell me about a time you challenged a design or delivery decision.
Use STAR, but keep it human
STAR means Situation, Task, Action and Result. It is useful because it stops you rambling. The mistake is sounding robotic. Use the structure, but speak like a normal person.
- Situation: what was happening?
- Task: what were you responsible for?
- Action: what did you actually do?
- Result: what changed, and what did you learn?
A better architecture example
Weak answer: I work well under pressure and I am a good team player.
Better answer: On a residential project, we had a late planning comment that affected the facade setting-out. I pulled together the relevant drawings, checked the Revit model against the latest consultant information and prepared a short options note for the project architect. We agreed a route quickly, avoided issuing conflicting information and I learned to flag coordination risks earlier.
Use your portfolio as evidence
When possible, connect the answer to a project in your portfolio. That makes the story easier to believe and gives the interviewer something concrete to look at. If you are Part I or Part II, university examples are fine, but be honest about your role.
Common mistakes
- Using a vague answer with no project, person or outcome.
- Blaming everyone else when discussing conflict or mistakes.
- Choosing an example that does not relate to the job.
- Over-explaining the background and rushing the result.
- Pretending you have never made a mistake.
Architecture Social view
Stephen’s recruiter view is that the best candidates make the interviewer’s job easier. They give a clear example, explain their role and show they can learn. That is much more convincing than a polished but empty answer.
Before your next interview, read our wider guide to architecture interview questions and check your sample portfolio is ready to support your answers.
If you are actively interviewing, browse architecture jobs or speak to Architecture Social about the kind of examples practices expect at your level.
Add a comment