Redundancy is common in architecture, especially when project pipelines shift, funding pauses or practices restructure. In an interview, the aim is not to apologise for it. The aim is to explain it clearly and move the conversation back to what you can do.
A strong answer is calm, short and factual. It gives enough context, avoids blame and shows that you are ready for the next role.
Watch: handle the interview with confidence
This Architecture Social video is useful here because redundancy questions are often won or lost on tone, structure and confidence, not a perfect script.
Related audio: finding jobs and securing interviews
This related episode adds wider context on rebuilding momentum, finding opportunities and turning interviews into practical next steps.
Use a simple three-part answer
You do not need a dramatic explanation. Use a structure that makes the situation easy to understand and then redirects the interview towards your strengths.
- Context: explain what changed in the practice or project pipeline.
- Role: clarify that the redundancy was about workload or structure, not conduct.
- Next step: connect your experience to the role you are interviewing for.
Example wording
A practical answer could be: my previous practice had a slowdown in a particular sector, and my role was made redundant as part of a wider restructure. Since then, I have been focusing on roles where I can use my project experience, software skills and client-facing work more fully.
That answer is not defensive. It gives the interviewer context and then brings the discussion back to fit.
What not to say
- Do not blame individuals at your last practice.
- Do not overshare private commercial details.
- Do not make the redundancy sound like the whole story of your career.
- Do not apologise for something outside your control.
- Do not avoid the topic so heavily that it becomes awkward.
Prepare the evidence underneath
The best way to make the redundancy conversation easier is to have strong evidence ready. Your CV, portfolio and interview examples should show what you contributed before the role ended.
Use recent project examples, explain your responsibility honestly and be ready to talk about what you learned from the period after redundancy.
Common mistakes
- Giving a long answer that invites more questions than it solves.
- Sounding bitter about the previous employer.
- Letting redundancy replace your career story.
- Failing to prepare a short explanation before the interview.
- Not linking the answer back to the role in front of you.
Architecture Social view
Stephen’s recruiter view is that most hiring managers understand redundancy. What they want to see is composure, evidence and a candidate who can talk about difficult career moments like a professional.
Next step
Use this with the interview questions guide, the how to resign guide, live architecture jobs and the career advice call.
Add a comment