Architecture Job Interview Tips

A good architecture job interview is not about sounding perfect. It is about showing that your experience, portfolio, communication and practical details match the role.

You need to show how you think, what you have done and why the role makes sense for your next step.

Most practices are trying to answer a few simple questions: can you do the work, can you explain your thinking, will you fit the team and are there any issues around salary, notice, software, location or right to work?

Watch: how to shine in an architecture interview

This related episode is directly useful because it covers how to present yourself, your portfolio and your practical details in interview.

Watch the video

Watch: how to ace architecture interviews online

Many architecture interviews now involve online presentation, quick judgement and portfolio explanation. This related video is useful because it shows how to keep that conversation clear on camera.

Watch the video

Listen: related Architecture Social podcast

The podcast expands on interview preparation, portfolio handling, online interviews and follow-up.

You can also open the Architecture Social podcast page for this episode.

Research the practice properly

Do not stop at the homepage. Look at project type, scale, location, sector, tone, clients, recent news and whether the role matches their current work. One specific observation is better than five generic compliments.

Prepare your portfolio walkthrough

Do not open a portfolio and hope the conversation flows. Choose two or three projects that match the role. For each one, explain the brief, your role, the stage, the tools used and one decision you can defend.

Know your practical details

• Current or expected salary.
• Notice period and availability.
• Location and hybrid preferences.
• Right to work or visa situation if relevant.
• Software confidence with real examples.
• Project stages and responsibilities you can evidence.

Prepare examples, not scripts

You may be asked about teamwork, pressure, mistakes, deadlines, software gaps or difficult feedback. Prepare examples from real projects, but do not memorise a speech. A clear honest example is better than a polished answer that feels detached from reality.

Choose examples that show different strengths: design thinking, technical coordination, software, client communication, planning, detailing, teamwork or leadership.

Questions to ask them

• What projects would this person work on first?
• What stage are those projects at?
• How is the team structured?
• What would success look like after three months?
• What software and workflows does the team use day to day?
• What are the next steps after this interview?

Common mistakes

• Talking through every portfolio page with no edit.
• Not knowing why you applied to that practice.
• Being vague about your role on past projects.
• Looking surprised by salary or notice questions.
• Leaving without understanding the next step.

Architecture Social view

Stephen’s recruiter view is that interviews are where evidence becomes a conversation. You do not need to perform. You need to be clear, prepared and honest about what you have done and what you want next.

Before the interview, check your architecture CV, your portfolio and the Architecture Salary Guide.

Next step

Practise a five minute portfolio walkthrough before the interview. If you want direct preparation, book a Power Hour career coaching session.

For practical next steps, compare the architecture salary guide, browse current architecture jobs, set up architecture job alerts or contact Architecture Social for tailored advice.