Entry-level Embedded Software Engineer resume example

• With a senior colleague reviewing the change, implemented firmware drivers in C for interrupt-driven sensor acquisition; checked register sequencing and buffer boundaries with captured traces before enabling the device in the integration build.
• Within an assigned workstream, built a Python hardware-in-the-loop harness for the C++ control service, injecting serial disconnects and delayed responses; saved failure traces that reproduced a watchdog reset.
• Within the assigned scope, used oscilloscope captures and firmware logs to isolate a startup race; checked watchdog recovery, power interruption and firmware-version compatibility on the bench.
• Within the assigned scope, owned a firmware startup investigation using C++ traces and Python test control, resolved a power-on race and completed repeated recovery tests on the bench.
• Within the assigned scope, released CI/CD hardware-test instructions using Linux serial logs, reduced failed-test triage from 40 to 16 minutes and retained the exact firmware build identifiers.

• The team reduced boot-time initialization and deferred noncritical peripherals; my scope was data preparation, quality checks, and follow-up documentation under senior review. The team kept turnaround time within the agreed operating window; documented my assigned work separately from the team result and confirmed it with a senior colleague.
• Within the assigned scope, reviewed a proposed change against the existing interface contract, reproduced a reviewer’s edge case, and added the missing test or example before merging the change.
• Within the assigned scope, investigated a failure reported by a downstream team using the exact version and input they supplied. Reduced it to a reproducible test, delivered the fix with compatibility notes, and confirmed the original case passed before closing the report.

• Within the assigned scope, the team built hardware-in-the-loop tests for 24 timing and communication scenarios; my scope was data preparation, quality checks, and follow-up documentation under senior review
• Built an isolated fixture with normal, malformed and interrupted inputs; recorded the expected response before running the implementation so failures were distinguishable from a changed assumption.
• Packaged the reproduction steps, configuration and regression tests with the project; checked the instructions from a clean environment and documented the unsupported cases instead of claiming production readiness.
• Owned the independent regression fixture using isolated inputs, resolved a failing edge case and released a reproducible test package with expected outputs.

Relevant coursework: Circuit analysis, electronics, power systems, control systems

Firmware debugging · Oscilloscope analysis · Watchdog recovery · Hardware integration testing

• Published an independent technical note using the project’s before-and-after traces, explaining the failed assumption, regression coverage and cases the implementation does not support.