An architectural designer interview is mostly a conversation about your portfolio, with a few pointed questions about how you'd handle a real project. The people across the table want to know two things: can you design, and can you produce a set that a contractor can build from. Prepare for both, because most candidates only prepare for the first.
| The question | What they want to know | Your angle |
|---|---|---|
| Walk me through one project in your portfolio from start to finish. | It's the whole interview in one question. They want to hear how you think, what you owned, and whether you understand how a design becomes a building. | Pick a built or permitted project if you have one, not your flashiest studio piece |
| Show me a wall section you drew and talk me through it. | A wall section proves you understand assemblies, water, air and heat, not just form. It's the fastest way to tell a designer who can document from one who can't. | Trace the layers from outside to inside and name each one |
| How do you set up a Revit project so a team can work in it without stepping on each other? | Messy models cost firms real hours. They want to know you won't be the person who breaks the central file the week of a deadline. | Talk about worksharing, worksets, and syncing often with comments |
| A plan checker sends back comments saying your exit widths don't work. What do you do? | Plan check responses are core designer work. They're testing whether you know the code, and whether you'll fix the drawing or argue with the city. | Read the exact code section they cited and check it against the occupancy and occupant load |
| The structural engineer's beam is deeper than the ceiling you drew. How do you handle it? | Coordination clashes happen on every job. They want to see whether you solve them early and calmly with consultants or let them reach the site. | Flag it as soon as you see it in the linked model or overlay |
| Tell me about a time a client changed their mind late in the design. | Late changes are the most common source of stress in this job. They want to hear how you protect the schedule and the design without being rude to the client. | Describe the change and when it came in |
| How do you check a set before it goes out? | Quality control separates a designer they can trust from one who needs a babysitter. Errors in a set turn into change orders. | Describe a real checklist or process you've used |
| What software do you use for design, and what do you use for documentation? | Firms have tool habits. They're checking whether you'll fit their workflow and whether you understand why different tools do different jobs. | Name what you use for early massing, like SketchUp or Rhino, and why |
You narrate the renderings slide by slide and can't say what you'd do differently.
Pick a built or permitted project if you have one, not your flashiest studio piece. Start with the constraint: the site, the budget, the code issue or the client ask. Say plainly which parts you did and which parts your team did. Show one drawing where a decision changed, and why it changed. End with how it turned out on site or at permit.
You can't explain why a layer is where it is, or you don't have a section in your portfolio at all.
Trace the layers from outside to inside and name each one. Point to where water and air are stopped and how the barriers connect at the window or roof. Mention the fire rating or energy code requirement that drove a choice. Say what you'd check with the manufacturer or the envelope consultant.
HeroApply applies to Architectural Designer jobs that match you, every day. 50 jobs are open today.