Architect Manager Interview Questions
For managers of architectural teams. Interviews focus on client briefs, coordination of building designs and code review.
30 questions
Question 1: Tell me how you negotiated a client's building space requirements when the initial brief exceeded the available floor area.
Suggested answerThe interviewer wants to see how you negotiate a building brief that cannot fit within the available space.
Use Situation, Task, Action, Result. Explain the floor area limit and the client's competing needs. Describe how you clarified priorities, explored options and confirmed the brief used for design.
A sample answer: "A client's initial room list exceeded the usable area of a renovation. I laid out the area schedule with the client and asked which spaces needed dedicated rooms and which could serve more than one purpose. I explained the design limits rather than simply reducing every room. We agreed to combine compatible functions and defer an optional space. I recorded the revised room list and obtained the client's confirmation before the team developed the layout."
Use a real brief and give the actual design outcome. Avoid quietly deleting a requirement, promising space the building cannot provide or presenting a client discussion without explaining the agreement reached.
What interviewers listen forA strong answer explains the competing space needs, the discussion with the client and the agreed brief. Quietly dropping a required space without client agreement is a red flag.
Candidate tipUse one real building brief. Explain the area constraint, how you helped the client choose priorities and the requirements you agreed to carry into design.
Question 2: Share an example of how you coordinated architects and building engineers when their drawings conflicted.
Suggested answerThe interviewer wants to learn how you bring architectural and engineering drawings into agreement.
Use Situation, Task, Action, Result. Describe one conflict, its effect on the building design and your responsibility for coordination. Explain the review you organized, the agreed correction and how you confirmed it across the drawing set.
For example: "A structural detail occupied space shown as clear on the architectural plan. I brought the architect and structural engineer together with the affected drawings. We checked the space requirement and the structural constraint, then agreed on a revision the two teams could support. I assigned responsibility for the changed sheets and checked the next coordinated set with both leads. The revised drawings showed the same arrangement before issue."
Choose your own case and state what you checked personally. Avoid blaming one discipline, accepting a verbal resolution without drawing updates or describing two separate revisions that still conflict.
What interviewers listen forThe example should show how the candidate organized review of the conflicting drawings and confirmed an agreed design. Letting each team issue its own conflicting version is a red flag.
Candidate tipDescribe one conflict between architectural and engineering drawings. Explain how you brought the teams together, settled responsibilities and checked the revised set.
Question 3: How do you organize code checks across an architectural team's building drawings before a permit submission?
Suggested answerThe interviewer wants to understand how you make code review a coordinated part of producing architectural drawings.
Walk through the review responsibilities, the requirements that apply to the building and the way you track issues through revisions. Explain how you check that a correction on one drawing agrees with the rest of the set.
For example: "I would identify the applicable building requirements at the start of the review and assign parts of the drawing set to reviewers with the needed expertise. I would record each issue against its drawing and give it an owner. If an exit layout changed, I would have the team check the related plans and schedules rather than closing the issue on one sheet alone. Before submission, I would confirm that open code issues were resolved and the drawing set was consistent."
Use the employer's actual review process where you know it. Avoid assuming a permit reviewer will catch everything, confusing a checked box with a resolved issue or presenting one jurisdiction's rules as universal.
What interviewers listen forExpect a clear division of code review work, checks against the applicable building requirements and resolution of conflicts between drawings. Submitting known code conflicts as if they were resolved is a red flag.
Candidate tipWalk through who reviews which drawings and how you track code issues to resolution. Explain how the team checks that revisions agree before submission.
Question 4: Tell me about a presentation you have given to a client that you are proud of. The presentation could be a proposal, report, or findings.
Suggested answerThe interviewer wants to see that you can explain technical work to clients clearly and win their confidence. Use Situation, Task, Action, Result: who the client was, what you had to present, how you prepared and tailored it, and what the client decided. Focus on how you made the technical content fit the audience.
Sample answer: "Our team had finished a study of options for expanding a client's manufacturing facility. The client's board had little engineering background, so I cut the report down to three options with plain trade-offs on cost, schedule and risk, and moved the calculations to an appendix. I rehearsed with two engineers who played skeptical board members. During the meeting, a board member asked about disruption to production, and because we had prepared a phasing plan, I could answer on the spot. The board picked our recommended option and asked us to start design the following month."
Pitfalls to avoid: describing your slides instead of what the client needed; burying a nontechnical audience in detail; skipping the outcome or what you learned.
Question 5: Describe a time you guided an engineer whose work fell short of the project expectations you had set.
Suggested answerThe interviewer wants to learn how you turn project expectations into useful guidance when an engineer's work falls short.
Use Situation, Task, Action, Result. State the deliverable you expected, how you checked the work and the gap you found. Spend most of the answer on your feedback and follow-up, then give the actual result and a lesson.
An example of the action portion: "An engineer submitted calculations without the supporting notes our review checklist required. I met with them privately and compared the package with a complete example. I asked what was getting in the way and learned they were rushing between two projects. I clarified which notes reviewers needed, reviewed their workload and arranged a short check before the next submittal."
Use your own case and describe what the next review actually showed. Avoid describing expectations without follow-up, blaming the engineer without explaining your guidance, or claiming an improvement you cannot support.
What interviewers listen forLook for clear project expectations, checks on the engineer's work and specific feedback, with a real result. Blaming the engineer without explaining any guidance is a red flag.
Candidate tipExplain the deliverables you expected, how you spotted the gap, and the guidance you gave the engineer. End with the result and what you learned.
Question 6: Walk me through how you plan and prioritize when you are running several engineering projects with competing deadlines and shared staff.
Suggested answerThe interviewer wants to understand how you keep several projects moving when people and time are limited. Describe your planning system first, then show it working in one real example. Cover how you set priorities, how you track progress, and how you shift staff when things change.
Sample answer: "I keep one schedule of every active project's milestones and who is assigned, and I review it with my leads every Monday. I rank work by client commitments, risk and how much other work depends on it. Last year two projects hit design deadlines in the same week, and one had a permit submittal that couldn't slip. I moved two engineers to the permit job for about two weeks, told the other client early that one drawing set would come a few days later, and agreed on a new date with them. Both projects met their key dates, and the client appreciated hearing about the change ahead of time."
Pitfalls to avoid: claiming you never face conflicts; describing tools without the decisions you made; relying on overtime as the plan.
What interviewers listen forListen for a concrete system: milestones, staff loading, and how they decide which project gets people first. Relying only on longer hours is a red flag.
Candidate tipDescribe the tools and check-ins you use, how you weigh client deadlines against risk, and give one example of moving staff between projects and what happened.
Question 7: Describe a product design or change which you approved. How about a design you rejected?
Question 8: What methods do you use to plan and assess the feasibility of projects?
Question 9: Share an example of how you helped a junior engineer or designer build a skill through mentoring.
Suggested answerThe interviewer wants to see how your mentoring helps an engineer or designer develop a specific skill.
Use Situation, Task, Action, Result. Briefly describe the person without identifying them, name the skill they needed and explain your coaching over time. End with the change you actually observed and what you learned about mentoring.
An example to adapt: "A junior engineer knew the design details but struggled to explain choices in client meetings. We chose one short agenda item for them to present. Before each meeting, we rehearsed the explanation and likely questions. Afterward, I gave specific feedback and asked for their view of the discussion. We used that feedback to plan their next presentation."
Complete your own answer with evidence of learning, such as a clearer explanation you heard in a later review. Avoid taking credit for all of the engineer's growth, calling one casual suggestion a mentoring program, or claiming progress without describing anything you observed.
What interviewers listen forListen for specific coaching actions and evidence of the engineer's learning, such as clearer design explanations. Taking credit for growth without describing any mentoring is a red flag.
Candidate tipPick one engineer or designer. Name the skill gap, describe your coaching over time, and finish with the change you observed in their work.
Question 10: Walk me through how you handled a difficult client, contractor or stakeholder on an architecture or engineering project.
What interviewers listen forListen for their own steps to resolve the friction, protect the project's scope or schedule, and learn from the result. Dismissing the client or contractor's concerns without checking them is a red flag.
Candidate tipChoose one real project and briefly explain the disagreement. Focus on your actions to understand the person's concerns and protect the project's scope or schedule, then give the result and what you learned.
Question 11: Tell me about a time you had to tell a client or senior leadership that a project would be late, over budget or needed a major design change.
Suggested answerThe interviewer wants to see whether you deliver bad news early, honestly and with a plan. Use Situation, Task, Action, Result: what went wrong, how and when you raised it, the options you offered, and how it ended.
Sample answer: "Midway through design of a water treatment upgrade, our geotechnical results showed weaker soil than the early reports assumed. The foundations would need redesign, which meant several weeks of delay and added cost. I didn't wait for the next monthly meeting. Within days, my team worked out two options: redesign the foundations, or shift the new tanks to a better part of the site. I called the client's project manager, explained what we found and why, and followed up with a short memo comparing both options. They chose the relocation, which protected most of the schedule, and later told us the early warning helped them brief their own board."
Pitfalls to avoid: blaming others for the problem; softening the message so much that the impact is unclear; bringing the problem with no options.
What interviewers listen forA strong answer shows they raised the issue early, came with options and owned the message. Hiding the problem until it could no longer be avoided is a red flag.
Candidate tipExplain what went wrong, when you found out, how you prepared the message and the options, and how the client or leaders responded.
Question 12: Share an experience in which your conference with staff helped to improve a project.
Question 13: Walk me through a long-range engineering objective you developed and worked toward with your team.
What interviewers listen forA strong example links a long-range engineering goal to concrete actions and progress checks. Claiming success without explaining the team's work or any evidence of progress is a red flag.
Candidate tipName the engineering goal and its time frame, explain why you chose it, and describe the steps and progress checks you used. End with the actual result, even if the goal changed.
Question 14: Describe a program which you developed or implemented to improve sustainability or reduce the environmental impact of a project.
Question 15: Tell me about a time your technical recommendation to senior leadership changed a decision about a project or product.
Suggested answerThe interviewer wants to see whether you can turn technical judgment into advice that leaders act on. Use Situation, Task, Action, Result: the decision leadership faced, what you recommended, how you made the case, and what happened.
Sample answer: "Our leadership planned to keep an aging test rig in service for a few more years to save money. My team's maintenance records showed failures getting more frequent, and each one delayed product testing. I put together a short comparison of repair costs, lost testing time and the risk of a failure during an important client program, next to the cost of replacing the rig. I presented it in business terms rather than technical detail and offered a phased plan that spread the cost over two budget years. Leadership approved the replacement, and the testing delays from that rig stopped once the new one was in place."
Pitfalls to avoid: overstating your role in the final decision; recommending something without evidence; leaving out what happened afterward.
What interviewers listen forA strong answer shows they framed the advice in the cost, risk and schedule terms leadership cares about. Pushing a favorite idea without evidence is a red flag.
Candidate tipSay what the decision was, what you recommended and why, the evidence you used to make the case, and what changed as a result.
Question 16: Tell me about a time you introduced a new design, analysis or project tool to your engineering team.
What interviewers listen forStrong answers cover why the tool was worth the switch, how they handled training and pushback, and what improved. Adopting tools for their own sake is a red flag.
Candidate tipName the problem the tool solved, how you tested it before rolling it out, how you brought the team along, and what changed in time, cost or quality.
Question 17: In your experience, what is the key to developing a good team?
Suggested answerThe interviewer wants to know what you believe makes a team work, and whether you have acted on that belief.
Name one or two keys, such as clear roles, trust, or regular honest feedback. Then back them up with a short example from a team you led or belonged to, and say what changed.
Sample answer: "For me, the key is trust built on clear roles. On one team I joined, two people kept doing the same tasks while other work went undone, and it caused friction. I suggested we list who owned each part of our weekly work and review it at a short Monday meeting. Once everyone knew what they owned, people started asking each other for help instead of complaining. Within a month we stopped missing handoffs, and the meetings got shorter."
Pitfalls: Don't give a list of buzzwords with no example. Avoid taking all the credit for the team's success. If you were a team member, don't describe only what the manager should have done.
What interviewers listen forLook for how they build mutual trust, respect, and cooperation.
Candidate tipBe sure to explain how you encourage and build trust, respect, and cooperation.
Question 18: Share an experience in which you successfully coordinated and/or directed a project. What methods led to your success?
Question 19: Tell me about your last experience preparing budgets, bids, and contracts. What methods did you use to successfully negotiate research contracts?
Question 20: Tell me about the last contract or cost estimate you approved. How about one you rejected?
Question 21: Tell me about the last staff you recruited, directed, and evaluated. What methods did you find most effective?
Question 22: Tell me about your last experience recruiting, interviewing, or hiring an employee. What techniques did you find most effective in finding the right person for the job?
Suggested answerThe interviewer wants to see that you can find the right person for a role in a fair, organized way.
Use Situation, Task, Action, Result. Describe the role you were filling, how you defined what the job needed, the techniques you used to screen and interview, and how the hire worked out. Say which technique helped most.
Sample answer: "I helped my manager hire a new team member last spring. Before posting the job, we listed the three skills that mattered most and wrote interview questions for each one. Every candidate got the same questions, and we scored the answers separately before comparing notes. We also asked the top two candidates to do a short work sample. The structured questions helped us compare people fairly, and the person we hired was working on their own within a few weeks."
Pitfalls: Don't describe hiring on gut feeling alone. Avoid any mention of personal traits that have nothing to do with the job. Don't skip how the hire turned out.
Question 23: Tell me about the last time you oversaw the work of someone else. How did you effectively motivate, develop, and direct the worker(s)?
Suggested answerThe interviewer wants to see how you guide other people's work: setting direction, keeping them motivated, and helping them grow.
Use Situation, Task, Action, Result. Name who you oversaw and on what work, then give one concrete thing you did for each part: direction, motivation, and development. Finish with how the work turned out.
Sample answer: "Last year I led two newer coworkers on a project to clean up our customer records. I split the work by region and gave each person a clear weekly target. When one of them got discouraged by the slow pace, I showed them a faster way to find duplicates and pointed out how much they had already finished. I also had the other person run our weekly check-in to build their confidence. We finished a week early, and both later took on similar projects on their own."
Pitfalls: Don't describe only giving orders. Avoid vague claims like being a natural leader. Don't leave out what the workers achieved.
Question 24: Tell me about a time when your ability to analyze needs and product requirements helped you create an effective design or make an informed decision to benefit your company.
Suggested answerThe interviewer wants to see how you find out what is really needed before you design something or make a decision.
Use Situation, Task, Action, Result. Explain how you gathered the needs or requirements, how you weighed them, the design or decision you reached, and how it helped the company.
Sample answer: "Our team was asked to choose a new tool for tracking customer requests. Instead of starting with product demos, I talked to the people who would use it every day and listed what they needed most: quick search, simple tags, and reports for managers. I scored three options against that list and shared the results. We chose the one that fit the daily work best, even though it had fewer extra features. People were using it within a week, and we didn't need a second round of training."
Pitfalls: Don't jump to the solution without showing how you learned the needs. Avoid a decision made only on cost or personal preference. Don't skip the benefit to the company.
Question 25: Share an experience in which your ability to consider the costs or benefits of a potential action helped you choose the most appropriate action.
Suggested answerThe interviewer wants to see that you think through the trade-offs of a decision before acting.
Use Situation, Task, Action, Result. Describe the decision, the options, and the costs and benefits you weighed, including money, time, risk, and the effect on people. Explain which you chose and how it turned out.
Sample answer: "Our team's printer broke for the third time in a year. One option was another repair, which was cheap. Another was a new printer, which cost more up front. I looked at the past year's repair bills and the downtime each breakdown caused. The repairs plus lost time were likely to cost more than a new machine over two years. I shared that with my manager, we bought a new printer, and we haven't had a breakdown since."
Pitfalls: Don't focus only on money; include time and people. Avoid a decision you made without checking the facts. Don't skip how it turned out.
Question 26: Provide a time when you were able to identify a complex problem, evaluate the options, and implement a solution. How did the solution benefit your employer?
Suggested answerThe interviewer wants to see how you handle problems with many parts: how you break them down, choose a path, and follow through.
Use Situation, Task, Action, Result. Explain why the problem was complex, such as several causes or many people affected. Walk through how you found the root cause, the options you weighed, and how you put the solution in place. End with the benefit to your employer.
Sample answer: "Our monthly billing kept going out late. The cause wasn't one thing: data arrived late from two departments, and the billing software needed manual fixes. I mapped each step, timed them, and found the manual fixes took the most time. I compared hiring temporary help with automating the fixes, and we chose automation with help from our technology team. Billing went out on time for the next three months, and customers paid faster."
Pitfalls: Don't pick a simple problem and call it complex. Avoid skipping the options you considered. Don't take credit for others' work; name who helped.
Question 27: Provide an example when your ethics were tested.
Suggested answerThe interviewer wants to know whether you do the right thing when it is inconvenient, and how you handle pressure to cut corners.
Use Situation, Task, Action, Result. Describe the pressure or temptation without naming people, explain the choice you made and why, and how you handled the conversation. Keep the focus on your actions, not on judging others.
Sample answer: "Near the end of a quarter, a coworker asked me to record a sale as complete even though the customer hadn't signed yet, so our numbers would look better. I told them I wasn't comfortable doing that and suggested we tell our manager the deal would close the following week. My manager agreed it should wait. The customer signed early in the new quarter, and our records stayed accurate."
Pitfalls: Don't say your ethics have never been tested. Avoid stories that make you sound self-righteous or that share confidential details. Don't pick an example where you went along with the wrong choice and stop there.
Question 28: Share an experience in which your attention to detail and thoroughness had an impact on your last company.
Suggested answerThe interviewer wants proof that you catch errors others miss and that this protects the organization.
Use Situation, Task, Action, Result. Describe what you were checking, what you noticed, and how you found it, such as comparing against a source or double-checking totals. Then explain what would have happened if the error had gone through, and what you did to prevent it next time.
Sample answer: "While preparing an order for a large customer, I compared the quantities against the signed quote, as I always do, and saw that one item had been entered as 1,000 units instead of 100. I flagged it to my supervisor, we corrected it before it shipped, and we avoided a costly return. Afterward I suggested adding a quote-check step to the order form, and the team adopted it."
Pitfalls: Don't just say you're detail-oriented without an example. Avoid exaggerating the dollar impact. Don't describe perfectionism that caused missed deadlines.
Question 29: Share an experience in which your willingness to lead or offer an opinion helped your company.
Suggested answerThe interviewer wants to know whether you step forward when a situation needs direction, even without a formal title.
Use Situation, Task, Action, Result. Explain what was missing or going wrong, why you chose to speak up or take charge, and what you did to bring others along. Make the benefit to the organization clear at the end.
Sample answer: "Our team kept missing small handoffs because no one was sure who owned each task after weekly meetings. I suggested we end each meeting by naming an owner and a due date for every action item, and I offered to send the list out that afternoon. After a month, missed handoffs had mostly stopped, and other teams in our area started using the same format."
Pitfalls: Don't take credit for the team's work. Avoid a story where you overrode others without listening. Don't stop at the opinion you gave; show what changed because of it.
Question 30: What is the most challenging part of budgeting for you?
Suggested answerThe interviewer wants to see how you plan with limited money, and how honestly you can name a challenge and deal with it.
Name one real challenge, such as estimating costs that change, keeping spending on track during the year, or balancing requests from different people. Then explain the method you use to manage it and give a short example.
Sample answer: "For me, the hardest part is planning for costs that change during the year, like supplies whose prices rise without much warning. On a team budget I helped manage, I started reviewing our biggest expenses every month instead of every quarter, and I kept a small reserve line for price changes. When a key supply went up partway through the year, we covered it from the reserve instead of cutting other plans."
Pitfalls: Don't say budgeting is never hard for you. Avoid naming a challenge with no plan for handling it. Don't claim budget authority you haven't had.