Role guide
Updated 20 August 2026
Architect roles cover design development, technical resolution, coordination, client communication and project delivery. This guide explains the documented interview process for one government technical architect role and helps you prepare relevant examples from your own work, while recognising that building-design practices may use a different format.
The documented three-stage journey applies specifically to a government technical architect role. Interviews for building-design practices may differ, so confirm the format with the employer rather than assuming every stage will apply.
Application review
Review of the submitted application before interview
Depends on the employerThe employer reviews your application. Make relevant experience and achievements easy to find rather than relying on an elaborate CV layout.
Phone interview
Phone interview
Depends on the employerThe phone interview is the second stage. The evidence does not specify its length, participants, questions or assessment criteria.
Face-to-face interview and role play
In-person interview with a technical role-play exercise
Depends on the employerThe face-to-face interview includes a technical role play. The exercise is technical and examines how the candidate interacts with non-technical stakeholders or domain experts.
Government technical architect recruitment
The documented process has three stages: application review, phone interview and a face-to-face interview containing a technical role play. The role play examines interaction with non-technical stakeholders or domain experts.
Choose a small set of projects that lets you discuss the brief, users, design development, technical constraints, planning or building control, sustainability, cost and programme. Be precise about your own responsibility, the people you worked with and what changed because of your input.
Review the tools named in the advert, such as Revit, AutoCAD, Vectorworks or ArchiCAD, but prepare to explain the decisions behind the drawings and models rather than merely listing software. For stakeholder scenarios, practise translating a technical issue into its effect on users, delivery, risk and the next decision.
Architectural work involves turning client briefs, user needs and site constraints into proposals that address function, safety, sustainability and appearance.
Architects may develop concepts into coordinated drawings, specifications and details informed by materials, structure and construction methods.
Architects discuss requirements, present proposals, explain risks and reconcile feedback from clients, users, consultants, authorities and contractors.
Projects depend on coordinated information from engineers, surveyors, planners, contractors and other consultants. Architects may also lead the design programme and responsibility matrix.
Architects work within planning, building control, health and safety, contractual and professional requirements. Their advice and records can have serious consequences for clients and building users.
Depending on their appointment and seniority, architects may manage programmes, resources, fees, budgets, tender information and construction-stage duties while attending to design quality.
Architectural work may require candidates to consider environmental and social effects, compare alternatives and explain sustainability decisions alongside other project constraints.
Use the answer plans as prompts, not scripts. Your examples should sound like you.
Prepare clear accounts of how you develop, test and communicate architectural ideas.
What they want to learn: The interviewer wants to understand how you moved from the brief and context to a proposal, including which decisions were yours.
Evidence to use: Choose a portfolio project for which you can discuss both the design reasoning and an unresolved or revised element.
What they want to learn: The interviewer is testing whether you can assess sketching as one method of architectural enquiry and communication alongside models, CAD and other media.
Evidence to use: Recall a design problem that became clearer through a sketch, model, digital study or comparison between media.
What they want to learn: In a graduate architecture interview, this question assesses teamwork and how you handled specialist input within an architectural project.
Evidence to use: Choose an example involving a specific exchange with an engineer, surveyor, planner, contractor or specialist consultant.
What they want to learn: The interviewer wants to see whether your skills match the role and whether you can support them with concrete examples.
Evidence to use: Pick strengths supported by visible work, feedback, a solved problem or a measurable project result.
Prepare to show how you approach coordinated, compliant and buildable project information.
What they want to learn: The interviewer wants evidence that you can diagnose a problem, consult the right people and reach a workable solution.
Evidence to use: Use an example with a drawing, detail, specification or site issue that you personally helped resolve.
What they want to learn: The interviewer wants practical evidence of how BIM affected information, coordination or delivery on a real project.
Evidence to use: Choose a project where the model changed an action, exposed a clash or improved coordination.
What they want to learn: The interviewer is checking whether you understand how a responsibility matrix can clarify design ownership, gaps and interfaces between contributors.
Evidence to use: Recall a project where unclear ownership caused, or could have caused, a coordination problem.
What they want to learn: The interviewer wants you to explain site observation, records and communication within the limits of the architect's appointment.
Evidence to use: Prepare a site example involving an observed defect, incomplete work or departure from the design information.
Connect planning, contractual and safety knowledge to work you have undertaken.
What they want to learn: The interviewer wants a clear account of a planning application, your involvement and the other outcomes relevant to that case.
Evidence to use: Use a planning application you worked on and review its decision, conditions, correspondence and any revisions.
What they want to learn: The interviewer wants to know how tender information was prepared, issued, queried, assessed and reported on your project.
Evidence to use: Choose a tender where you can identify the documents, participants, decisions and one practical lesson.
What they want to learn: The interviewer is asking you to examine the wording and professional risk attached to these obligations without straying into unsupported legal advice.
Evidence to use: Recall an appointment review, specification discussion or project risk where the wording of an obligation mattered.
What they want to learn: The interviewer wants to know how you would respond to a safety concern while recognising urgency, the appropriate escalation route and the limits of your authority.
Evidence to use: Choose a real safety concern you raised, or prepare a careful scenario showing who you would contact and why.
Prepare to discuss environmental choices, consultation, competing work and commercial exposure through specific projects.
What they want to learn: In a graduate architecture interview, this question assesses critical thinking about environmental impact and sustainable development, calling for a reasoned position rather than a slogan.
Evidence to use: Choose a project where you assessed retention, adaptation, material use or operational performance.
What they want to learn: The interviewer wants you to describe the consultation, who took part, the response and whether it influenced the project.
Evidence to use: Use a consultation exercise where you can describe the participants, feedback and project response, whether or not the design changed.
What they want to learn: The interviewer is assessing how you manage competing priorities, meet deadlines and protect the quality of completed work.
Evidence to use: Choose a week or project stage with genuinely competing deadlines and identify the trade-off you made.
What they want to learn: The interviewer wants to understand your actual exposure to fees, time and resources; you do not need to claim access to commercial information you have not seen.
Evidence to use: Prepare an example involving timesheets, a fee proposal, resource planning, additional work or stage performance.
At the face-to-face interview, the technical role play examines how you interact with non-technical stakeholders or domain experts.
Architect appointments vary. This reveals whether the post centres on concept design, technical delivery, construction-stage work or a mixture.
The answer shows how the employer handles design quality, accountability and changes during delivery.
It helps you judge how coordination works in practice and whether responsibilities between disciplines are clear.
This clarifies the communication and relationship-management demands of the post.
You can assess the technical learning curve and whether your current software experience transfers.
The response reveals the firm's working priorities and how much influence architects have over trade-offs.
This often produces a more concrete picture of expected judgement, behaviours and ownership than the job description.
Talking about a project's finished appearance without explaining the brief, users, constraints or technical reasoning.
Trace the decisions that produced the design and show how you tested feasibility, function, safety and environmental performance.
Claiming credit for a team project without defining your own work.
State the project's team structure, your remit, the decisions you owned and where another consultant led.
Treating regulations, planning or contractual duties as details for somebody else.
Prepare examples showing how you checked requirements, sought suitable advice and recorded decisions within your level of responsibility.
Giving a design answer before clarifying the client's priorities, budget, programme and risks.
Explain what you would establish first, then compare options against those constraints.
Describing software proficiency as a substitute for architectural judgement.
Connect CAD or BIM use to a result, such as testing a proposal, coordinating information or resolving a construction issue.
Offering polished generalities about organisation while avoiding a real deadline conflict.
Use one project with competing tasks, explain how you ranked them and show how you communicated any effect on programme or quality.
Send a short thank-you message after the interview. Refer to one specific discussion and, if useful, clarify a point you could not answer fully.
Review your notes while the conversation is fresh. Record the projects, responsibilities and working arrangements described by the employer, then compare them with the role you applied for. Keep contractual questions for the appropriate post-interview or offer discussion if the interview panel has said it cannot cover them.
From guide to application
Use cvlift to tailor your CV to the role and bring the most relevant experience forward. Then use this guide to practise the examples behind it.
