Electrical Engineer Resume Examples & Writing Guide

This is a mid-level resume for a licensed electrical engineer at a consulting firm that designs power distribution for commercial and industrial buildings. The name and firms are made up. Notice that the license sits next to the name, each project has a size, and the software and codes are named exactly. That is what an engineering manager scans for in the first pass.

Electrical engineering is broad. A manager hiring for power distribution does not want a PCB designer, and a controls team does not want a substation engineer. Say which kind of electrical engineer you are in the first three lines. Four things decide whether you get a call.

• License status. PE, EIT (FE passed) or neither. Consulting and utility roles often require a PE or a path to one; product and controls roles usually do not, but they still notice it.
• Domain and scale. Power distribution, utility and renewables, controls and automation, electronics and embedded hardware, or building systems. Then the size: kV and MVA, square feet and construction value, number of I/O points, boards shipped, units in production.
• Software and codes, spelled exactly. Revit MEP, ETAP, SKM, AutoCAD Electrical, Studio 5000, TIA Portal, Altium, MATLAB/Simulink, LTspice. Codes and standards: NEC, NFPA 70E, IEEE 1584, IEC 61131, UL 508A. Recruiters search for the exact string.
• Ownership. Did you run a project, sign drawings, own a subsystem, lead commissioning, or support someone who did? "Assisted with" on every bullet reads as junior regardless of your years.

“The first pass takes about fifteen seconds: license letters after the name, then the domain, then the software list. If a power engineer tells me the voltage class and the biggest service they have designed, the interview is half decided. The resumes that lose are the ones that list twenty tools and never say what they built with any of them.”

Your summary is where you state your domain, your license status, your years and the largest thing you have designed. Four lines maximum. Use an objective only as a new graduate or when changing domain (for example, from utility work to controls), and keep it about what you bring.

Engineering resumes often list responsibilities in the words of the job posting ("designed electrical systems", "performed calculations"). Managers want the scale, the standard you designed to, the tool and what your work changed.

Group the skills section into three short lists: engineering skills, software, and codes and standards. Twelve to sixteen items total. Match the list to your domain; a power engineer does not need to list Altium, and a hardware engineer does not need the NEC.

• Power and building systems: load calculations, feeder sizing, short-circuit and coordination studies, arc-flash analysis, grounding, emergency power, lighting design. Software: Revit MEP, AutoCAD Electrical, SKM PowerTools, ETAP, AGi32. Codes: NEC (NFPA 70), NFPA 70E, NFPA 99, NFPA 110, IEEE 1584, IEEE 80, IECC.
• Utility and renewables: protection and relay settings, substation and collection system design, power flow, interconnection studies. Software: ETAP, PSS/E, PSCAD, CYME, AcSELerator. Standards: IEEE C37, IEEE C57, IEEE 1547, UL 1741, NESC.
• Controls and automation: PLC programming (ladder, structured text), HMI and SCADA, control panel design, motor control and VFDs, functional safety. Software: Studio 5000, TIA Portal, FactoryTalk View, Ignition, EPLAN. Standards: UL 508A, NFPA 79, IEC 61131-3, ISO 13849.
• Electronics and hardware: schematic capture and PCB layout, power supply design, mixed-signal design, signal integrity, EMC. Software: Altium Designer, KiCad, LTspice, MATLAB/Simulink, Python. Standards: IPC-2221, IPC-A-610, CISPR, IEC 61000.

Copy the exact tool names from the posting. "Revit" and "Revit MEP" are searched differently, and so are "Studio 5000" and "RSLogix 5000". Use the posting's version.

In the US, engineering licensure runs through your state board and the NCEES exams. Employers read your license line carefully, so write it exactly. The wording below is standard; adjust to your state's title (some states say "Engineer Intern" instead of "Engineer in Training").

• PE: required to sign and seal drawings and to be the engineer of record. Consulting firms (MEP, utility, transportation) treat it as required for senior roles and strongly preferred at mid-level. The typical path is FE exam, then 4 years of experience under a PE, then the PE exam and a state application; a few states allow the PE exam earlier. Requirements vary by state, so check your board.
• EIT: tells employers you have passed the FE and are on the licensure path. List it even in product or controls roles; it costs you nothing.
• Not a license but worth listing: NFPA 70E training, OSHA 10 or 30, PMP (project engineer roles), LEED AP (building design), ISA Certified Automation Professional (controls), and vendor PLC courses with the course name and year.

"No experience" for a new BSEE graduate means no full-time engineering job yet. You still have a senior design project, labs, possibly an internship or co-op, and the FE exam. Entry-level postings are written for exactly that. Managers hiring new graduates want to see that you can finish a design, use the standard tools and pass the FE. Keep it to one page.

1. 1Header with FE status. "EIT" after your name once your state issues it; otherwise "FE Electrical and Computer passed, May 2026" on the first line under your name.
2. 2Objective, 3 lines: degree and date, FE status, your emphasis (power, controls, electronics), your strongest project and the type of role you want.
3. 3Education near the top: degree, ABET accreditation, school, graduation date, GPA if 3.3 or higher, and 4 to 6 relevant courses only if they signal your emphasis (power systems analysis, power electronics, control systems, embedded systems).
4. 4Projects section, written like jobs: name, what it did, your part, tools and standards, the result. Senior design counts as your first engineering project. Two to four projects.
5. 5Internships and co-ops with the same detail as a job. If you have none, include technician, electrician or lab assistant work and any teaching assistant role.
6. 6Skills: the software you have actually used for a full project, plus the lab equipment you can run (oscilloscopes, spectrum analyzers, power analyzers). Then certifications (FE, OSHA 10, NFPA 70E if you have them).

Engineering firms and utilities almost all use an applicant tracking system (Workday, Taleo, iCIMS), and recruiters search it by exact keyword. Format for the parser first and the manager second.

• Length: one page up to about 5 years of experience; two pages for licensed engineers with many projects or for principal and lead roles. A project list beyond that belongs in a separate portfolio or statement of qualifications.
• Order: header with license letters, summary, skills (grouped), experience, education, licenses and certifications. New graduates put education and projects above experience.
• No photo, no date of birth, no citizenship line unless the posting requires work authorization or clearance status, in which case one line ("US citizen, eligible for DOE Q clearance") is normal.
• One column, standard fonts, no text boxes or tables for the skills list; parsers drop them. Save as PDF unless the portal asks for Word, and name the file Priya-Natarajan-PE-Resume.pdf.
• Keywords to mirror from the posting: the domain words (power distribution, protection, controls, embedded), the exact software names, the codes and standards they list, the voltage class or product type, "PE" or "EIT", and the industry (healthcare, data center, utility, automotive).

Outside the US, the document is called a CV in the UK, Ireland and India, and UK employers look for IEng or CEng registration with the Engineering Council instead of a PE. Keep the same structure and swap the license line. Then run the file through the cvplex ATS checker with the posting pasted in; it flags a software name or code you left out and any layout the parser cannot read.