How to write an electrical engineer resume
Updated 2026-09-02

An electrical engineer’s resume is measured in numbers that moved: efficiency from one figure to another, a certification passed on the first submission, a failure mode that never came back, a plant energized on the date in the schedule. The person reading it has calculated fault currents and signed single-line diagrams, and looks for three things: the system or product family in your name, its scale in kW, MW or units shipped, and what you changed to move the number. A row of standard numbers and software names with no system behind it answers none of the three.
This page is about power, industrial and plant work, not consumer boards. A hardware engineer proves the case with shipped boards and DPPM, and has a page of that name; an electrical engineer proves it with a drive’s efficiency curve, a switchgear FAT record, relay settings that held on the trip test, and the first-submission line on a UL or IEC report. The moves are well worn: from a power-supply or drive maker into an automation group or an automotive tier one, from plant electrical into an offshore wind developer or EPC, from storage and charging into an energy company. All three readers read English, so every example here is English, and every figure stays [N]: the efficiency and the losses must be values from your own measurement report.
The first sentence also has to settle your lane: power conversion, industrial controls, plant electrical, or certification and test. Electrical openings are split along those four lines, and a resume that stands in none of them is routed to none of them. Below: section order, three summary levels, bullets by competency, weak lines rewritten, what to keep in Skills, ATS keywords, the mistakes particular to this role, and the follow-up each claim invites.
What a finished one looks like
Below is a complete sample for a fictional person, rendered as a real page by the product's own sheet and scored by the same rules engine the editor uses — the number is computed, not typed in. Every figure a bullet owes is left as [N], which is why the score stops under the cap. That is not a flaw in the example; it is the product's rule, demonstrated.
Yi-Hsuan Chang
Education
- Built a [N] kW bidirectional DC-DC converter for the department’s solar-storage testbed as the senior project, measuring within [N]% of its SPICE model at full load
- Won the department’s senior-project award, one of [N] selected from [N] entries that year
Experience
- Owned the [N] kV inter-array collection design for a [N] MW offshore wind farm, sizing cables, switchgear and earthing for [N] turbines and carrying the package through the grid operator’s review without a resubmission
- Halved the electrical punch-list at substation energization, against the previous project, by running a factory acceptance test on every switchgear panel against the single-line diagram before it shipped to site
- Delivered protection and control commissioning of the onshore substation [N] days ahead of first power, writing the relay settings for [N] feeders and witnessing every trip test
- Cut collection-grid losses by [N]% by re-sequencing the turbine strings and moving [N] turbines onto a larger conductor after a load-flow study in PSCAD
- Designed the power stage and gate drive of a [N] kW three-phase industrial motor drive that shipped [N] thousand units, lifting full-load efficiency from [N]% to [N]% with a SiC half-bridge and a laminated DC-link
- Secured UL 508A and IEC 61800-5-1 certification for the drive family on the first submission by closing every creepage-and-clearance finding at schematic review, before a sample reached the test lab
- Eliminated a field failure that had been returning [N] units a month by tracing DC-link capacitor overheating to ripple current at low motor speed and releasing a bus-bar revision that cut the ripple by [N]%
- Doubled end-of-line test throughput by building a regenerative load bench that returned the drive’s output power to the grid instead of burning it in resistor banks
Projects
- Created a Python derating tool that derives a drive’s continuous-current rating from heatsink temperature and altitude, which the applications team now uses in place of the [N]-page derating tables
Additional Information
Structure and section order
One column, standard headings, plain text, no photograph. The first reader is a parser and the second is an electrical manager who has signed drawings; neither rewards layout. Single-line diagrams and cabinet photographs belong behind a portfolio link, not on the sheet.
The ordering rule: the product and plant record leads. The drives, switchgear and distribution systems in your name, and what happened to their numbers while they were yours, are the body of the resume; the other sections make room. Entry-level candidates put the project converter and the commissioning they shadowed in the same seat.
- 1Summary
Three sentences: your lane (power conversion / controls / plant electrical / certification), the power class you work at (kW or MW), and the one figure you can defend hardest. The electrical manager decides from this paragraph whether you are the kind of electrical engineer the opening wants.
- 2Experience
Reverse chronological, one entry per product family or site: the system you owned, its power or scale, efficiency or losses before and after as [N], one certification or one energization. This section owns most of the page.
- 3Project and Commissioning Record (optional)
One line each: year, system class, power class, your role, energization date against plan. Every row is a question you are volunteering to answer, so keep only the rows you can.
- 4Skills
Grouped by function: power and system design, simulation and calculation, standards and certification, controls and site. A cross-reference to the posting, not a transcript of your coursework.
- 5Certifications
One line each for a PE or chartered status, a vendor PLC certification, a high-voltage switching authorization. Abbreviations are what the parser matches, and for plant roles they are the door.
- 6Education
A bachelor’s degree is the baseline; a master’s in power electronics or power systems helps. Entry-level candidates lead with the project converter and relevant coursework. After the first plant is energized, this shrinks to two lines at the bottom.
Summary examples by level
The summary is a ten-second routing decision for the electrical manager: your lane, your power class, one number. One example per level, figures left as [N] for you to fill.
Electrical engineering graduate who built a [N] kW bidirectional DC-DC converter for the department’s solar-storage testbed, measured within [N]% of its SPICE model at full load, and spent a [N]-month internship writing relay settings for a plant’s [N] kV feeders under a licensed engineer. Comfortable with PLECS, ETAP and a power analyzer. Looking for a power-electronics or plant-electrical seat where the first assignment is a real efficiency or commissioning target.
The evidence at entry level is a converter that was actually measured and a set of relay settings you followed under a signature: the power class, the gap between measurement and model, the slice you owned. That converter can carry an hour of questions.
Electrical engineer with [N] years in power conversion and plant electrical systems, owning a [N] kW industrial motor-drive family from topology selection through UL 508A and IEC 61800-5-1 certification, then the [N] kV collection grid of a [N] MW offshore wind farm from load-flow study to energization. Increased drive efficiency by [N] points with a SiC power stage, and closed substation commissioning [N] days early. Prefers owning a system end to end: calculation, drawing, factory test, site test.
Mid-career routing needs all four facts: lane, power class, one certification, one energization. The last sentence describes a way of working. A system that stays in your hands from calculation to site test says more than an adjective.
Senior electrical engineer leading a [N]-person team across power conversion and plant electrical for a [N] MW energy-storage program, owning the single-line diagram, the protection philosophy and the grid-code compliance case. Cut certification retests to zero on the last [N] products by making a creepage-and-clearance review the schematic release gate, and holds every energization to a signed FAT-to-SAT punch-list. Writes down every derating decision so the next program starts from measured data.
Senior evidence is what got built into the process: a safety review that became the drawing-release gate, a signed FAT-to-SAT punch-list on every energization, derating decisions written down with their data. Nothing in it describes the person; all of it describes what the team does differently now.
Bullets grouped by competency
Every bullet has the same skeleton: a verb, then the system in your name, then the method, then an [N] outcome. Kilowatts and megawatts, efficiency points, first submissions and energization dates are how this role states scale. Whichever figure is missing stays [N].
Power conversion and drive design
· Designed the power stage of a [N] kW three-phase motor drive, moving from a Si IGBT six-pack to a SiC half-bridge and a laminated DC-link, which lifted full-load efficiency from [N]% to [N]% and let the enclosure drop one frame size.
· Redesigned the gate-drive and snubber network on a [N] kW solar inverter after field returns, cutting turn-off overshoot by [N] V and ending the IGBT failures that had come back at [N] units a month.
· Built a [N] kW bidirectional DC-DC stage for a battery energy-storage system, holding round-trip efficiency above [N]% across the [N] V to [N] V pack window with a variable-frequency control scheme.
· Cut the magnetics cost of a [N] kW onboard charger by [$N] a unit by merging three transformers into one planar design, validated in FEA before the first sample was wound.
Industrial controls and PLC
· Delivered the control system for a [N]-station automated line, writing the PLC logic, the safety circuit to ISO 13849 PL d and the HMI, and handing it to production [N] days ahead of the customer’s acceptance date.
· Resolved a nuisance-trip fault that stopped a packaging line [N] times a shift by tracing it to a floating analog ground in the drive cabinet and re-terminating the shields at one end.
· Migrated [N] legacy relay-logic panels to a PLC and networked drives on Modbus TCP over scheduled weekend windows, with zero unplanned line stops attributable to the changeover.
Plant electrical and power systems
· Owned the [N] kV distribution design for a new [N] MW plant, running the load-flow, short-circuit and arc-flash studies in ETAP and sizing [N] MCCs and the main switchgear so the utility connection was approved on the first submission.
· Cut the plant’s peak demand charge by [$N] a year by staging [N] chillers and compressors on a demand controller and correcting power factor to [N] with a detuned capacitor bank.
· Defined the relay settings and coordination study for [N] feeders of an onshore substation, then witnessed every trip test at site acceptance so the first-power date held.
Certification, compliance and safety
· Secured UL 508A and IEC 61439 certification for an industrial control-panel line on the first submission by closing every creepage, clearance and short-circuit-rating finding at schematic review rather than at the test lab.
· Eliminated a conducted-emissions failure at [N] kHz on a [N] kW drive by moving the EMC filter onto the enclosure wall and shortening the motor-cable pigtail, so the family cleared IEC 61000-6-4 at the first test-lab booking.
· Built the grid-code compliance case for a [N] MW storage inverter against IEEE 1547 and the local ride-through rules, running [N] fault-ride-through cases in PSCAD and matching the field test within [N]% on reactive-current response.
Commissioning, energization and failure analysis
· Delivered energization of a [N] MW plant’s main switchgear on the scheduled date by running a FAT on every panel against the single-line diagram, which halved the site punch-list against the previous project.
· Eliminated a repeat DC-link capacitor failure on a fielded drive family by tracing it to ripple current at low motor speed rather than the supplier defect the returns had been booked as, and released a bus-bar revision that cut the ripple by [N]%.
· Led the commissioning of [N] MW of rooftop solar across [N] sites in one quarter by writing the test procedure once and training [N] site technicians to run it, with every site accepted by the utility on the first inspection.
· Doubled end-of-line test throughput on the drive line by building a regenerative load bench that returned output power to the grid instead of dissipating it in resistor banks, cutting the test bay’s energy bill by [N]%.
Before and after
The same experience written weakly and then well. Weak electrical writing has fixed patterns: a standard number in place of a result, the whole plant in place of your system, and no line between the contractor’s work and yours.
Responsible for electrical design of industrial drives.
Owned the power stage and gate drive of a [N] kW industrial drive family from topology selection to UL 508A certification, shipping [N] thousand units with a first-year field-return rate under [N]%.
Why it works · “Responsible for” names the seat. The rewrite has a product family, a power class, the slice you owned, and two checkable facts: a certification and a return rate.
Familiar with UL, IEC and NEC standards.
Closed [N] creepage-and-clearance findings at schematic review so a control-panel line passed UL 508A and IEC 61439 on the first submission, saving one [N]-week retest cycle.
Why it works · A row of standard numbers proves you have heard of them. The rewrite shows what you decided with the standard, at which stage, and what it saved.
Improved the efficiency of the inverter.
Increased full-load efficiency of a [N] kW solar inverter from [N]% to [N]% by replacing the Si IGBT stage with SiC and re-winding the boost inductor on a lower-loss core, verified on [N] units with a calibrated power analyzer.
Why it works · “Improved” gives no before, no after and no method. The rewrite has both figures, the change that produced them, the instrument and the number of units measured. Every part can be probed.
Worked on the electrical installation of a new factory.
Owned the [N] kV distribution design for a [N] MW plant, from load-flow and arc-flash studies in ETAP to the FAT of [N] switchgear panels, and energized the main board on the scheduled date.
Why it works · “Worked on” is spectator language. The rewrite carries a voltage class, a power class, the studies and tests you ran, and the date that held. Each is a question you can answer.
Coordinated with contractors and the utility to complete the project.
Drove the utility interconnection review for a [N] MW site to approval on the first submission by delivering the protection-coordination study and the IEEE 1547 compliance package [N] weeks before the milestone.
Why it works · “Coordinated” shows no decision. The rewrite names the documents you delivered, the reviewer’s verdict and when. Work with the utility or a contractor is written as the calculations and drawings you handed over, not as attendance.
What belongs in the skills section
Your interviewer has calculated fault currents and signed drawings. Every term here has to survive the question: what did you decide with it?
Worth the space
Power-electronics topology · Motor drives & inverters · Magnetics design · Protection & coordination · Earthing & lightning protection
PLECS · LTspice · ETAP · PSCAD · Ansys Maxwell · MATLAB/Simulink
UL 508A · IEC 61439 · IEC 61800-5-1 · IEEE 1547 · IEC 61000 · NFPA 70E / arc flash
Siemens TIA Portal · Rockwell Studio 5000 · IEC 61850 / Modbus · FAT / SAT · Relay testing · Python
Cut these
- Every standard number you have ever read · A number proves you have heard of it, not that you decided anything with it. Keep the ones you submitted against and signed reports for; delete the rest.
- Office suites and generic CAD · They match nothing and dilute the terms that do. AutoCAD Electrical or EPLAN stays if you actually issued drawings in it; Word does not.
- Sentences that begin “Familiar with” · Familiarity says you touched it. Evidence in this role is a product whose efficiency you measured or a plant you energized, and that belongs in Experience.
- Power, controls, plant and certification all at once · A little of everything reads as no lane. Show the square you stand in first, and give the rest as a ratio.
- Customer names and unannounced sites · Offshore wind farms and tier-one platforms are mostly under NDA. Write the class and the scale: a [N] MW offshore wind farm for a European developer.
ATS keywords
The terms on the posting are matched one by one before a person reads anything. These are the ones electrical openings commonly match, by category.
List only terms you have calculated with, tested against, or signed for. An electrical manager’s follow-ups all take the form “how did you arrive at that value”, and one keyword you cannot hold hurts more than a blank. Stacking keywords earns nothing from the parser and reads as a paragraph of noise to the person after it.
Registers, certificates and the drawings you cannot send
There is no portfolio link on an electrical resume. What happens after the reader finishes your Experience section runs in a fixed order: the register gets checked to see whether the licence you claim exists, the certification database gets searched for the UL or IEC certificate under the maker and model you named, and then your patents and site qualifications get looked at to see whether they are still in date. All three sit off the page. The resume’s only job is to point at them accurately, and pointing at something that cannot be found costs you more than leaving it out.
- The licence: the register is public, so write it the way the register reads
This is one of the few engineering resumes where the reader looks you up. In the US the PE is issued by a state board, and every board publishes a licence lookup. In the UK, CEng sits on the Engineering Council register and is assessed through an institution such as the IET. In Taiwan the electrical engineering professional exam earns the certificate, and practising takes a separate practising licence on top of it. Write the entry as the register writes it: full title, the state or country that issued it, the year — Professional Engineer (Electrical), Taiwan. Leave the certificate number off. Your name is enough to find the record, and the paper belongs at the stage where someone asks for the original.
- Passing, registering and practising are three different things — say which one you are at
The US path is the FE exam, then supervised experience, then the PE exam, and most states call the middle stretch EIT. “Passed the FE exam (Electrical and Computer); accruing supervised experience toward PE licensure” is honest, checkable, and costs you nothing. Writing PE when the board’s lookup returns nothing is not read as a typo. The reader concludes you will round up on a fact that can be verified in ten seconds, which is the worst available conclusion about someone hired to calculate. The same goes for a CEng application still in assessment: write it as an application, with the institution it sits with.
- The UL or IEC certificate is public, and it is in your employer’s name
Claim a first-submission UL 508A and someone will go and find the certificate. UL’s Product iQ, the IECEE CB certificate search and the certification bodies’ own databases are open, and a maker plus a model number is all anyone needs. So write the boundary rather than the certificate. Name the standard and its edition, name the work that was yours — the creepage and clearance findings closed before drawings were issued, how the SCCR was arrived at, where the EMC filter finally went — and put yourself in the sentence with a role: “Took the [N] kW drive family through UL 508A and IEC 61800-5-1 on the first submission as the responsible design engineer.” Claim the whole certificate instead, and anyone in the industry can see you were not the person holding it.
- Site and safety qualifications expire, and an expired one belongs off the list
Plant, EPC and utility postings treat these as a gate rather than a bonus: NFPA 70E arc-flash and lock-out/tag-out training, first aid, high-voltage switching authorisation, the local wiring trade certificates. They share one property — they lapse, and retraining runs on a cycle. Write them with a date attached: “NFPA 70E arc-flash and lock-out/tag-out training, renewed [N].” When one has lapsed, take it out of Certifications and put the substance into Experience instead: you were trained to it, and you worked to it on a named kind of site. In front of a reader who will ask how you picked a PPE category, an expired safety card reads worse than a blank line.
- Patents and papers: write the status to the precision someone can check
Power-electronics work leaves patents behind, and patents are public — an inventor name in Google Patents or a national office finds them in a minute. Granted and pending are therefore not interchangeable. Say granted with a count, say pending with the filing year, and if you were a co-inventor, say co-inventor. Nobody cares about the ordering; everybody cares about the rounding. Conference work behaves the same way, since APEC, ECCE and PCIM proceedings are searchable by name. One line carries all of it: “Co-inventor on [N] granted patents and [N] pending applications covering gate-drive and DC-link design.”
- One-lines, relay setting files and switchroom photographs are the portfolio you must never send
Other roles attach the work. You cannot. The single-line diagram, the protection settings, the ETAP or PSCAD model and the photographs of the switchroom belong to the owner or the utility, and some of them touch site security. Emailing a former employer’s drawing to an interviewer ends the interview, because the reader has just watched the next person who will be sent your drawings. Do the other thing: redraw a generic one-line carrying no site information and use it to talk from at a whiteboard. On the page, keep the study and the scale — “Ran the load-flow, short-circuit and arc-flash studies in ETAP for a [N] MW plant” — and describe the site as a type. That whiteboard is this role’s portfolio review.
- With no licence and no patents, the evidence is the people who signed beside you
Most of the record in this work already carries a signature: the witness column on a FAT and SAT sheet, the utility’s interconnection approval, the engineer who reviewed the settings you wrote. Those people can confirm that the relay settings were yours and that you stood there through every trip test, which beats an attachment. Ask them first, then list them. If you want one public artifact of your own, publish a calculator built from public material — a derating or cable-sizing tool that works from datasheets and standard tables, with no figure in it lifted from an employer’s test report. And if the tool is half-finished, leave the link off. This reader will open it, put two sets of numbers through it, and judge how you calculate from what comes back.
Common mistakes on electrical engineer resumes
- 1A row of standard numbers with no product or plant in your name
UL 508A and IEC 61439 are numbers every electrical engineer has heard. What is yours is the product family or the plant: its power class, the slice you signed, what happened to its efficiency or its energization date.
- 2Wearing the whole plant’s scale as your contribution
“Worked on a [N] MW plant” describes the owner’s project. Write the system you owned: the distribution design, the relay settings, the switchgear FAT. A small scope written clearly beats the nameplate of an entire site.
- 3No line between the contractor’s work and yours
A hiring manager at an EPC or a developer knows how the work is divided, who drew which drawing and who ran which test. Write what you calculated, what you signed and what you changed on site. A contractor’s deliverables list pasted in is not a design.
- 4Efficiency and losses written as “improved”, with no figures or test conditions
“Improved efficiency” says nothing. Efficiency needs before and after as [N], the load point, the instrument and the number of units. If you cannot state the test conditions, the number is read as a simulation.
- 5Certification written as “passed”, with no stage and no finding
“Passed UL certification” credits the test lab. Write the findings you closed before the drawings were released, the retest cycles saved, and which submission passed. First time and third time are the same sentence on a resume and very different ones in an interview.
- 6No way to tell if you are power, controls, plant or certification
Electrical openings are finely split, and the reader routes before reading. The first sentence of the summary has to stand in one square; if you have worked in all four, give the ratio in years or in projects.
The follow-up each claim invites
Every follow-up in this field tests one thing: did you calculate and measure that number, or did a contractor or a test lab hand it to you? Before a claim goes on the page, think about the third question it leads to.
Increased full-load efficiency from [N]% to [N]% with a SiC power stage.
Where were the measurement points: input to output, with or without the fan and the auxiliary supply? Which load point? Which instrument, and when was it calibrated? How much of the gain is switching loss and how much is conduction loss?
Bring an efficiency curve you measured yourself: load points, instrument model, the number of units averaged. If you can split the gain into its parts and name the part you did not get, the number is yours.
Secured UL 508A certification on the first submission.
What did you review yourself before submitting? Which item came closest to failing? How was the SCCR calculated?
Bring your pre-review list: creepage, clearance, SCCR, marking. Naming the item that came closest to failing and how you closed it is more convincing than “first time”.
Energized the main switchgear on the scheduled date.
Which tests did you witness in person? What did the FAT catch, and what did the SAT catch after it? What was the last open punch-list item before energization, and how did you decide it was safe to proceed?
The evidence of an energization is the punch-list and the witness record. Prepare one call you made on site: which item was energized under a condition, how the risk was assessed, and how it was closed afterwards.
Eliminated a repeat DC-link capacitor failure.
Why had the returns been booked as a supplier defect for so long? How did you rule out a component lot against design margin? What changed, and how long did you track it afterwards?
Bring the return record before and after: units a month before the revision, months and units tracked after it. If you can say how you proved ripple rather than a lot, with the ripple current and the temperature rise you measured, the claim holds.
Cut the plant’s peak demand charge by [$N] a year.
How was the peak measured? What changed in the load schedule, and did production feel it? Did harmonics get worse after the power-factor correction?
Bring the demand curve and the utility bill from before and after. If you can name the loads that were staggered, how production agreed to it, and the harmonic measurements afterwards, the saving is yours.
FAQ
What changes when a power-supply or drive-maker resume is written for an automation group or an automotive tier one?
The grain of ownership and the language of standards. The habit at a component maker is product names and years of service; the reader wants your power class, the topology tradeoffs you made, the certifications you carried through. The word before every verb has to be you.
Second, standards written as evidence. A European reader reacts to IEC 61800 and EN 61439, but only to what you decided with them and at which stage. A list of numbers is not a record.
I have no offshore wind experience. Can I apply to a wind developer or an EPC?
Yes, if the distribution and power-systems evidence leads. Developers hire electrical engineers out of plant electrical, utilities and heavy-electrical manufacturers; they look for the fault currents you calculated, the protection you set, the switchgear you energized. The turbine has its own manufacturer.
Translate the onshore record into their vocabulary: MV distribution, substations, grid code, FAT and SAT. For the offshore part, write what you are prepared to learn, and do not pretend to have done it.
Efficiency and loss figures are confidential to my customer or my employer. Can I write them?
The change is safer than the absolute value: raised efficiency by [N] points places you for a peer without pointing at a model. Power class and unit volumes are usually fine; model names and customer names are not.
When unsure, leave [N] and give the figure out loud in the interview. You are the one keeping the secret, not the resume.
I only have a university project converter and a commissioning I shadowed as an intern. What can I write?
Write it as measured evidence, not as production or energization: the converter’s power, the efficiency you measured and its gap from the model, the slice you owned. A commissioning you shadowed is labelled as support; write the part you did with your own hands: the measurements, the settings you checked, the report.
At entry level the evidence is a machine that was actually powered, not the name of a course.
I do design, certification and site work in one job. How do I split them?
Pick the lane of the posting. For a design role, topology, efficiency and failure analysis lead, with certification and site compressed to a line or two; for a plant or EPC role, reverse it.
All three in one person is a rare combination, but each has to be its own bullet. A line that mixes design and commissioning gets discounted on both sides.
Write the plants you energized and the products you certified the way an electrical manager reads them
Describe your systems in plain language: the power class, efficiency before and after, the certification you secured, the plant and the date it was energized, the failure you eliminated. The Tech lens rewrites them into English at the level on this page. The 0–100 score comes from a rules engine, so the same draft always scores the same, and every missing efficiency figure or date stays a yellow [N] placeholder for you to fill from your own test reports.
Try 2 free drafts