Architecture Interview Questions: 20 Questions & How to Answer Them

You've landed the interview. Your portfolio got you in the door, but now you need to prove you can think on your feet, articulate design decisions, and demonstrate you understand what actually happens on a construction site.

Architecture interviews aren't just about showing pretty renderings. They're about revealing how you solve problems, collaborate with engineers, and handle the inevitable chaos of real projects. The firms that skip the softball questions and ask tough ones? Those are usually the ones worth working for.

Here are 20 questions you'll likely face, what the interviewer really wants to know, and how to answer without sounding like you memorized a textbook.

Portfolio & Project Discussion Questions

1. "Walk me through your favorite project in your portfolio."

What they're actually asking: Can you tell a coherent story? Do you understand why you made certain decisions, or did someone else drive the design?

How to answer: Pick a project where you had genuine ownership. Structure your answer chronologically: brief, constraints, concept development, key design decisions, challenges, outcome. Spend most of your time on the "why" behind decisions, not describing what the interviewer can already see.

Example: "This mixed-use project had a tight urban site with strict setback requirements. We explored three massing options, but the sawtooth facade you see here was driven by daylighting analysis -- the south-facing units needed shading, while north needed maximum glazing. The cantilever wasn't just aesthetic; it created covered outdoor space the planning department required without eating into our ground floor retail area."

2. "What was the biggest challenge in this project, and how did you solve it?"

What they're actually asking: Can you handle adversity? Do you take responsibility or blame others?

How to answer: Choose a real technical or coordination challenge, not "the client changed their mind a lot." Explain the constraint, your analysis, options you considered, and why you chose your solution. If it involved collaboration, say so.

Avoid: Blaming consultants, contractors, or clients. Even if they made your life hell, the interview isn't the place to air grievances.

3. "How did you incorporate sustainability into this design?"

What they're actually asking: Do you actually understand environmental design, or do you just add solar panels and call it green?

How to answer: Be specific. Passive strategies first (orientation, shading, natural ventilation, thermal mass), then active systems. Mention standards if relevant (LEED, Passivhaus, WELL). If the project wasn't particularly sustainable, be honest and explain what you'd do differently now.

Example: "The building orientation minimizes east-west glazing to reduce heat gain. We used triple glazing with low-e coatings on the north facade to maximize daylight without thermal loss. The green roof isn't just for aesthetics -- it reduces stormwater runoff by 60% and provides additional insulation."

4. "If you could redesign one aspect of this project, what would it be?"

What they're actually asking: Are you self-critical? Can you learn from experience?

How to answer: Pick something meaningful but not catastrophic. Show you've thought about it since the project ended. This is a chance to demonstrate growth.

Example: "The circulation on the third floor creates a pinch point near the elevator lobby. If I could redo it, I'd swap the meeting room and break room locations to distribute foot traffic more evenly. It's functional as-built, but the flow could be smoother."

Technical Knowledge Questions

5. "Explain the difference between a shear wall and a load-bearing wall."

What they're actually asking: Do you understand structural systems beyond aesthetic implications?

How to answer: A load-bearing wall carries vertical loads (gravity) from above. A shear wall resists lateral loads (wind, seismic) by acting as a vertical cantilever. A wall can be both. Then relate it to design: "This matters because shear wall placement affects floor plan flexibility and where you can put large openings."

6. "What's your approach to designing for accessibility?"

What they're actually asking: Do you see accessibility as a checklist or an integral design consideration?

How to answer: Start with universal design principles, then get specific. Mention code requirements but frame them as minimums, not targets. If you have experience with specific needs (autism-friendly environments, aging-in-place design), mention it.

Example: "I start with circulation -- ensuring level changes are minimized and ramps integrate naturally rather than feeling tacked on. Door widths, turning radii, and counter heights come next. But good accessible design benefits everyone: curbless showers, lever handles, good lighting contrast. I've found that when you design for the most restrictive case first, you usually create a better space for all users."

7. "How do you coordinate with MEP engineers?"

What they're actually asking: Will you be a pain to work with, or do you understand that architecture is a team sport?

How to answer: Emphasize early coordination. Mention specific coordination points: structural depth for ductwork, riser locations, equipment room sizing, ceiling heights.

Example: "I try to get MEP involved during schematic design, not just CDs. We'll do a coordination meeting to establish ceiling plenum depths and discuss routing strategies for major systems. I've learned to leave space for things I don't see on my drawings -- knowing a mechanical shaft needs X square feet is different from understanding it needs clear vertical runs without offsets."

