Firmware Engineer
AssetWatch, Inc.
$150,000–$170,000
Jul 7, 2026
—
Jul 21, 2026
What this job asks for AI summary
This role centers on writing, debugging, and releasing embedded firmware for industrial IoT hardware — vibration sensors, BLE-enabled devices, and edge hubs. Day-to-day work spans wireless and wired communication protocols, cybersecurity features such as secure boot and encrypted OTA updates, and cross-functional collaboration with hardware, test, cloud, and manufacturing teams. It suits an experienced embedded C/C++ engineer comfortable moving between bench debugging and production release workflows.
Senior level · Remote · Full-time
Pay in the description: $150,000–$170,000
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 2,800 people nationally plausibly meet what this posting asks for (software developers). range 820–4,200
Applicant volume Light — Few people clear these requirements, so an application that does clear them gets looked at. Worth applying to even if you miss a nice-to-have.
Rare in this occupation — lead with these, and say what you built with them.
What the occupation pays Median $138,970 (middle half $107,524–$175,762). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (8)
The role is titled simply 'Firmware Engineer' with no level modifier, so advertised seniority is Unspecified; however, the breadth of required expertise (BLE, Wi-Fi, Ethernet, TLS/mTLS, secure boot, OTA/FOTA, cross-functional hardware bring-up) strongly supports a Senior classification.
SOC 15-1252 (Software Developers) is used because the role's primary work is writing and shipping production firmware code; 15-1299 (Computer Occupations, All Other) is noted as a runner-up since embedded/firmware engineering sits at the edge of the standard SOC taxonomy.
The role is remote-first but explicitly US-based (with some Canadian team members); no specific metro is listed.
Nordic/nRF and NUS-style command interfaces are mentioned within the BLE requirements section but framed as examples ('especially … Nordic/nRF'), so Nordic nRF is captured as preferred rather than a hard gate.
J-Link is listed as one example among several debug tools ('such as J-Link, oscilloscopes, logic analyzers…'); the hard gate is on hardware debugging capability broadly, but J-Link is the most specific named tool and is captured as required to represent that gate.
OTA/FOTA, embedded Linux, CI/CD, CMake/Makefile, systemd, and Jira all appear under the Preferred Qualifications section or in workflow/process narrative and are marked preferred accordingly.
AI tool usage is listed first under Required Qualifications ('Experienced in using AI tools to accelerate FW production and quality') but names no specific tool, so it is omitted from the skills list per the rule against generic concepts with no named technology.
This posting reads as a fully-remote role, so it was scored against the national candidate pool rather than a single metro.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.