An architect interviewing for a data centre project may expect to show a clean industrial building and talk about efficient planning. The team may be listening for something else: whether you understand how architectural decisions interact with cooling, power, security, maintenance and the construction sequence. You do not need to be an electrical engineer. You need to know which questions belong to specialists, which spatial decisions depend on their answers and how you keep those decisions coordinated.
This article is for architects entering the sector from other building types. It is an interview preparation guide, not a design standard. Data-centre requirements vary with the operator, technology, location and reliability objectives. Use the employer’s brief and current specialist guidance for any actual project. In an interview, show how you work across disciplines without borrowing technical authority you do not have.
Start with the operator’s purpose
Ask what the facility is for: enterprise use, colocation, edge capacity or another model. Who owns the equipment requirements and who approves changes? What parts are built now and what parts may be fitted out later? A data centre is not simply a shell around server racks. The operating model affects access, phasing, security, resilience and the boundary between landlord, operator and tenant work.
Do not assume every project aims for the same redundancy or certification. If the interviewer names a particular standard or target, ask what it requires of the architectural package and which consultant leads compliance. The ASHRAE data-centre resources illustrate how much specialist work sits around cooling, energy and equipment environments. Your contribution is to make the building, interfaces and documentation work with that specialist design.
Prepare a short answer to “What would you ask at project start?” Include equipment and service access, security zones, fire strategy, structural loads, space for plant and distribution, phased growth, site constraints and the decision owners. You are not prescribing the answer. You are showing that a façade concept should not be frozen before the equipment and maintenance strategy is understood.
Use one interface story from another sector
You may have never worked on a data centre. Choose a real project where a spatial decision depended on an engineer or operator. A hospital plant room, laboratory fit-out, airport services corridor or complex office retrofit may provide an analogous coordination story. Explain the conflict, the options you tested, the specialist input and the documented decision. Then state what would differ in a mission-critical facility.
For example: “On an occupied office retrofit, the MEP route reduced the available corridor height. I mapped two bulkhead options and coordinated the final position after engineer and client review. In a data centre, I would expect equipment access and resilience requirements to make that interface more critical, so I would seek the operator’s maintenance brief earlier.” This does not claim data-centre expertise. It demonstrates a transferable method.
Bring a drawing or diagram that shows an interface, not only a finished image. The interviewer may ask what happens if a component changes size or a route needs to be separated. Your answer should follow the decision chain: who provides revised criteria, what spaces are affected, which drawings and models change, and who approves the response.
Prepare for five recurring questions
Access: How will large equipment arrive, be replaced and maintained? The architect may need to coordinate doors, routes, structural openings and clearances with specialists. Security: Which people and deliveries may enter each zone, and how are public, staff and equipment routes separated? Plant: Where do cooling and power systems need space, support and external interfaces? Phasing: What can be built or expanded without disrupting live operations? Documentation: How do revisions stay consistent across architecture, structure, MEP and specialist packages?
These are interview prompts, not universal design rules. An employer may use different terms or divide work differently. Ask which interfaces the role will own. The ASHRAE resilient-design framework discusses reliability and the relationship between electrical and mechanical systems. That is a reminder to treat resilience as a system property requiring coordinated decisions, rather than an architectural label added to a presentation.
Avoid repeating acronyms you cannot explain. If you have read about UPS, PUE or redundancy, be ready to say what the term means in broad project terms and who designs or verifies it. “I would confirm the operator’s resilience target with the electrical and mechanical leads before fixing room adjacencies” is a sensible architectural answer. Pretending to specify electrical topology is not.
Show a method for handling late changes
Data-centre programmes can change as equipment and tenant needs develop. In an interview, describe how you would record an assumption and manage a change. Suppose the operator increases equipment density. The team may need to revisit cooling, power, loads, access and programme. Your role is to flag affected architectural spaces and documents, assign questions to the right leads and keep a decision record.
Use a simple issue card: change request, current assumption, affected zones, consultant owners, decision deadline, approved response and drawing revisions. If a model clash appears, show how it becomes a coordinated action rather than a screenshot in a meeting. The firm is assessing whether you can make complex work traceable under pressure.
Do not promise a zero-clash model or claim one person can prevent every late change. Show a review rhythm and escalation point. A junior applicant can describe how they would maintain a log under supervision. A senior applicant should discuss who decides trade-offs when cost, programme and resilience conflict.
Ask questions that reveal the actual job
Discuss energy without promising a single metric
Data-centre projects can create difficult energy, cooling and resilience trade-offs. Ask who sets the performance targets and how the architectural team helps test options such as plant placement, envelope design, heat-rejection space and future expansion. Do not reduce the discussion to one efficiency metric or claim that an attractive material choice will solve an engineering problem. A candidate from another sector can still bring experience in comparing life-cycle implications and coordinating planning constraints.
For an interview case, describe how you would record two alternatives: what each does to site area, maintenance access, structural support, planning appearance and specialist systems. The engineers and operator would establish technical performance. The architect would make the spatial consequences visible and ensure an approved choice appears consistently in the package. This is a useful contribution even when you are still learning the sector’s technical vocabulary.
What part of the facility does the architecture team lead? Is the role on shell and core, internal fit-out, planning, construction administration or repeated prototype delivery? Who is the operator representative? Are specialist vendors involved during design? How are model and drawing interfaces managed? Does the firm have a standard detail library, and who checks when a project departs from it?
Ask whether the practice expects sector experience from day one or is hiring transferable coordination ability. If it expects immediate independent data-centre leadership, a beginner may not fit. If it has senior specialists and needs disciplined package coordination, your existing work may be relevant. The interview should discover that difference.
Also ask about working pattern. Mission-critical projects can have compressed deadlines or site constraints, but “data centre” alone does not tell you the hours. Ask how deadlines are staffed, how travel works and what the team does when operator requirements change late. Evaluate the actual role rather than the sector’s reputation.
Create a one-page interview brief
After the interview, note which interface the team returned to most often. If they repeatedly asked about plant access, your next portfolio revision should make a real access decision easier to see. If they focused on phased delivery, prepare a clearer sequence from a past project. Do not invent new experience to match the questions. Use the questions to surface evidence you already have and to identify a learning gap you can address before the next conversation.
Before the meeting, prepare four boxes: what you know about the firm’s data-centre work from public sources; one verified interface story from your portfolio; three technical questions for the team; and two gaps you intend to learn. If the firm’s project information is confidential, do not guess at details. Use the advertised role and public case studies only.
Practice a two-minute explanation of your story without images, then a five-minute version with one plan or section. The best candidates can show how a design decision crossed disciplines and reached an authorised outcome. A dramatic render may help set context, but the interface story gives the hiring team evidence of how you will work.
You do not have to claim that aesthetics disappear from data-centre architecture. Form, site and community impact still matter. For this interview, earn trust by showing that you know where architecture meets the systems the building exists to support, and how you will coordinate those boundaries.
Browse current architecture jobs on Jobs.archi and compare your next step with our guide to architecture job opportunities.
The post Data Center Architecture Interviews: Explain Interfaces Before Aesthetics first appeared on jobs.archi.