Embedded Firmware Engineer (26-00819) -

Embedded Firmware Engineer – Connected Products

Location

Brookfield, WI. If we have someone great from 60-90 minutes away, 1-2 days/week onsite can be fine after they kick things off.

Position

Senior Firmware Engineer

Top 3

Embedded, C++, Connectivity (Bluetooth, Cellular, WiFi)

• If they don't have Connectivity, they need strong full design, test, validate of STM products
• This is C++ --- not C based.

Type

Contract / Potential Contract-to-Hire

Rate

$55–75/hr depending on experience and onsite availability

• Can subvend up to $80/hr

Schedule

Hybrid flexibility available

Position Overview

We are looking for Embedded Firmware Engineers to support new product development and next-generation connected product platforms. These engineers will work on embedded products incorporating technologies such as Bluetooth/BLE, Wi-Fi, and cellular connectivity, including devices that provide location and connectivity capabilities for products used in the field.

This is a hands-on firmware development role covering the complete embedded product lifecycle. Engineers should be capable of designing and implementing firmware, testing and validating their own code, troubleshooting issues, and supporting products through launch and post-launch bug fixes.

Responsibilities

• Design, develop, test, and troubleshoot embedded firmware for new and existing products.
• Develop firmware primarily in C++ within bare-metal and MCU-based embedded environments.
• Contribute to firmware architecture and make significant hands-on contributions to production code.
• Develop firmware for connected products utilizing Bluetooth/BLE, Wi-Fi, and/or cellular technologies.
• Work with microcontrollers, with STM/STMicroelectronics experience strongly preferred.
• Develop and execute testing and validation for your own firmware.
• Debug firmware and embedded-system issues throughout development and product validation.
• Participate throughout the complete product development lifecycle, including design, implementation, integration, validation, product launch, and production bug fixes.
• Translate system and product requirements into embedded firmware functionality.
• Participate in design and code reviews.
• Support both new product development and reusable/platform-level firmware development.

Required Experience

• Professional embedded systems or firmware development experience.
• Strong C++ programming experience in an embedded environment.
• Hands-on microcontroller-based firmware development experience.
• Experience developing bare-metal embedded firmware.
• Experience personally implementing substantial portions of production firmware.
• Experience testing, validating, and debugging your own code.
• Experience taking an embedded product through development and product launch.
• Experience troubleshooting and implementing post-launch bug fixes.
• Ability to work closely with embedded hardware and understand firmware/hardware interaction.

Preferred Experience

• Bluetooth / BLE
• Wi-Fi
• Cellular connectivity
• Connected or IoT products
• STMicroelectronics / STM microcontrollers
• Location, asset-tracking, telematics, or similar connected-device experience
• Experience developing reusable firmware or platform architectures
• Experience working across both new product development and platform firmware

Ideal Background

The ideal candidate is a strong embedded C++ firmware engineer who has worked at the MCU/bare-metal level and has experience developing connected products.

Candidates without significant connectivity experience can still be a fit if they have strong STM microcontroller, bare-metal, and C++ experience and have personally owned firmware through design, development, testing, validation, launch, and post-launch support.

Candidates whose experience is primarily MPU, embedded Linux, or higher-level application development without significant MCU/bare-metal work would be less aligned with this position.

Recruiter Screening Questions

• Tell me about an embedded product where you personally developed the firmware. What code did you own?
• How much of your experience is bare-metal/MCU development versus MPU, Linux, or higher-level application development?
• Which microcontroller families have you worked with? Have you used STM/STMicroelectronics devices?
• How extensively have you used C++ in embedded systems?
• Have you developed products using Bluetooth/BLE, Wi-Fi, or cellular connectivity? What did you personally implement?
• How did you test and validate your own firmware?