Division Engineer Interview Questions
For electrical engineers who design power systems, motors, controls and electrical equipment. Interviews focus on design calculations, specifications and testing.
30 questions, ranked by what the job needs most
Print the top 10:Scoring sheetPractice sheet
Question 1: Walk me through a change you made to an electrical circuit to meet a new operating requirement.
Interviewer tipA strong example connects the circuit change to the new requirement and shows how they checked its performance. Changing component values without checking voltage, current or power limits is a red flag.
Candidate tipUse one circuit change from a real project. State the new requirement, explain your design changes and checks, then finish with the measured result and a lesson for your next design.
Question 2: Tell me about an electrical drawing or specification you prepared that helped an installation meet code and the customer's requirements.
Example answerThe interviewer wants to know how your electrical drawings or specifications help installers meet the project's requirements. Use Situation, Task, Action, Result. Identify the installation, your responsibility for the documents, the checks you performed, and the handoff.
For example: "For a warehouse power upgrade, I prepared the one-line diagram and panel schedules. I compared the equipment list with the proposed panel loads and found that a new machine was missing from the calculation. I updated the load calculation and checked the feeder and panel selections against the applicable code and project requirements. I coordinated the change with the project engineer, marked the revision clearly, and issued the reviewed drawings with notes explaining the changed circuit. The installer received the revised documents before that part of the work began."
Keep the example true to your own role. Avoid claiming inspection results you cannot support, describing a drawing without its checks, or leaving the contractor to guess which revision applies. Code editions and local adoption vary; identify the rules that applied to your project.
Interviewer tipListen for checks of the electrical drawing against the applicable code and customer's needs, plus a clear handoff to installers. Issuing it with known unresolved conflicts is a red flag.
Candidate tipName the system, the drawing or spec you made, and the code or requirement it had to meet. Explain how you caught any conflict before installation and how the job turned out.
Question 3: Walk me through the calculations you used to set a specification for an electrical installation.
Interviewer tipA strong answer traces the specified size or rating back to the expected load and shows how the candidate checked the calculation. Reusing a rating from a past job without checking the new load is a red flag.
Candidate tipName the size or rating you had to specify, the load and installation conditions you used, and one check you made before putting the value on the drawing.
Question 4: Describe how you've coordinated electrical equipment testing to meet a project's acceptance requirements.
Interviewer tipListen for who ran each check and how the candidate made sure everyone used the right pass limits. Signing off with a required test still missing is a red flag.
Candidate tipUse a real test program to show how you set the test sequence, assigned each check, and made sure the team knew what results the equipment had to meet before sign-off.
Question 5: Share a method you've used to keep an electrical equipment installation on schedule and within budget.
Interviewer tipListen for how they tracked installation milestones and equipment and labor costs against the plan. Checking spending only after the installation was finished is a red flag.
Candidate tipPick one installation and explain how you used the work schedule and cost records to spot problems early. Finish by comparing the actual finish date and cost with the plan.
Question 6: What would you do if a completed electrical installation matched the drawings but showed signs of overheating during operation?
Interviewer tipProtect people first: arrange for safe shutdown if needed, keep clear of energized parts and get the overheating assessed before acceptance. Accepting unsafe operation because it matches the drawings is a red flag.
Candidate tipStart with the overheating hazard and your role in getting the installation made safe. Then explain how you would compare operating conditions with equipment ratings and resolve the issue before accepting the installation.
Question 7: How do you make sure your designs comply with the electrical codes and standards that apply to a project?
Example answerThe interviewer wants to know whether compliance is built into your design process or left to the end. Explain your steps, then back them with a short example. Cover how you find which codes and standards apply, when you check, who reviews your work, and how you keep up with changes. Codes are adopted by states and local jurisdictions, often with amendments, so say that you confirm the edition in force for each project. Sample answer: "At the start of a project I confirm which code editions and local amendments apply, and note any utility or client standards. I check key items such as conductor sizing, grounding and clearances as I design, not at the end. Every drawing set gets a peer review against a checklist before it is issued. On one job, that review caught a working clearance problem at a switchboard that would have failed inspection." Pitfalls to avoid: naming codes without explaining how you apply them, relying on the inspector to catch errors, and claiming you know every code by heart.
Interviewer tipLook for knowing which codes apply, checking early, peer review and tracking code changes. Leaving code checks to the inspector is a red flag.
Candidate tipName the kinds of codes and standards you work with, then describe your steps, such as checklists, design reviews and talks with inspectors. A real example helps.
Question 8: Describe a tool you designed to make an electrical engineering task easier or more reliable.
Interviewer tipAsk what they designed and how they checked its benefit, such as getting consistent readings across repeated tests. Calling a tool reliable after one successful run is a red flag.
Candidate tipA course lab tool can count. Say what your test script or test fixture (a setup that holds and connects the device) was built to do and what showed it made the task easier or the results more consistent.
Question 9: Tell me how you used test results to choose between two electrical design options.
Interviewer tipListen for which measurement settled the choice and why it mattered to the design. Picking an option that missed a required limit because it scored better on another measure is a red flag.
Candidate tipUse a real design decision from work or a capstone. Name the requirement at stake, such as power use or signal accuracy, and point to the test result that tipped the decision.
Question 10: Walk me through how you analyzed test or measurement data to find the cause of a problem in an electrical system.
Example answerThe interviewer wants to understand how you work through data to find a root cause instead of guessing. Walk through it in order: the symptom, the data you collected and how, how you narrowed the possibilities, and how you confirmed and fixed the cause. Sample answer: "A production line kept tripping a breaker at random times. I set up a power quality meter on the feeder for a week and lined up the trip times with the line's operating log. The trips matched moments when two large motors started together, and the combined inrush current was close to the breaker's setting. I confirmed it by staggering the starts during a test shift, with no trips. We added a start delay in the controls and adjusted the breaker settings within the coordination study, and the trips stopped." Pitfalls to avoid: describing tools without your reasoning, skipping how you checked that the data was accurate, and stopping at a likely cause without confirming it.
Interviewer tipListen for a clear method: checking the data's quality, comparing it to expected values and confirming the cause with a test. Jumping to a cause without checking is a red flag.
Candidate tipPick one real problem. Say what data you collected and with what instruments or software, how you narrowed down the cause, and how you confirmed it.
Question 11: Describe effective specifications you prepared for the purchase of materials or equipment. How about specifications that were not as effective?
Question 12: Share an experience in which conferring with others has helped you in your work.
Question 13: Describe a time you caught a missing labor or material cost while estimating an electrical project.
Interviewer tipExpect a specific omitted cost, how they found it and its effect on the estimate. Quietly leaving out known labor or materials to meet a target budget is a red flag. Ask what they changed in later estimates.
Candidate tipPick one estimate with a missing labor or material item. Show how you traced it to the electrical scope, checked its quantity or rate and corrected the estimate. End with the result and a check you added for future estimates.
Question 14: Share an experience in which investigating a vendor's or competitor's product helped you in your work.
Question 15: Describe an effective research procedure you planned and/or implemented to apply principles of electrical theory to engineering projects.
Question 16: What is the state of your reports regarding electrical engineering studies or projects? What is one thing you would like improve in your reports?
Question 17: Tell me about a time you used customer reports to work out how widespread an electrical problem was.
Interviewer tipListen for how they compared the timing, locations and symptoms in customer reports to establish the problem's reach. Treating unverified reports as proof of a shared cause is a red flag; ask what their investigation established.
Candidate tipChoose a real investigation involving customer reports. Explain how you compared the reports, checked which equipment or users were affected and established the problem's extent. Include what you learned about checking reports.
Question 18: Provide a time when you successfully supervised and/or trained project team members.
Question 19: Describe an effective capital project program for new equipment or a major repair which you developed.
Question 20: Share an example of how you explained your design to electricians or technicians installing or modifying equipment under your supervision.
Example answerThe interviewer wants to learn how you make an electrical design clear to the electricians or technicians carrying out work you supervise.
Build the answer using Situation, Task, Action, Result. Name the equipment and the installation or modification. Explain your responsibility, how you communicated the design and how you checked the crew's understanding. Finish with the result and something you learned about giving clear instructions.
For example: "During a control panel modification I oversaw, the technicians were unsure how my wiring changes fit the existing terminal layout. I walked through the drawing with them at the panel and pointed out the connections being changed. I asked them to walk me through the planned connections so we could catch misunderstandings. That exposed an unclear label, which I corrected before they continued. The completed wiring matched the revised drawing. I learned to review labels against the actual equipment before briefing the crew."
Avoid assuming that handing over drawings is enough, blaming the crew for unclear instructions, or leaving out your own role in explaining the design.
Interviewer tipA strong example shows clear explanations of the equipment design, checks of the crew's understanding and a result. Expecting electricians or technicians to guess at unclear instructions is a red flag.
Candidate tipName the equipment and the crew, then focus on how you explained your design and checked their understanding. Include the result and a lesson for your next installation or modification.
Question 21: Tell me about a time you had to tell a project manager or client that a design would not meet the schedule, budget or a code requirement.
Example answerThe interviewer wants to know whether you raise problems early and honestly, with facts and options, even when the news is unwelcome. Use Situation, Task, Action, Result. Describe what you found and when, who needed to know, how you told them, and what was decided. Sample answer: "While finishing load calculations for a clinic renovation, I found the existing electrical service could not support the new imaging equipment. A service upgrade would add cost and weeks of utility coordination. I told the project manager the same day, with my calculations and three options: upgrade the service, phase in the equipment, or choose lower-demand units. We met with the client that week. They chose the upgrade and revised the opening schedule. I documented that decision, updated the design assumptions and identified the utility coordination still needed." Pitfalls to avoid: waiting until you have a perfect answer before speaking up, presenting the problem without any options, and making the story about blame instead of what you did.
Interviewer tipA strong answer brings the bad news early, with the facts and options ready. Waiting until the deadline or blaming others is a red flag.
Candidate tipSay what the problem was and how you found it, how and when you raised it, and the options you offered. End with what the team decided and what happened.
Question 22: Tell me about a time you learned a new design tool, standard or technology and used it on an electrical project.
Example answerThe interviewer wants to see that you keep your skills current and can apply new knowledge carefully on real projects. Use Situation, Task, Action, Result. Say what you needed to learn and why, how you learned it, how you checked your work, and what it changed. Sample answer: "Our team switched to a new power system analysis program for short-circuit and arc flash studies. I took the vendor's online course, then rebuilt a study we had already done by hand so I could compare results. Where the numbers differed, I traced the cause to how I had modeled transformer impedance and fixed my setup. Before applying the tool on the next project, I checked its equipment models and calculation settings with a senior engineer. I documented the inputs and comparison results and wrote a short setup guide for colleagues." Pitfalls to avoid: listing tools without showing how you used one, skipping how you verified results from something new, and claiming an improvement you did not verify. Keep the example to what you really did.
Interviewer tipListen for how they learned it, how they checked their results, and the effect on the project. Vague claims of being a fast learner with no example are a red flag.
Candidate tipPick one tool, code edition or technology and say why you needed it and how you learned it. Then describe how you applied it and what it improved, such as accuracy or time.
Question 23: Share an experience in which your attention to detail and thoroughness had an impact on your last company.
Example 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 24: Provide an example when your ethics were tested.
Example 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 25: Share an experience in which your diligence of inspecting equipment, structures, or materials helped you identify a problem or the cause of a problem.
Example answerThe interviewer wants evidence that you inspect carefully and that your checks catch problems before they grow.
Use Situation, Task, Action, Result. Say what you were inspecting and why, what you noticed, how you traced the cause, and what happened after you reported or fixed it.
Sample answer: "During a routine walk-through, I noticed a small puddle of fluid under one of our machines. It wasn't on the checklist, but I wiped it up and checked again an hour later, and it was back. I followed the line and found a fitting that had worked loose. I tagged the machine, reported it to my supervisor, and maintenance replaced the fitting before the end of the shift. If it had failed during a full run, we would likely have lost most of a day."
Pitfalls: Don't claim you never miss anything. Avoid stories where you found a problem but didn't report it. Don't skip how you confirmed the cause.
Question 26: Share an experience in which you conducted a test of a product, service, or process and successfully improved the quality or performance.
Example answerThe interviewer wants evidence that you test things carefully and use what you find to make them better.
Use Situation, Task, Action, Result. Explain what you tested and why, how you set up the test, what the results showed, and what you changed. End with how you measured the improvement.
Sample answer: "Customers kept saying our online order form was confusing, so I was asked to look into it. I had five coworkers who had never used the form place a test order while I watched and took notes. Four of them got stuck on the same shipping step. I suggested moving that step and rewording two labels, then ran the same test again. All five finished without help, and complaints about the form dropped over the next month."
Pitfalls: Don't describe a change made on a hunch with no test. Avoid skipping how you checked the result. Don't use jargon without explaining it.
Question 27: Provide an experience in which you successfully corrected a power system problem. How did you identify the problem?
Question 28: Tell me about a time when you successfully determined the cause of an operating error at your company and solved the problem.
Example answerThe interviewer wants to see how you track down the real cause of a problem instead of treating only the symptoms.
Use Situation, Task, Action, Result. Describe the error and its impact, the steps you took to narrow down the cause, the fix, and what you did to keep it from happening again.
Sample answer: "Our label printer started putting the wrong dates on some product labels, which meant those items had to be pulled from the shelves. I checked the printer settings first, and they were fine. Then I compared the bad labels and saw they all came from orders entered after a software update. The update had changed the date format in one field. I worked with our IT contact to fix the setting, reprinted the labels, and added a quick label check to our start-of-shift routine."
Pitfalls: Don't stop at the first fix that seemed to work. Avoid blaming coworkers. Don't leave out how you prevented a repeat.
Question 29: Share an effective method you have used to ensure conformance to design and equipment specifications and compliance to standards.
Question 30: 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.
Example 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.
New to interviews? Start with the common questions every interview asks →