I recently earned my PE in Power, and I am trying to understand the real-world value chain behind what I learned.
I do not mean, “What jobs can a PE get?” I mean: where does the material on the PE Power exam turn into a client problem that someone will pay an engineer to solve?
My background is in a niche area of electrical engineering, so I have not spent years doing commercial power design, utility work, industrial power systems, or MEP consulting. I know the technical material: NEC concepts, transformers, synchronous and induction machines, per-unit systems, fault calculations, symmetrical components, three-phase faults, line-to-ground and line-to-line faults, protection concepts, basic ladder logic, load calculations, and so on.
The issue is that I understand these as engineering topics and calculations, but not yet as products or services.
I also do not fully understand what people mean when they say they “design” an electrical system.
When I look at a real set of electrical drawings, floor plans, one-line diagrams, panel schedules, equipment schedules, wiring diagrams, and specifications, it looks very different from anything I saw on the PE exam. I do not yet understand how an engineer goes from a client saying, “I need power for this building/facility/equipment,” to a completed design package that a contractor can build from.
What is the actual workflow? What is it that I know (PE Power exam knowledge) that they need from me is my biggest question?
- What information does the client provide at the beginning?
- What does the engineer need to determine, select, calculate, or coordinate?
- What industry software is typically used?
- What does the final deliverable look like?
- Is it drawings, a one-line, equipment schedules, load calculations, a short-circuit study, protective-device coordination study, arc-flash labels/report, relay settings, construction specifications, or some combination?
- What is stamped, and what is the engineer actually taking responsibility for?
- What makes the result valuable enough that a client will pay professional consulting rates for it?
For example:
- When does a client actually need a three-phase, line-to-ground, or double-line-to-ground fault calculation?
- What decision does that calculation support?
- When are per-unit calculations used in real work versus buried inside software?
- Where do transformer, motor, protection, and NEC knowledge show up in an actual project?
- Which types of clients buy this work: industrial facilities, commercial buildings, utilities, data centers, manufacturers, contractors, renewable-energy developers, etc.?
I see experienced EE Power PEs on reddit charging high hourly rates, and I assume clients are not paying because someone can solve a per-unit problem or merely provide a stamp. They are paying for a defensible answer to an expensive problem: safety, equipment ratings, code compliance, reliability, utility requirements, construction documents, liability, or avoiding downtime.
That is the connection I am trying to understand and I honestly, even after receiving my license, don't know what it is.
I am frustrated because I worked hard to learn this material and can apply it in an exam setting, but I do not yet see the bridge between that knowledge and a real consulting deliverable. I want to build that bridge the right way, not rent out a stamp or take work outside my competence.
If you work in power consulting, industrial power, utility engineering, MEP, protection and controls, or forensic/electrical consulting, I would really appreciate a concrete example of a normal project that actually uses the material which NCEES tested you on:
- What was the client’s problem?
- What did the engineer actually design or analyze?
- What inputs, calculations, and software were used?
- What did the final deliverable look like?
- What decision, risk, or cost did it address for the client?
- What experience would a newer PE need before taking on that type of work independently?
I would especially appreciate examples of the first types of projects a newer PE can responsibly grow into.