The Interview

The interview is won mostly before you enter the room. Preparation is what converts nerves into confidence, because confidence is largely just knowing you are ready. Three kinds of preparation matter. First, know the studio: their recent projects, their sensibility, who works there, what they seem to care about. You should be able to say, specifically, why you want to work here and not at any of a dozen similar places - and to connect their work to yours. Generic enthusiasm reads as having applied everywhere; specific knowledge reads as genuine interest, and interest is magnetic.

Second, know your own portfolio cold. It sounds obvious, yet candidates freeze when asked a simple question about their own project. For each piece you might discuss, be ready to say in a sentence what it is, what problem it solved, what your idea was, what you actually did, and what you would change now. Rehearse aloud - talking through work is a different skill from making it, and it improves fast with practice. Ask a friend to play interviewer, or record yourself and listen back once, wincing but learning. You are not memorising a script; you are getting comfortable in the material.

Third, handle the logistics so they never distract you. Know the format - a portfolio walk-through, a panel, a short design task, a casual chat - and prepare accordingly. Bring what you need and test it: a charged laptop with the PDF open offline, a small printed leave-behind, a physical model if you have a good one, water, and a couple of questions written down. Arrive early. Plan for the video-call version too - check your camera, light, sound and background, and have the file ready to share. The point of all this is not to script yourself into a robot. It is to remove every avoidable worry so your attention is free for the actual conversation, which is where you win or lose.

The heart of most design interviews is walking through your work, and it is a skill you can learn. The single biggest mistake is narrating every slide in order - 'and then I did this, and then this' - a flat travelogue that buries your thinking and bores your reader. Instead, lead with the idea. For each project, open with one clear line of what it is, then the problem or brief, then your idea and the move you made, then the result and what you learned. That four-beat shape keeps you crisp and lets the interviewer follow your logic instead of your chronology.

Be rigorously honest about your role, especially with team and office work. Say clearly what you did - 'I led the facade study and produced the working drawings; the concept was the team's' - and credit others generously. Interviewers have seen a thousand portfolios and can smell an inflated claim; honest, specific credit reads as maturity and makes your genuine contribution more believable, not less. The same goes for AI-assisted work: be straightforward about what you used a tool for. Nobody expects you to have done everything alone; they want to know you understand what you did and can be trusted with the truth.

Keep it a conversation, not a monologue. Watch their cues - if they lean in and ask about a detail, follow them there; if they are glazing over, move on. Aim for roughly two minutes per project unless invited deeper, and stop talking when you have made your point. Expect the classic prompts and prepare for them without over-rehearsing: 'talk me through this one', 'what was the hardest part', and especially 'what would you change?' - which is not a trap but an invitation to show self-awareness. A strong answer names a real weakness and what you learned:

If I did it again I would test the section earlier - I
committed to the roof geometry before I understood the
drainage, and paid for it in the final week. It taught me
to resolve the section and the plan together.

That kind of answer - specific, honest, reflective - does more for you than any polished boast ever could.

An interview runs in both directions, and the questions you ask matter as much as the answers you give. First, prepare for what they will ask you. Beyond your projects, expect versions of: why this studio, tell me about a time you worked in a team or handled a setback, what are you weak at, where do you want to grow, and sometimes the software and skills you know. Answer honestly and briefly, and bring every answer back to something concrete you have actually done rather than adjectives about yourself. For the weakness question, name a real one and the steps you are taking - self-awareness beats a humblebrag every time.

Then ask well, because your questions reveal what you value. Good questions are about the work and the growth: What does a first year here actually look like? Who would I learn from? How do projects move from concept to site? What kind of person thrives in this studio? Asking these signals that you are serious about the craft and the fit. It is completely fine - important, even - to understand pay, hours and leave too, but let the conversation earn its way there; opening with a question about annual leave before you have shown any interest in the work sends exactly the wrong signal. Save the package questions for later in the process, or for the next lesson's territory.

Avoid two traps. Do not ask questions whose answers are plainly on their website - it shows you did not look. And do not say 'no, I think you covered everything' when invited to ask; having nothing to ask reads as indifference. Keep two or three real questions in your pocket precisely for that moment, and let one of them be genuinely curious about their work. The best interviews stop feeling like an examination and start feeling like two people who both care about the work figuring out whether they should make some of it together.

Nerves are not a flaw to eliminate; they are a sign you care, and everyone on the other side of the table has felt them. The goal is not to be fearless but to be prepared enough that the nerves stay in the background. A few practical anchors help: breathe and slow down - most of us speak too fast when anxious, so it is fine to pause, think, and even say 'let me take a second on that'. Sit up, make normal eye contact, and treat it as a conversation between colleagues rather than an interrogation you must survive.

The most freeing move in any interview is honesty over bluffing. If you are asked something you do not know - a detail, a piece of software, a code - do not invent. Say so, and show how you would find out: 'I have not used that tool, but I picked up Rhino in a week and I would do the same here.' Experienced interviewers respect a candid 'I do not know' far more than a confident wrong answer, because it tells them you can be trusted on a real project, where bluffing causes real damage. Your job is not to be perfect; it is to be capable, honest and easy to work with.

Remember that the interview is a two-way fit. You are also deciding whether you want to spend your days here, learning from these people, on this kind of work. That reframing quietly steadies you: you are not a supplicant hoping to be chosen, you are a professional assessing a match. Notice how they treat you and each other; it tells you a great deal about the years ahead. Finally, close well and follow up. Thank them in the room, and send a short, warm thank-you note within a day - a couple of sincere lines referencing something you discussed. It is easy, most people skip it, and it leaves the last impression working quietly in your favour.