Architect Interview Questions

Recruiters typically want to see how you think, not just what you designed. For each selected project, prepare a clear structure: brief and context, constraints (site, planning, access, utilities), your design rationale, and quantified outcomes. Use your portfolio to point to specific evidence—such as design development drawings, a façade section strategy, or a model screenshot from Revit or Dynamo that demonstrates coordination. Where possible, connect your choices to KPIs like BREEAM target performance, cost-plan alignment, programme milestones, or measurable carbon reduction assumptions. Bring either printed A3 sheets or a tablet and be ready to talk for 5–8 minutes per project with pace and clarity.

In interview settings, it helps to reference the relevant RIBA stage you reached and what “good” looked like at that stage. For example, at RIBA Stage 3 you should be able to explain how you matured design options into coordinated drawings and how you confirmed compliance assumptions with consultants. If BIM is part of the role, reference your BIM Execution Plan and the federation process—who owned which model elements and what exchange formats you used (such as IFC). Finally, highlight your personal contribution, including approvals you led, risks you mitigated, and decisions you escalated—because panels often test whether you can operate as the design lead, not just a modeller.

Architect panels frequently test whether you understand BIM Execution Plans as a process for information—not a file format. Show that you can define LOD/LOI expectations by RIBA stage, maintain a shared coordinate system, and manage worksets and naming conventions so models stay usable across disciplines. Mention the exact workflows you used for coordination, such as federated model reviews, Navisworks clash detection, and consistent IFC exchanges with structural and MEP teams. If you use Revit, talk concretely about parameter sets, model health checks (e.g., missing parameters, duplicates, or broken references), and how you prevent “model drift” between design iterations. Strong candidates also talk about information quality metrics—like reducing clash counts by a set percentage or lowering RFIs after issue.

When describing your BIM approach, connect it to outcomes that matter on site. For example, you can say you scheduled clash detection gateways to protect submission deadlines, and you used an issue log linked to revision tracking to reduce ambiguity. If your role included data-rich deliverables, reference structured information outputs where relevant (e.g., COBie-style information requirements or schedule accuracy targets). You can also mention how you trained team members on authoring standards and how you ran sanity checks before issuing drawings to avoid avoidable rework. The best answers show you can coordinate people, models, and information at the same time, using repeatable quality control rather than improvisation.

Architects are often judged on whether they can integrate compliance into design without creating last-minute emergencies. Prepare to explain how you approach statutory compliance: planning constraints, Building Regulations, accessibility expectations, and CDM awareness around risk management. Use a practical tool mindset—such as keeping a compliance matrix that links requirements to drawings, specifications, and consultant calculations. Reference real coordination points: fire strategy sign-off, structural load paths and details, MEP routing constraints, and façade performance assumptions. When you describe conflicts, show how you decide quickly, document trade-offs, and communicate implications to clients in a measurable way (cost, programme, carbon, or operational performance).

Stakeholder alignment is equally important. Interviewers will look for evidence you can chair design coordination sessions, handle conflicting consultant advice, and escalate risks appropriately. Talk about how you schedule reviews, run design freeze points, and capture decisions so the team knows what has been agreed. If you use project management tools like MS Project, Asta Powerproject, or even a structured stage-gate tracker, mention it as part of how you protect critical path activities. Finally, connect compliance and risk to outcomes: fewer RFIs, cleaner submissions, smoother approvals, and a robust audit trail. Strong candidates treat compliance as a design discipline that supports confidence, not as paperwork done at the end.

Panels often probe how you evaluate options when trade-offs are unavoidable—especially between aesthetics, sustainability, and construction practicality. Build your answer around how you compare alternatives using clear criteria and evidence, rather than intuition alone. Mention how you work with QS colleagues on early cost plan updates, how you coordinate sustainability assumptions with the consultant, and how you validate targets such as BREEAM ratings or embodied carbon reduction strategies. For buildability, highlight detail-level questions you ask early: structural grids, tolerances, access for maintenance, service penetrations, and procurement lead times. Where relevant, talk about using calculation tools and design support packages (alongside consultant outputs) to confirm energy and performance assumptions.

A high-quality approach includes knowing when to involve others and when to make the call. Describe how you set design thresholds—what must be confirmed before you lock a direction, such as façade interface details, fire-stopping strategies, or structural connection assumptions. If you used Revit for option comparisons, reference specific outputs like updated massing envelopes, room schedules, or parameter-based quantities. Also mention how you communicate decisions: concise decision notes, annotated drawings, and a linked issue log that shows what changed and why. The goal is to show that your design leadership improves outcomes across the project lifecycle—from feasibility to technical design and into construction issue.