Chief Engineer Interview Questions
For managers and directors across engineering and architecture. Interviews focus on leading technical teams, directing research and development projects and presenting proposals to clients.
30 questions, ranked by what the job needs most
Also for Chief Engineer: Petroleum Engineers · compare them →
Print the top 10:Scoring sheetPractice sheet
Question 1: What do you check at an engineering project handoff to confirm each discipline is working from the same design inputs?
Interviewer tipA sound check covers current input versions, units and assumptions shared across disciplines. Letting a handoff proceed with conflicting inputs still unresolved is a red flag.
Candidate tipWalk through how you compare the disciplines' input sources, revisions and assumptions at a handoff. Explain how you identify a mismatch before the next team relies on it.
Question 2: What would you do if a client requested a design change that reduced cost but left a safety concern unresolved?
Interviewer tipThe safety concern must be resolved through qualified technical review before the change is approved. Accepting the change just because it saves money is a wrong first move.
Candidate tipStart with the unresolved safety concern and the status of the proposed change. Explain the technical review you would arrange before deciding whether the client can get the cost saving safely.
Question 3: Describe a time you reassigned an engineer or designer because a project's needs had changed.
Interviewer tipThe answer should connect changed project needs to the engineer's skills, the reassignment and its result. Moving someone into technical work they cannot perform without needed support is a red flag.
Candidate tipPick one reassignment prompted by a change in project needs. Describe how you assessed the engineer's or designer's fit for the new work, managed the transition and checked the result.
Question 4: Walk me through your most recent successful negotiation with a client about the scope of a design project.
Interviewer tipListen for where the client's request and the team's plans differed, what the candidate offered, and what both sides agreed to. Promising design work the team could not deliver is a red flag.
Candidate tipStart with what the client wanted your design team to deliver and where you disagreed. Explain the trade-off you proposed, such as moving part of the work to a later phase, and end with what both sides agreed to.
Question 5: Describe a presentation you're proud of where you explained a design proposal or technical findings to a client.
Interviewer tipA strong example shows how the candidate made a technical point clear and what the client's response showed. Watch for a presentation that left out a limitation the client needed to know.
Candidate tipPick a point in the proposal or findings the client needed to understand. Explain how you made it clear, such as using a drawing to show a design limit, and give one sign the client understood.
Question 6: Describe a time you built an engineering project budget with incomplete scope information.
Interviewer tipListen for the candidate's own budget assumptions, treatment of unknown scope and eventual result. Presenting an uncertain scope as a firm, complete budget is a red flag.
Candidate tipChoose one engineering budget with real scope gaps. Name the cost inputs you had, the assumptions you made explicit and how the budget held up as the scope became clearer.
Question 7: Tell me about a project where you had to bring several engineering disciplines or outside consultants together to deliver one integrated design.
Example answerThe interviewer wants to know whether you can integrate the work of different technical teams so the design holds together. Use Situation, Task, Action, Result. Name the disciplines, the risks where their work met, and the methods you used to coordinate them.
Sample answer: "I led design of a mid-size laboratory building with in-house structural and civil teams and an outside mechanical and electrical consultant. The biggest risk was ductwork and piping clashing with the structure, since lab buildings carry heavy services. I set up a shared model with weekly coordination reviews, gave each discipline a clear owner for every interface, and kept a running clash log that we cleared before each milestone. When the consultant fell behind, I moved our review dates rather than letting the structural team design around guesses. We went to bid with far fewer coordination questions from contractors than on our previous lab project."
Pitfalls to avoid: listing meetings without explaining how conflicts were resolved; taking credit for every discipline's work; leaving out what you would do differently next time.
Interviewer tipListen for how they handled the interfaces between disciplines, such as clashes, handoffs and shared deadlines. Treating each team separately and fixing conflicts late is a red flag.
Candidate tipName the disciplines involved, the coordination problems you expected, the methods you used, such as regular model reviews or a clear split of responsibilities, and the result.
Question 8: Walk me through how you plan and prioritize when you are running several engineering projects with competing deadlines and shared staff.
Example 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.
Interviewer tipListen 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 9: 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.
Example 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.
Interviewer tipA 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 10: Describe a time you guided an engineer whose work fell short of the project expectations you had set.
Example 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.
Interviewer tipLook 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 11: How do you make sure the work your team produces meets the codes, permits, safety rules and industry standards that apply to it?
Example answerThe interviewer wants to know that compliance is built into your team's process, not left to chance. This is a process question, so describe your system, then give a short example of it catching a problem. The codes and licensing rules that apply vary by state and locality, so speak to how you find and follow the ones for each project.
Sample answer: "I build compliance into design reviews. Each project starts with a code and permit checklist for that jurisdiction, and an experienced engineer who didn't do the design checks the work against it before each milestone. I also assign someone to track changes to the codes and standards we use most and share updates at team meetings. On one project, the checklist review found that a recent local code update changed the fire separation requirements for the building we were designing. We caught it before submittal, revised the drawings, and avoided a permit rejection."
Pitfalls to avoid: saying compliance is the inspector's job; naming rules without explaining your process; claiming your team has never had a compliance issue.
Interviewer tipLook for a repeatable process: code checks in design reviews, qualified reviewers, and tracking changes in rules. Relying on the client or an inspector to catch problems is a red flag.
Candidate tipDescribe your review steps, who signs off, how you stay current when standards change, and give an example of a compliance issue you caught early.
Question 12: Walk me through a time resource limits made you scale back an engineering project before it started.
Interviewer tipThe example should connect a specific resource limit to a smaller, feasible engineering scope and its result. Cutting scope without checking whether the project still meets its purpose is a red flag.
Candidate tipSet out the original engineering scope and the resource limit. Focus on your feasibility assessment, the work you removed or deferred and the result of that decision.
Question 13: How do you check that an engineering cost estimate covers the full project scope before recommending approval?
Interviewer tipExpect a comparison of scope and deliverables against estimate line items, including exclusions and assumptions. Approving an estimate with known scope gaps hidden from the decision maker is a red flag.
Candidate tipExplain how you trace engineering deliverables to estimated work and check exclusions, quantities and assumptions. Show how you handle a missing item before recommending approval.
Question 14: Tell me how you used a discussion with your design staff to improve a project.
Interviewer tipListen for a specific suggestion from the design staff, what the candidate did with it, and the improvement that followed. Watch for someone who dismissed a design concern without checking it.
Candidate tipPick a project issue your team raised, such as two drawings that didn't line up. Explain how you used the team's input to make a change and what improved on the project.
Question 15: Give an example of a technical review procedure you changed after the same error kept appearing in engineering deliverables.
Interviewer tipA strong example links a recurring deliverable error to a specific review change and evidence that it helped. Adding a signoff without addressing the cause of the missed error is a red flag.
Candidate tipName the recurring engineering error and the review step that missed it. Describe your change to the procedure, how reviewers used it and the result in later deliverables.
Question 16: Share an example of how you helped a junior engineer or designer build a skill through mentoring.
Example 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.
Interviewer tipListen 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 17: Talk about a time you revised an engineering team's technical goal after early test results challenged its assumptions.
Interviewer tipListen for a reasoned revision tied to test evidence and leadership's broader aim. Changing a goal solely to make a failed test look successful is a red flag.
Candidate tipExplain the original technical goal, the test result that challenged it and your part in revising it. Show how the revised goal still served leadership's aim and what happened next.
Question 18: Walk me through a long-range engineering objective you developed and worked toward with your team.
Interviewer tipA 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 19: Share an example of how you corrected a misleading project status report before management used it.
Interviewer tipSeek a clear account of the misleading status, the source checked and the corrected report's result. Replacing a questionable figure with an unsupported guess is a red flag.
Candidate tipBriefly describe the project report and the misleading claim. Spend most of your answer on how you checked the source, corrected the report and confirmed management received accurate information.
Question 20: How would you compare the environmental impacts of two engineering design options with different energy use and material needs?
Interviewer tipA useful comparison uses the same project purpose and time period, with clear energy and material assumptions. Ignoring known material impacts simply because one option uses less energy is a red flag.
Candidate tipSet a common basis for the two designs, then compare energy use and material impacts over that period. Explain the information you need and how you would make uncertainties visible.
Question 21: Describe a program which you developed or implemented to improve sustainability or reduce the environmental impact of a project.
Question 22: Tell me about a time your technical recommendation to senior leadership changed a decision about a project or product.
Example 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.
Interviewer tipA 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 23: Tell me about a time you introduced a new design, analysis or project tool to your engineering team.
Interviewer tipStrong 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 24: In your experience, what is the key to developing a good team?
Example 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.
Interviewer tipLook for how they build mutual trust, respect, and cooperation.
Candidate tipBe sure to explain how you encourage and build trust, respect, and cooperation.
Question 25: Walk me through how you handled a difficult client, contractor or stakeholder on an architecture or engineering project.
Interviewer tipListen 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 26: Share an experience in which you successfully coordinated and/or directed a project. What methods led to your success?
Question 27: Walk me through a design review where you decided whether to approve a product design or a proposed change.
Interviewer tipA strong answer points to the requirement and the evidence that drove the decision. Signing off while ignoring a known gap against the design requirements is a red flag.
Candidate tipPick a review where the decision was yours. Name the design requirement at stake, the evidence you weighed, and whether the design went ahead or went back for changes.
Question 28: How do you plan an engineering project to see whether it can meet its technical requirements within budget and on time?
Interviewer tipA sound plan shows what still needs to be proven about the design and how the team estimated time and cost. Treating an untested design assumption as settled is a red flag.
Candidate tipStart with the design requirements, then explain how you check unproven design assumptions and estimate staff time and costs. Say what would make you revise the plan.
Question 29: Tell me about your last experience preparing budgets, bids, and contracts. What methods did you use to successfully negotiate research contracts?
Question 30: Tell me about the last contract or cost estimate you approved. How about one you rejected?