Questions to Ask in an Architecture Interview
For graduates and working architects interviewing for a job at an architecture firm, these are the questions to put to the people across the table. They follow the order the conversation usually takes: the work you would do, the team, software and standards, hours and deadlines, mentoring and licensure, then pay and the offer. The note under each one says what a reassuring or a worrying answer sounds like, or what to ask next.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The work
What types of projects would I be working on in my first year?
Why ask it
A firm's website shows its best finished buildings, while this answer shows what is in the studio now. A good one names real jobs and their sectors, such as a school extension or an apartment building. If you hear 'a bit of everything', ask which project has an empty seat today.
Which stages of a project would I spend most of my time in?
Why ask it
Early design, detailed drawings and construction are close to being different jobs, and many people spend their first year in just one. Listen for the stage they name and for when you would see another. A worrying answer is production drawings with no end date and no plan to move you.
How much of the role is design, and how much is documentation and coordination?
Why ask it
Below principal level the split often leans toward documentation, and an interviewer who admits it is being straight with you. A promise of pure design work for a junior deserves some doubt. The check is how someone at your level spent last week, hour by hour.
How would you describe the firm's design approach, and who sets it on a project?
Why ask it
You have seen the buildings, so what you are after is how they get that way. Some studios have a house language every project follows, and others start again from the site and the client each time. The second half shows whether direction comes from one principal or is argued out by the team, which decides how much of your own thinking reaches the drawings.
What would you expect me to be handling on my own by the end of the first year?
Why ask it
This turns the job description into something you can be measured against. A stair package, a planning submission or a small job run with light supervision are all answers with content. When nobody can say, the role is probably 'help where needed', which makes a first review hard to pass or fail.
Would I stay with one project from early design through construction, or move between jobs as they need hands?
Why ask it
Staying with a building teaches you what your drawings cost someone on site. Moving around shows you more project types sooner. How long a typical job runs there settles which you are being offered: on a five-year hospital, 'start to finish' is most of your time at the firm.
How often would I get to a construction site, and at what point in the job?
Why ask it
Site is where you find out which of your details hold up, and firms differ widely on who gets to go. The best version has you walking the job beside someone senior from the early visits. Where juniors stay at their desks, the next thing to learn is who answers the contractor's queries and whether you could sit with them while they do.
Would I deal with clients and consultants myself, or does that go through the project lead?
Why ask it
Sitting in on a client meeting or a coordination call with the engineers is training you cannot get from a drawing set. Hear whether they describe a path: listening first, then taking the notes, then running a small item. 'Not for the first few years' deserves a why.
Which project in my portfolio is closest to the work I would be doing here?
Why ask it
Their pick shows what they think they are hiring you for, which may not be what you expected. If they point to the construction drawings and you were hoping for the competition scheme, better to hear it today. It also opens the door to asking what they found missing from the portfolio.
What is on the boards now, and what is coming in after it?
Why ask it
This is how you ask about job security without using the words. Named projects with dates behind them are reassuring. One large job nearing completion with nothing confirmed after it calls for a calm follow-up about how the firm staffed its last quiet spell.
How much of what the firm designs gets built?
Why ask it
Feasibility studies, competitions and early approvals can fill a studio for years without anyone seeing a building go up. If you need built work for your experience record or your portfolio, a low share matters. The sharper version is which of the current jobs has funding and a contractor.
How does the firm handle sustainability on an ordinary project, not the showcase one?
Why ask it
Nearly every practice says it cares, so the ordinary project is the test. The real answers are habits: energy modeling at an early stage, a materials policy, someone whose job includes it. If the reply is only about one award winner, you have learned that it depends on the client.
The team
How are project teams put together, and how many people would be on mine?
Why ask it
A team of three and a team of twenty give you different jobs under the same title. On a small one you touch everything and have less cover, and on a large one you may own the stair cores or the facade package for months. Decide which you want at this point in your career before you hear which it is.
Who would I take direction from day to day: a project architect, an associate, or a principal?
Why ask it
The person who hands you work and checks it will shape your first years more than the name on the door, so try to meet them if they are not in the room. An answer of 'whoever needs you' means several people setting priorities, and the follow-up is who settles it when they clash.
How would you describe the studio culture?
Why ask it
Every candidate asks this, so the stock reply is ready. Notice what they reach for first: the work, the people or the hours. Then ask for something from the past month that shows it, such as a Friday pin-up, a site trip for the whole office, or everyone staying late for one team's deadline.
Would I be on one project at a time or split across several?
Why ask it
Being split sounds like variety, but it can mean three deadlines and three leads who each think you are theirs. The detail that matters is who divides your week when two of them want you on the same day. One project at a time is calmer and narrower.
How involved do the principals stay once a project is under way?
Why ask it
Some principals draw alongside the team, and some appear at the client presentation and again at the deadline. The thing to hear is when design direction arrives. Late changes from the top are a common cause of the long nights you will ask about later.
How does design get reviewed here: pin-ups, desk crits, or a principal's markup?
Why ask it
The format tells you how ideas travel in the studio. Open pin-ups mean you will see how seniors think and be expected to speak. Markups that land on your desk overnight mean the design lives with one person, which can still teach you a lot if they explain the changes.
How many people at my level are in the studio, and how long have they tended to stay?
Why ask it
Peers are who you learn software tricks from and compare notes with, so being the only junior is a real difference. Length of stay is the quieter half of the question. When most people at your level are gone within two years, where they went is the next thing to find out.
Who decides which project someone goes onto next, and can staff ask for one?
Why ask it
Staffing is often settled in a regular meeting among the seniors, and people who have never said what they want get placed where the gap is. A good sign is an example of someone who asked for a project type and got it. Note the name of whoever runs that meeting.
Is there a technical lead, a specification writer or a BIM manager, or does each team cover those itself?
Why ask it
In a firm with specialists you have someone to ask about a waterproofing detail or a broken model, and you will learn their standards. Without them you learn by doing it all, with more risk of learning it wrong. Ask who you would take a technical question to on an ordinary afternoon.
Do people work from the studio every day, and how do reviews work for anyone remote?
Why ask it
Architecture is learned partly by overhearing, so treat this as a question about training as much as convenience. If seniors are mostly at home, find out how drawings get marked up and how a new person asks a quick question. A written policy is steadier than a habit, which can change with one new principal.
Tools
Which software does the studio run for drawing, modeling and visualization?
Why ask it
Check the answer against the job posting, since postings lag behind practice. If their main program is one you know, say what you have built in it, and if it is not, say so now and find out how others made the switch. Being found out in week one is worse than a frank answer today.
Does a project stay in one model from concept to construction drawings, or change programs along the way?
Why ask it
A handover between a design program and a documentation program is where work gets redrawn and information gets lost. Ask who does the redrawing, because it is often the newest person. A single model from the start usually comes with stricter rules about how you build it.
Are there office standards and templates, and who keeps them current?
Why ask it
Standards decide how much of your time goes to setting a file up and how much to drawing. A named person who maintains them is a good sign. 'We have some, but every team does its own thing' means your habits will be formed by whichever project you land on first.
How does someone who is new to your main program get up to speed?
Why ask it
You are asking whether training is real or assumed. Real looks like a walkthrough of the office setup in the first week, a named person to ask, and a small task before a live deadline. With 'you pick it up', the number to get is how many weeks they allow before they judge your speed.
Who checks a drawing set before it leaves the office, and what does that check involve?
Why ask it
A proper check protects you: an error caught by a senior with a red pen is a lesson, and one caught by the contractor is a problem with your initials beside it. Ask whether juniors see the marked-up set afterwards. An answer of 'whoever has time' is one to remember.
Where do construction details come from: an office library, the last project, or drawn fresh?
Why ask it
A maintained library means someone has learned from what failed and written it down. Copying from the last job passes on its mistakes along with its good ideas. Drawing each one fresh is slow and the best teacher of the three, provided someone experienced reviews what you draw.
How much do people here still sketch by hand or build physical models?
Why ask it
If hand drawing or model making is in your portfolio, this tells you whether it will be put to work or just admired. A studio with a workshop and a shelf of working models designs differently from one that goes straight to renderings. Look around on the way out to see which it is.
Are AI image or drafting tools allowed on client work here, and who decided?
Why ask it
Some studios now make early concept images this way and some forbid it on client work. What matters is that someone has made the call and written it down. Where nobody has, hold off using one on a live project until you have asked, since the client's confidentiality terms may have a say.
Hours
What are the studio's usual hours, and what does the week before a deadline look like?
Why ask it
Ask both halves together, because the first alone gets the contract answer. A worrying reply treats late nights as proof of commitment. A better one says how often they happen and what the firm does to prevent them.
When did the team last work late or over a weekend, and what caused it?
Why ask it
A date and a cause are more useful than 'occasionally'. One push before a big submission last spring is ordinary. When the cause was a late change of mind inside the firm, what you want next is whether anything was done differently on the following job.
How do deadlines get set: by the client's schedule, by a principal, or with the people who have to meet them?
Why ask it
A date agreed with the people doing the drawings tends to have the hours counted into it. One promised in a client meeting and announced afterwards often has not. Ask for a recent case where the team said a date could not be met, and what the firm then told the client.
What happens when a project's fee is spent before the drawings are finished?
Why ask it
Many projects run on a fee agreed in advance, and when it runs out the remaining work still has to be done by someone. Listen for whether the firm absorbs the cost, goes back to the client, or quietly expects the team to finish in its own time. The third is the one to weigh carefully.
How are hours recorded, and what happens if a task takes me longer than the time allowed for it?
Why ask it
Many practices track time against each project, and how they react to an overrun shows how they treat people who are still learning. The answer you hope for is that the lead wants to know early and adjusts the plan. Pressure to enter fewer hours than you worked is a red flag.
Does the firm enter competitions or do unpaid bids, and when does that work get done?
Why ask it
Competition entries are some of the most enjoyable design work in a studio, and they often sit on top of fee-paying jobs. The two things to pin down are whether entries are staffed in working hours and whether taking part is optional. If the answer is evenings and everyone joins in, count those hours when you compare offers.
Growth
How does the firm support people working toward licensure or registration?
Why ask it
The route to a license differs by country and state, so have them explain the local process and what the firm adds to it. Strong answers are concrete: a named supervisor, exposure to the kinds of work you must log, help with exam costs or study time. 'We are very supportive' with no detail needs a follow-up.
Who would sign off my logged experience, and would the work here cover the areas I still need?
Why ask it
Bring your own record and name the gaps, whether that is contract administration, site work or project management. A firm that only does early-stage work may not be able to fill them, however willing it is. Better to learn that now than a year into the job.
Does the firm pay exam or registration fees, and is study time given?
Why ask it
Policies range from nothing to full fees plus paid days off, and some attach conditions, such as paying only for a pass or asking for money back if you leave soon after. Ask for the policy in writing with the offer. It is part of your pay, so compare it between firms.
Would I have a mentor apart from my project lead, and how often would we meet?
Why ask it
A project lead needs drawings out the door, which is not always the same as what you need to learn. A separate mentor can say things about your career that your lead cannot. If mentoring is informal, ask one of the interviewers who theirs was and how that came about.
How many people have become licensed while working here in the past few years?
Why ask it
This checks the support answer against results. A handful of recent names, some of them still at the firm, is the best reply you can get. No names at all has two explanations: people arrive already licensed, or they leave before they finish.
Does the firm pay for professional memberships, courses or conferences?
Why ask it
Some licensing bodies require continuing education to keep a license, so check what yours asks for and whether the firm counts that time as work. A set amount per person each year is easier to use than 'just ask'. Find out what the last person spent theirs on.
What does the step from this role to project architect look like here, and how long did it take the last person?
Why ask it
Titles and their order differ from firm to firm, so ask them to describe the rungs in their own words. The last real case is more reliable than a general timeline. Listen for what that person did to earn it, such as running a small job alone.
When are reviews held, and do raises follow from them?
Why ask it
Some firms review every year on a fixed date, others when someone remembers. Ask who conducts yours and whether salary is discussed in the same meeting. If the two are separate, find out when pay is looked at, or you may wait a long time for a good review to reach your paycheck.
Pay and offer
What is the salary range for this role, and what would put someone at the top of it?
Why ask it
Save this for the person who can answer, usually a principal or whoever handles hiring, and for a second conversation if there is one. The second half is the useful part: it shows whether a license, a software skill or years of experience moves the number. Published salary surveys for your region give you something to compare with.
Is overtime paid, banked as time off, or neither?
Why ask it
Rules on overtime depend on where you work and how the role is classified, so ask how the firm handles it and check the answer against the contract. Where extra hours cost the firm money or leave, someone has a reason to plan deadlines carefully. 'It is part of the job' means the hours you heard about earlier are unpaid.
Does the title or the pay change when someone gets licensed here?
Why ask it
In some firms a license brings a new title and a raise the same month, and in others nothing changes until the next review. The last person it happened to is the example to ask for. Their case shows how much the firm values the credential it says it supports.
What benefits come with the role besides salary?
Why ask it
Health coverage, retirement contributions and paid leave differ a great deal by country and by firm size, so ask for the written summary. Small studios sometimes offer less on paper and more flexibility in practice. Put a rough value on each item before you set two offers side by side.
Is this a new position, a replacement, or a hire for one particular project?
Why ask it
A hire for one large job can still be a good one when you know the date it ends and what became of the people taken on for the last one. If you are replacing someone, where they went matters: up within the firm is a different story from out of it. A new seat usually means work has just been won.
When are you hoping to have someone start, and what is left in the process?
Why ask it
A firm that needs someone in two weeks has a deadline coming, which says something about your first month. Ask whether a second interview, a studio visit or a skills test is still to come. If you hold another offer with a date on it, this is the moment to mention it.
How to use your questions in an architecture interview
Practical guidance for the conversation itself
Before the interview
Study the built work, not just the homepage
Go through the firm's recent projects and note which are finished, which are under construction and which exist only as renderings. Your questions can then start from something real: 'I saw the library is on site. Is that the team this role joins?' It also stops you asking about project types the website already answers.
Know your own gaps
Write down what you still need: experience areas for your license, a building type, time on site, a program you have never run on a live job. The questions under Growth and The work only pay off if you can say what you are missing, and interviewers tend to respect a candidate who can.
Find out who will be in the room
A principal can speak to the pipeline, pay and where the firm is heading. A project architect knows the hours, the software and who checks the drawings. An office manager or HR person knows benefits and policy. Ask for names beforehand and sort your questions by who can answer them.
Pick five or six, one from each group
There is rarely time for more. From each group take the one you would not accept an offer without knowing, and put the most important first. Keep a few spares, because a good interviewer will answer some of yours before you ask.
In the room
Let the portfolio open the door
Many architecture interviews spend a good share of the time on your portfolio. Use it: after showing a project, ask whether the firm does that stage or type of work, and how. Questions that grow out of your own drawings sound like a conversation between colleagues, not a checklist.
Ask for the last time, not the policy
'Do you support licensure?' gets a yes. 'Who was the last person to get licensed here?' gets a name and a story. The same move sharpens the questions on deadlines, reviews and staffing.
Ask about hours without apologizing
Wanting to know the working week is not a sign of low commitment, and a studio that treats it that way has told you something. Ask plainly, in the middle of the conversation, and tie it to the work: 'What did the week before your last submission look like?'
Hold pay until someone who can answer is present
If the first conversation is with a project architect, stay with the work, the team and the tools. Raise the questions under Pay and offer with a principal or whoever handles hiring, and ask for anything that matters to you in writing. Where the posting already gave a salary range, start from that number instead of asking for it again.
Ask for a walk around the studio
Ten minutes among the desks shows you what is on the screens, whether there are models and marked-up prints about, how full the room is and how people speak to each other. If the interview is on a video call, ask whether you could visit before you decide.
Reading the answers
Names and dates beat adjectives
'We had two late nights before the submission in March' is information. 'We work hard and play hard' is not. When an answer is all adjectives, ask for one example before you judge it.
Compare the principal with the people at the desks
If you meet more than one person, ask two of them the same question about hours or about who reviews work. Small differences are normal. A wide gap means the people who run the firm and the people who draw for it are describing different places, and the second account is nearer to the job you would have.
Notice what they ask you
Interviewers who press on your detailing and construction drawings are hiring for production. Ones who linger on concept work and competitions want a designer. If that does not match the way they described the role, say so and ask which it is.
Do not decide on reputation alone
A firm whose buildings you admire can still be a poor place to learn, and a firm with unremarkable work can train people very well. Weigh who you would report to, which stages you would see and how the hours run before you weigh the name.
Which questions matter at your stage
A first job after school
Put the weight on Tools, Growth and the questions under The team about who directs you. Your first two years set your working habits, so who checks your drawings matters more than how impressive the project list is.
A few years in, still working toward a license
Lead with the experience you have left to log and the project stages you have not seen. Ask how many people got licensed at the firm in recent years. It is the quickest test of everything else they say about support.
Licensed and moving firms
Your questions shift to responsibility: whether you would run jobs, deal with clients directly and have a say in who is on your team. Pay and title can come up earlier in the conversation, since both sides expect it at this level.