8. "What building codes are you most familiar with?"

What they're actually asking: Have you actually worked on buildable projects, or just academic exercises?

How to answer: Name the codes you've used (IBC, local amendments, accessibility codes). Mention specific sections you've dealt with: occupancy classifications, fire separation, egress calculations, height and area limitations.

Don't panic if: You don't know every code inside out. No one does. What matters is showing you know how to research and apply them.

Design Process Questions

9. "Describe your design process from concept to construction documents."

What they're actually asking: Do you understand the full arc of a project, or just the sexy early phases?

How to answer: Hit the major phases with specific deliverables at each stage.

Add: "The transitions between phases are critical. A good SD-to-DD handoff can save weeks of rework later."

10. "How do you handle design feedback you disagree with?"

What they're actually asking: Are you a defensive prima donna or a collaborative professional?

How to answer: Acknowledge that architecture is subjective, but good design has rationale. Explain that you listen first, then either adjust based on new information or explain your reasoning with evidence.

Example: "I had a client who wanted to remove clerestory windows I'd added for daylighting. Instead of dismissing it, I asked why -- turned out they were worried about heat gain. I showed them the energy model demonstrating the windows actually reduced cooling loads due to reducing artificial lighting. They kept them. But I've also had feedback that made me realize I'd prioritized aesthetics over function, and I adjusted."

11. "What role does hand sketching play in your process?"

What they're actually asking: Can you think spatially and communicate quickly, or are you dependent on software?

How to answer: Be honest. If you sketch regularly, explain when and why. If you're more digital-native, that's fine too -- but acknowledge the value of quick visual communication.

Example: "I sketch during client meetings and early concept development. It's faster than Revit for exploring options in real-time. But once I'm refining proportions or testing daylighting, I move to digital tools. I've found trace paper over printed plans is still the fastest way to work through plan iterations."

Behavioral & Situational Questions

12. "Tell me about a time you made a mistake on a project. What happened?"

What they're actually asking: Do you own your errors, and more importantly, do you learn from them?

How to answer: Pick a real mistake (not a humble brag). Explain what you missed, how it was caught, what the impact was, and what you changed afterward.

Example: "I spec'd a curtain wall detail without confirming the structural engineer had accounted for the lateral load transfer. It got caught during shop drawing review, but it delayed fabrication by two weeks and required a change order for additional steel. Now I front-load structural coordination during DD and use a coordination checklist before issuing CDs."

13. "Describe a conflict you had with a team member and how you resolved it."

What they're actually asking: Can you handle interpersonal friction professionally?

How to answer: Choose a professional disagreement, not a personality clash. Focus on the resolution and what you learned.

Avoid: Anything that makes you sound petty, vindictive, or unable to compromise.

14. "How do you prioritize tasks when you have multiple deadlines?"

What they're actually asking: Will you melt down during a deadline crunch, or can you triage effectively?

How to answer: Mention a system (task lists, project management tools, time blocking). Acknowledge that architecture involves constant reprioritization based on consultant turnaround, RFIs, and client urgency.

Example: "I keep a running task list sorted by deadline and dependency. If I'm waiting on structural calcs to finalize a detail, I'll shift to another task rather than blocking myself. I also communicate early when I see deadline conflicts -- better to reset expectations early than miss a deadline silently."

15. "Why do you want to work here specifically?"

What they're actually asking: Did you do any research, or are you applying everywhere?

How to answer: Reference specific projects, design philosophy, or firm culture. If they have a strong sustainability practice or specialize in a building type you're interested in, say so.

What not to say: "I need a job" or generic praise that could apply to any firm. Also avoid "I love your website" -- it sounds shallow.

Software & Technical Skills Questions

16. "What software are you most proficient in?"

What they're actually asking: Will you need three months of training, or can you contribute immediately?

How to answer: List your primary tools and your proficiency level honestly. If the job posting mentioned specific software you don't know, acknowledge it and mention how quickly you've picked up tools in the past.

Example: "I'm most efficient in Revit for production work and Rhino + Grasshopper for complex geometry and early massing studies. I use Enscape for real-time visualization and know enough Photoshop for presentation graphics. I haven't used [their firm's software X] professionally, but I've learned new tools quickly -- I picked up Grasshopper on a tight deadline and was productive within a week."

17. "Have you worked on any BIM projects? What was your role?"

What they're actually asking: Do you understand BIM workflows, or do you just use Revit as a drafting tool?

