What Electrical Engineering Interviews Are Actually Testing For
Electrical engineering interviews at any employer type are testing two things at once: whether you actually understand the fundamentals well enough to reason through a problem you haven't memorized the answer to, and whether you can communicate that reasoning clearly to a non-specialist (a project manager, a client, an inspector) as well as a fellow engineer. Strong candidates lose points less often on knowing the material and more often on giving a vague or memorized-sounding answer instead of demonstrating actual reasoning. The examples below show the difference.
Technical Fundamentals: Three-Phase Power
Likely question: "Explain why three-phase power uses a factor of √3, and what changes between a wye and delta connection."
Weak answer: "You multiply by root 3 for three-phase calculations."
Strong answer: "√3 comes from the phasor relationship between two of the three phase quantities that are 120° apart, not from the number three itself. In a wye connection, line voltage is the phasor difference between two 120°-apart phase voltages, which works out to √3 times the phase voltage — so a 277V phase-to-neutral system gives you 480V line-to-line. In a delta connection, it's the reverse: line voltage equals phase voltage directly, because each winding is connected line-to-line, but line current is √3 times phase current, since line current is now the phasor sum of two winding currents 120° apart. So the √3 factor always shows up on whichever quantity — voltage or current — is a phasor combination of two winding-level quantities rather than a direct measurement of one." This answer demonstrates you understand where the constant comes from, not just when to apply it — which is exactly the kind of reasoning an interviewer is trying to surface.
Technical Fundamentals: Grounding vs. Bonding
Likely question: "What's the difference between grounding and bonding, and why does it matter?"
Strong answer approach: Define both precisely — grounding connects a system or equipment to earth (for voltage stabilization relative to earth and for a path for lightning/surge energy); bonding connects metal parts together to ensure they're all at the same electrical potential, specifically so that a fault current has a low-impedance path back to the source to trip protection quickly. Then give the concrete safety consequence: without proper bonding, a fault on one metal enclosure could energize it relative to another nearby metal surface, creating a shock hazard between two things a person could simultaneously touch — bonding is what prevents that voltage difference from existing in the first place, and grounding alone (without bonding) doesn't guarantee it.
Technical Fundamentals: Transformer Basics
Likely question: "Walk me through how a transformer's turns ratio relates to voltage and current, and what determines its rated kVA."
Strong answer approach: State the turns ratio relationship for both voltage (directly proportional to turns ratio) and current (inversely proportional, since power in equals power out for an ideal transformer). Then go a level deeper than the basic ratio: explain that rated kVA is a thermal limit tied to how much current the windings can carry continuously without exceeding their insulation temperature rating — not a hard power limit in the way a breaker's trip rating is a hard current limit — and connect this to why K-factor derating exists for harmonic-heavy loads (additional eddy current heating beyond what standard RMS current alone predicts).
Technical Fundamentals: Protection Coordination
Likely question: "What does 'coordination' mean in protective device selection, and why does it matter?"
Strong answer approach: Define coordination as ensuring that when a fault occurs, only the protective device closest to the fault (upstream of the fault, downstream of the source) operates to clear it — leaving the rest of the system energized rather than tripping upstream devices unnecessarily and taking down more of the facility than the fault required. Then demonstrate depth by mentioning time-current curves: coordination is verified by plotting the time-current characteristics of series devices and confirming adequate time separation between them across the full range of possible fault currents, not just at one operating point. A strong candidate will also mention the tension between coordination and arc flash reduction — faster-tripping settings reduce incident energy but can compromise coordination margins, and real designs often have to balance the two rather than purely optimizing one.
Behavioral: A Design Change Mid-Construction
Likely question: "Tell me about a time a design had to change after construction had already started."
What interviewers are actually evaluating: not whether the change was your fault, but how you handled the discovery, the communication, and the resolution. A strong answer follows a clear structure: what the original design assumed, what was discovered in the field that conflicted with it (a utility conflict, an unexpected structural condition, a code interpretation that differed from what was assumed at design time), how you assessed the impact (cost, schedule, and any safety implications), how you communicated the change to the relevant parties (contractor, client, AHJ if applicable), and the outcome. Avoid framing this as "the contractor made a mistake" or "the original design was wrong" in a way that assigns blame rather than showing problem-solving — interviewers are listening for professionalism and ownership as much as technical judgment.
Behavioral: A Code-Compliance Disagreement With an AHJ
Likely question: "Describe a situation where you disagreed with an inspector or authority having jurisdiction on a code interpretation."
What interviewers are actually evaluating: your ability to hold a technically defensible position while still being professional and collaborative — not whether you "won" the disagreement. A strong answer shows that you researched the specific code section thoroughly, understood the AHJ's concern rather than dismissing it, and worked toward a resolution — whether that meant providing additional documentation that satisfied the AHJ's interpretation, proposing an alternative approach that met the intent of the code, or, in cases where you were genuinely wrong, updating your own understanding. Answers that come across as adversarial toward inspectors are a red flag for interviewers, since working productively with AHJs is a routine and important part of the job.
What Utilities Tend to Emphasize
Utility interviews often weight system-level thinking heavily: protection coordination across a distribution or transmission network, reliability metrics (SAIDI/SAIFI awareness), grid codes and interconnection standards, and questions about how a single component failure propagates through a larger interconnected system. Utilities also frequently probe safety culture specifically — expect direct questions about NFPA 70E, arc flash awareness, and lockout/tagout, since utility work involves live systems at a scale where mistakes have severe consequences.
What Consulting Firms Tend to Emphasize
Consulting interviews weight client communication and multi-discipline coordination more heavily — expect questions about working with architects, mechanical engineers, and clients with limited technical background, and about managing competing constraints (budget, code compliance, aesthetic or space requirements from other disciplines). Technical breadth across many building types (rather than deep specialization in one system) is often valued more than at a utility, since a consulting engineer typically works across a wider range of project types.
What Contractors Tend to Emphasize
Contractor-side interviews (whether for an EC's engineering staff or a design-build role) weight practical constructability and field-awareness heavily — expect questions about how a design decision affects installation cost and schedule, familiarity with actual installed products and lead times, and questions that test whether you understand the difference between what's technically correct on paper and what's actually practical to build. Direct field experience or willingness to visit job sites regularly is often valued more explicitly here than in a pure design role.
Preparing Your Own Questions
Strong candidates ask questions that show genuine engagement with how the specific employer operates: what a typical project timeline looks like from design through commissioning, how the team handles code interpretation disputes with AHJs, what tools (calculation software, drafting platforms, power system analysis tools like ETAP) the team uses day to day, and how professional development toward a PE license is supported. Avoid questions whose answers are easily found on the company's public website — they signal you didn't do basic preparation.