How many projects should I bring to an architecture interview?

Prepare two in depth and have a few more ready to show if asked. One project you can explain thoroughly beats a fast tour of ten.

Should I bring a printed portfolio or a tablet?

Ask the practice what they prefer. Whatever you bring, make sure you can find any drawing in a few seconds and talk without reading from it.

What if my best project was a student project?

Use it, and say so. Explain the brief, the constraints you set yourself and how you would adapt it for a real client and budget.

How do I answer if I disagreed with the lead architect on a project?

Describe the disagreement as a design question, what you proposed and why, and how it was settled. End with what you learned, even if your idea wasn't chosen.

How long should my answer to "walk me through a project" be?

About five minutes for the first pass. Then stop and let them choose where to go deeper.

Architect interview questions and how to answer them

What the partner is listening for

Architecture interviews are usually run by a partner or a senior associate, and most of the time goes on your portfolio. They already think your images look good, or you wouldn't be in the room. What they're testing is whether you can explain why the building looks the way it does, what you personally did, and whether you can hold a design together when a client, a budget or a code pushes back.

Every answer gets stronger when it names the constraint. "The site was 9 metres wide" or "the client cut 15% from the budget at stage 3" tells them you've lived through a real project.

Presenting a project

Pick one or two projects, not ten. Most interviewers would rather go deep on one building you can defend than skim through a whole career. A five-minute shape that works:

Minutes	What you cover
0–1	The brief, the site and the one constraint that shaped everything
1–2	Your role: which stages, which drawings, who you reported to
2–4	Two or three key decisions, each with the reason behind it
4–5	What got built, what changed on site, and what you'd do differently

Say "I" for what you did and "we" for the team. Partners listen closely for this, because a junior who claims the whole scheme is a red flag.

Example opening (made-up details):

"This is a 14-unit housing scheme on a corner site that was only 9 metres deep at one end. I was the project architect from stage 2 through tender. The depth problem drove everything: we went to dual-aspect flats with the stairs on the north side, so every living room got the south light."

If you're presenting in person, practice speaking to the person, not to the screen. Our guide to a job interview presentation covers timing and handling interruptions.

When the client changes the brief

This is the most common behavioural question in architecture. They want to see that you protected the design's core while giving the client what they actually needed.

Example answer (made-up details):

"On a dental clinic, the client asked to add two more treatment rooms after planning approval. Redrawing the whole floor would have meant a new application. I went back through the layout and found we could take the rooms from an oversized staff area and a corridor, without changing the outside. I showed the client two options with the trade-offs, and they picked the one that kept the waiting room's daylight. We filed it as a minor amendment instead of starting over."

The structure: what changed, what was at risk, the options you put forward, and what the client chose.

Codes, planning and budgets

Interviewers ask about these to see whether you treat limits as part of the design or as an obstacle. Name the requirement in general terms (fire escape distances, accessibility, height limits, energy rules) and say how the design responded.

Weak answer	Stronger answer
"We had to follow fire code."	"Travel distance to the exit was too long, so we added a second stair and used it as a feature in the atrium."
"The budget was tight."	"We were 12% over at cost plan. I proposed a simpler facade system and kept the expensive cladding only on the street side."
"Planning was difficult."	"The planners wanted the roofline lower. We dropped one floor-to-ceiling height by 200 mm and kept the unit count."

For budget questions, say what you protected and what you gave up. "We value-engineered it" alone tells them nothing.

Your design philosophy

Avoid abstract statements like "I believe architecture should elevate the human experience." Give one principle and show it in a building.

"I care most about how a building is used on an ordinary day. On the library project I spent a morning watching how people moved through the old building, and that's why the entrance faces the bus stop, not the main road."

Then tie it to the practice. Mention one of their projects and what you noticed in it.

Mistakes to avoid

Narrating every slide. Let the image sit and talk about the decision behind it.
Taking credit for the whole scheme. Be precise about your stages and drawings.
Blaming the client. Every change story should end with what you learned about briefing.
Listing software without a task. "I modelled the facade options in Revit and ran daylight studies" says more than a list of programs.

Speaking about your own work under questioning is a skill you can rehearse. Speaking Coach can play a partner who stops you mid-presentation and asks why.