How to answer: Explain your involvement in BIM execution plans, coordination meetings, clash detection, or model management. If you haven't, be honest but express willingness to learn.

Example: "I was the BIM coordinator on a 15,000 SF office renovation. I set up the Revit template, managed worksharing, and ran weekly Navisworks clash detection sessions with MEP. The biggest challenge was maintaining model discipline -- making sure everyone used the correct worksets and didn't model outside their scope."

Industry Awareness Questions

18. "What trends in architecture are you most excited about?"

What they're actually asking: Do you stay current, or did your knowledge freeze at graduation?

How to answer: Pick one or two genuine interests. Mass timber, adaptive reuse, computational design, resilient design, affordable housing innovations -- whatever you actually follow. Explain why it matters, not just that it's trendy.

Example: "I'm really interested in adaptive reuse, particularly office-to-residential conversions. The financial models are finally starting to work in some markets, and it's a more sustainable approach than demolition. The design challenges are fascinating -- you're working with existing floor plates and core locations that weren't designed for residential unit layouts."

19. "How do you stay updated on industry developments?"

What they're actually asking: Are you intellectually curious, or are you coasting?

How to answer: Mention specific sources: publications (Architect Magazine, Dezeen, ArchDaily), podcasts, conferences, local AIA events, continuing education.

Be honest: If you don't have time for much beyond work, say you follow a few key sources and browse architecture jobs on ArchGee to see what skills firms are prioritizing.

20. "Where do you see yourself in five years?"

What they're actually asking: Are you going to leave in 18 months, and do you have realistic career expectations?

How to answer: Show ambition but not entitlement. Mention skills you want to develop, project types you want to experience, or licensure goals.

Example: "I want to be leading smaller projects independently and starting my ARE exams. Long-term, I'm interested in [specific building type or expertise area]. I'm not in a rush to open my own firm -- I want to build a strong technical foundation first."

How to Prepare for Your Architecture Interview

Review your portfolio ruthlessly. You should be able to explain every decision in every project. If you can't remember why you did something, cut that project or refresh your memory.

Research the firm. Look at their recent projects, read interviews with principals, check if they've won any awards. Have specific questions ready about their work.

Practice talking about your work. Out loud. To another person if possible. You'll sound less rehearsed if you've actually rehearsed.

Prepare questions to ask them. Mentorship structure, typical project types, software workflows, project team sizes, professional development support. Asking nothing suggests you don't care.

Bring physical materials if possible. A small portfolio, a sketch model, detail drawings you're proud of. Digital is fine, but tangible work makes an impression.

Know your gaps. If you're light on CA experience or haven't used their primary software, acknowledge it directly and explain how you'll get up to speed.

What Happens After the Interview

Most firms take 1-3 weeks to decide. If you haven't heard back in two weeks, a polite follow-up email is fine. If you get an offer, it's acceptable to ask for a few days to consider it (but not weeks).

If you don't get the job, you can ask for feedback. Most firms won't give detailed critiques, but some will, and it's valuable information for your next interview.

And if you're still searching, check out architecture positions across the US and UK opportunities on ArchGee -- we focus specifically on built-environment roles, so you're not sifting through software architect jobs.

Frequently Asked Questions

Should I bring a printed portfolio or just show a digital version?

Bring both if possible. A small printed portfolio (8.5x11 or 11x17) shows preparation and gives interviewers something to reference during the conversation. But also have a digital backup in case they want to see details on a larger screen or if you're interviewing remotely.

How long should my answers be?

Aim for 1-2 minutes for most questions. Longer for portfolio walkthroughs (3-4 minutes per project). If you see eyes glazing over, wrap it up. It's better to give a concise answer and let them ask follow-up questions than to ramble.

What if I don't know the answer to a technical question?

Say "I don't know, but here's how I'd find out" or "I haven't encountered that yet, but based on X principle, I'd approach it like this." Honesty is better than bullshitting. Junior candidates aren't expected to know everything; you're expected to know how to learn.

Is it okay to say I want to eventually start my own firm?

Depends on the context. If you're interviewing at a 5-person firm where the principal is 40 and planning to practice for 30 more years, probably skip it. If you're at a large firm where people regularly spin off after 10 years, it's fine. Frame it as a long-term ambition, not a 2-year plan.

How technical should I get when explaining projects?

Match the interviewer's level. If you're talking to a licensed architect, you can discuss wall assemblies and thermal bridging. If it's an HR screening call, stick to big-picture concepts. Read the room and adjust.