Most architecture interviews are not designed to catch you out. They are trying to answer a few practical questions: can you do the work, can you explain your thinking, will you fit into the team, and are there any obvious issues around salary, notice, software or availability?
The best candidates do not memorise perfect answers. They prepare clear examples, know their portfolio, and can explain what they actually did on a project.
Watch: practical advice from Architecture Social
What practices are really checking
An architecture interview is usually part technical, part practical and part human. The practice wants to understand whether your experience matches the role and whether working with you would feel straightforward.
- Level: are you applying at the right seniority?
- Evidence: can you explain your CV and portfolio clearly?
- Role fit: do your project types, stages and software match the vacancy?
- Communication: can you talk through work without overclaiming?
- Practical details: salary, notice, location, right to work and availability.
- Motivation: do you understand why this practice and this role?
Questions you should expect
Tell me about yourself
Keep this short. Explain your level, your current or recent experience, and what you are looking for next. Do not retell your whole life story. Give the interviewer enough context to understand the rest of the conversation.
Talk me through your portfolio
Do not start at page one and hope for the best. Choose two or three projects that fit the role. For each one, explain the brief, your role, the stage, the tools used and one decision you can defend.
A better answer sounds like: I chose this project because it is closest to the kind of work your studio does. My role focused on concept options, model development and preparing the presentation pack. The pages I would point you to are the section, massing studies and final elevation.
What was your role on this project?
This is where vague portfolio language falls apart. Be honest and specific. If it was a university project, say that. If it was practice work, explain the stage and what you personally handled.
Why do you want to work here?
Avoid generic praise. Mention a real project, sector, scale, location, design approach or team structure. One specific reason is better than a long answer that could apply to any practice.
What are your salary expectations?
Be prepared. Know the market, your level and the role. You do not need to negotiate aggressively in the first answer, but you should not look surprised by the question.
Use the Architecture Salary Guide before the interview so your answer is grounded in the UK market.
Portfolio preparation
Bring a small, controlled set of work. For in-person interviews, printed A3 or A4 pages can still work well. For online interviews, have the PDF ready, tested and easy to navigate.
Your portfolio should not rely on you apologising for missing pages. If a project is confidential, prepare a clean explanation and only show what you are allowed to show.
Questions to ask the practice
- What projects would this person be working on first?
- What stage are those projects at?
- How is the team structured?
- What software and workflows are used day to day?
- What would success look like in the first three months?
- What are the next steps after this interview?
Follow up after the interview
A short follow-up is useful. Thank them for their time, mention one specific thing you discussed, and confirm that you are still interested. Do not send a desperate essay.
If a recruiter is managing the process, follow up through them. If you applied directly and the practice gave you a contact, a short direct note is fine.
Architecture Social view
Stephen Drew is the founder of Architecture Social, a recruiter and industry voice with a Part II background. His view is that the interview is where evidence becomes a conversation. You do not need to sound polished. You need to sound clear, honest and prepared.
If you can explain your role, your project decisions and your practical details without drifting, you are already ahead of many candidates.
Listen: related Architecture Social podcast
This episode expands on interview preparation, portfolio handling, salary conversations, online interviews and follow-up.
You can also open the Architecture Social podcast page for this episode.
Common questions
Should I bring a printed portfolio?
If the interview is in person, yes, a small printed set can help. It shows preparation and gives the conversation something physical to centre on. Bring a tablet or laptop as backup.
How should I answer if I do not know something?
Be honest. Explain what you do know, where your experience stops and how you would approach learning or solving the issue. Overclaiming is worse than a clear gap.
Should I mention other interviews?
You can mention that you are active in the market if asked. Keep it professional. Do not use it as a threat or try to create fake urgency.
When should I follow up after an architecture interview?
A short thank-you note within 24 hours is fine. If there is no update after the agreed timeline, follow up politely once. Keep it simple.
Next step
Before applying, make sure your architecture CV and sample portfolio support the answers you plan to give. You can also browse live roles on the Architecture Social jobs board or book a Power Hour career coaching session for direct interview preparation.
Add a comment