Electrical engineer new grad resume example

By the Rezumed team · Updated November 3, 2026

A new grad electrical engineer resume should show that you can design a circuit, build it or lay out the board, and find out on the bench why it doesn't work yet. Each bullet should name the hardware, the tool or instrument, and what you found.

What hiring teams look for

The Bureau of Labor Statistics says electrical and electronics engineers "design, develop, and test electrical and electronic equipment, components, and systems". Electrical engineers work on equipment such as electric motors, communications systems or power generation equipment; electronics engineers "design and develop the components and circuitry of electronic products". Listed duties include determining product or system requirements, using design software to create models, diagrams and layouts, testing reliability and safety, and preparing documentation. They typically need a bachelor's degree in electrical engineering, electronics engineering or a related engineering field.

Two important qualities BLS lists shape this resume. Under computer skills, it says these engineers "need a working knowledge of programming languages". Under problem-solving skills, it says they "must troubleshoot issues that arise in designing products and systems". So hiring teams look for a board you designed, a fault you tracked down on the bench, and code that runs on hardware.

Sample resume

Sample resume (fictional)

Nathan Pryor
Austin, TX · nathan.pryor@example.com · (512) 555-0129 · github.com/your-handle
Education

B.S. Electrical Engineering, Thornbury Technical University · May 2026

GPA 3.5 · Coursework: Electrical Circuit Theory, Digital Systems Design, Electronics I and II, Signals and Systems, Embedded Systems, Power Electronics

Experience

Electrical Engineering Intern, Hardware Test, Veltrix Motion Controls · Austin, TX · May to August 2025

  • Tested 25 motor controller boards against the production test procedure and wrote failure reports for the four that failed
  • Traced a reset fault on a prototype board to an undersized pull-up resistor with an oscilloscope; the fix went into the next revision
  • Wrote a Python script that runs the power-up check through a bench supply and multimeter and logs each result
  • Updated the fixture test procedure and wiring diagram so technicians can run the test without an engineer

Lab Teaching Assistant, Circuits I, Thornbury Technical University · 2024 to 2026

  • Run two lab sections a week of about 20 students and help them debug breadboard circuits
Projects

Senior design: wireless soil moisture sensor network, team of 4, power and PCB lead

  • Designed the sensor node schematic and two-layer PCB in KiCad, including the battery charger and 3.3 V regulator
  • Wrote STM32 firmware in C for sleep mode and sensor reads, and measured average current on the bench
  • Brought up the first board, found a reversed regulator footprint and corrected it in revision two

FPGA traffic light controller, Digital Systems Design course

  • Wrote the state machine in Verilog, simulated it in Vivado and ran it on a development board
Skills

Design and simulation: KiCad, LTspice, MATLAB and Simulink, Verilog (Vivado)

Programming: C for microcontrollers (STM32, Arduino), Python for test scripts

Lab: oscilloscope, logic analyzer, function generator, bench power supply, soldering and rework

The hardware test internship comes first. Almost every bullet names a board, an instrument, a part or a document, so an engineer can picture the work and ask about each line.

How to write each section

Experience: the hardware, what you did, what changed

Name the hardware (a motor controller board, a battery pack, a relay panel), what you did to it and what happened next. BLS lists testing reliability and safety among the duties, so a test internship is real engineering experience. Give it the same detail as design work.

Hardware bullets, rewritten

Instead of: Tested circuit boards
Write: Tested 25 motor controller boards against the test procedure and wrote failure reports for the four that failed
Instead of: Troubleshot hardware issues
Write: Traced a prototype reset fault to an undersized pull-up resistor with an oscilloscope; the fix went into the next revision
Instead of: Designed a PCB for senior design
Write: Designed the sensor node schematic and two-layer PCB in KiCad, including the battery charger and 3.3 V regulator
Instead of: Programmed a microcontroller
Write: Wrote STM32 firmware in C for sleep mode and sensor reads, and measured average current on the bench
Instead of: Wrote documentation
Write: Updated the fixture test procedure and wiring diagram so technicians can run the test without an engineer

Projects: say what ran on real hardware

BLS says programs include classroom, laboratory and field studies, so lab and capstone work counts. Name the microcontroller, FPGA or main parts, and say whether you built it or only simulated it. Most students skip bring-up: what you measured on the first board and what you changed.

Education and licensure

Degree, school and month, plus your GPA if it helps. List four or five courses that match the posting; BLS names digital systems design and electrical circuit theory among them. BLS says licensure is not required for entry-level positions, and that experienced engineers may get a Professional Engineering (PE) license. If you have passed the Fundamentals of Engineering (FE) exam, one of its requirements, add one line with the month.

Skills to list

Electrical postings often name an exact tool chain: a PCB tool, a simulator, a microcontroller family. Write the names you have used ("Altium", "LTspice", "STM32") and add "coursework" for tools you only used in class. The University of Maryland career center also suggests mirroring the job description's keywords.

Tools

  • Schematic and PCB: KiCad, Altium Designer or OrCAD
  • Simulation: LTspice or PSpice, MATLAB and Simulink
  • Digital and embedded: C, Verilog or VHDL, Vivado or Quartus
  • Test automation: Python or LabVIEW
  • Lab equipment: oscilloscope, logic analyzer, multimeter, function generator, soldering station

Abilities

  • Reading datasheets and schematics
  • Board bring-up and bench debugging
  • Turning requirements into a circuit
  • Writing test procedures and failure reports
  • Explaining design choices to technical and nontechnical audiences

Common mistakes

  • Debugging with no cause. "Troubleshot boards" hides the interesting part. Say what was wrong, which instrument found it and what changed.
  • Specs with no numbers. "Designed a power supply" could be anything. Give the voltage, current or key part, such as a 5 V buck converter.
  • Simulation written up as hardware. If the circuit only ran in LTspice, write "simulated". Interviewers will ask what happened on the bench.
  • Code hidden in the skills line. BLS says these engineers need a working knowledge of programming languages. If you wrote firmware or test scripts, give each a bullet that says what the code did.

FAQ

Power, electronics or embedded: should my resume pick one?

BLS notes that some engineers specialize in areas such as electric power, radio communications or control systems. You don't have to choose on paper; put the closest courses, projects and tools first for each posting.

What if my only hardware experience is from labs?

Then labs and senior design are your experience. Give them full bullets with parts, tools and measurements, move Projects above Experience, and keep any unrelated job to one line.

I want firmware or embedded software jobs. What changes?

Lead with the code: the microcontroller, the language, what the firmware did and how you tested it. See the software engineer new grad example for project bullets that read well to software teams.

Check your resume free

Upload or paste your resume and see what to fix, in under a minute. Add a job post to see what's missing for that job. No sign-up.

Check my resume

More resume examples

See all resume examples.

Sources