Remote Embedded Systems Engineer Jobs
Remote Embedded Systems Engineer jobs are open across the U.S. at remote-first firms and distributed teams in defense, automotive, consumer electronics, and industrial IoT. Employers hiring remotely right now include Canonical USA, Arcfield, and Boomi. Scan the live roles below and apply to whichever ones fit.
Find JobsOverview
Showing 5 of 27+ Remote Embedded Systems Engineer jobs
About the role
We build the HyperView handheld hyperspectral medical imaging camera — a clinical device that captures tissue oxygenation / hemoglobin maps and exports them as DICOM. We're hiring a Java/Android engineer to own and evolve the camera's on-device application across three fronts: (1) maintain and extend current functionality, (2) modernize a long-lived legacy Android/NDK stack to current versions, and (3) integrate new and upgraded hardware as the device platform advances. This is a hands-on, full-stack-on-the-edge role spanning the Android app layer, native (JNI/C/C++) imaging and device-control code, and the embedded hardware boundary — on a regulated medical device where correctness and traceability matter.
The platform you'll work on
- Product: HyperView — handheld hyperspectral clinical imaging camera; DICOM output.
- Compute board: NXP / Freescale i.MX6 (SABRE-SD class, ARM Cortex-A9; sabresd_6dq).
- Operating system: Android 4.3 "Jelly Bean" (API level 18) — rooted, kiosk-locked.
- Peripherals / hardware: Atmel UC3 capture/optics board (exposed to Android over USB mass storage), GPIO-driven illuminator / optics-power / capture trigger, IR/thermal sensor, and a calibrated optical path.
- App stack (current / legacy): Java (JDK 8); Android SDK 23, build-tools 27.0.3; Gradle 4.6–4.10.1 + Android Gradle Plugin 3.1–3.3; NDK r16b; native C/C++ via JNI (imaging algorithm, libhm_client, libIRSensor, device-helper utilities); pre-AndroidX android.support libraries; SQLite; the Imebra DICOM toolkit; Timber.
- Ecosystem: a companion Android app (DicomSaver) and a Windows .NET/WPF imaging suite that talks to the device over WPD/MTP.
What you'll do
- Maintain, debug, and extend the on-device Android application (Java and the native JNI layer).
- Lead the modernization: raise the Android API level, migrate android.support → AndroidX, upgrade Gradle/AGP/NDK and third-party libraries, replace deprecated APIs, and re-establish clean, reproducible builds — without regressing clinical behavior or calibration integrity.
- Integrate new and upgraded hardware being added to the device: bring up sensors/boards/illumination/compute and write or adapt the Android↔hardware glue (JNI, GPIO, USB, serial/I²C/SPI), validated end-to-end against the imaging pipeline.
- Work fluently across the native boundary: read, debug, and modify performance- and hardware-sensitive C/C++; manage NDK toolchains and reproducible native builds.
- Debug on real hardware: adb/logcat, root (su), filesystem mounts, kernel logs (dmesg), USB/storage enumeration.
- Uphold medical-device rigor: verification, documentation, and change traceability.
Required qualifications
- Strong Java and Android engineering, genuinely comfortable across both legacy and modern Android.
- Demonstrated experience working inside legacy Android codebases — Android 4.x / Jelly Bean era, android.support libraries, old Gradle/AGP, NDK r16-era toolchains. You can navigate, build, and debug an old stack, not just greenfield modern apps.
- A proven track record modernizing legacy Android apps: API-level upgrades, AndroidX migration, Gradle/AGP/NDK upgrades, dependency and deprecation remediation — executed methodically and regression-safe.
- Android NDK / native development: C/C++, JNI, ndk-build/CMake; ability to read and modify imaging and device-control native code.
- Embedded / hardware integration: integrating peripherals over GPIO/USB/serial/I²C/SPI; running Android on custom ARM boards (i.MX6 / NXP a strong plus); comfort with rooted/AOSP devices and board bring-up.
- Solid on-device debugging discipline (adb, logcat, dmesg, mounts) and reproducible-build hygiene.
Strongly preferred / bonus
- Medical-device or other regulated / safety-critical software (IEC 62304, ISO 13485, FDA QSR / Design Controls).
- DICOM and/or the Imebra toolkit; medical or scientific imaging, computer vision, or hyperspectral/multispectral imaging.
- AOSP / BSP / custom-ROM work on NXP i.MX or similar SoCs; Linux kernel / device-driver familiarity.
- Kotlin; modern Android architecture; CI for Android + NDK.
- Windows/.NET interop experience (for the companion PC suite).
Pay: $90,000.00 - $120,000.00 per year
Work Location: Remote
See All 27 Remote Embedded Systems Engineer Jobs
Find roles that match your experience and apply in just a few clicks.
Find JobsRemote Embedded Systems Engineer Job Market
Who's Hiring
- Canonical USA4
- Arcfield3
- Boomi2B
- dormakaba2
- Lynx1
Top Industries Hiring
- Technology & Software7
- Manufacturing3
- Distribution & Wholesale2
- Energy1
- Electronics & Hardware1
What Employers Look For
The qualifications that appear most often in remote embedded systems engineer jobs.
- Proficiency in C and C++ for bare-metal and RTOS-based development
- Experience with microcontrollers such as ARM Cortex-M, STM32, or equivalent platforms
- Familiarity with communication protocols including I2C, SPI, UART, CAN, and Ethernet
- Bachelor's degree in electrical engineering, computer engineering, or a closely related field
- Experience with debugging tools including JTAG, oscilloscopes, and logic analyzers
- Knowledge of real-time operating systems such as FreeRTOS, VxWorks, or Zephyr
Tips for Your Remote Embedded Systems Engineer Job Search
Show your async documentation skills upfront
Remote embedded teams rely on written specs, design documents, and clear commit messages to stay aligned across time zones. Include links to README files, design notes, or technical write-ups in your application so hiring managers can see you communicate your engineering decisions clearly without a meeting.
Build a firmware portfolio with real hardware
Remote employers can't watch you solder or debug in person, so a public GitHub repository with firmware projects on common platforms like STM32, ESP32, or NXP targets is your proof of hands-on ability. Document the hardware setup, the problem you solved, and the toolchain you used.
Apply early to remote roles that fit
Migrate Mate lists remote embedded systems engineer openings from across the U.S. in one place, so you can find roles that match your hardware background and apply directly. Applying in the first 48 hours of a posting going live meaningfully improves your chances of a response.
Prepare for remote technical screens on embedded toolchains
Remote interviews for embedded roles frequently include live debugging sessions over shared screen or take-home code reviews using JTAG, GDB, or oscilloscope data files. Practice narrating your debugging process out loud, since remote teams assess how well you explain your reasoning in real time.
Target companies with established remote hardware workflows
Remote-first firmware teams have already solved the hardest logistical problems, including hardware shipping, lab access, and cross-timezone handoffs. Search for job postings that mention remote lab kits, async design reviews, or distributed hardware teams, which signals the company won't ask you to improvise the remote setup from scratch.
Remote Embedded Systems Engineer Jobs: Frequently Asked Questions
How do I get a remote embedded systems engineer job?
Target remote-first companies and distributed hardware teams that have already built workflows for async collaboration. Remote employers screen for C/C++ or Rust proficiency, RTOS experience, and comfort with toolchains like JTAG and GDB, but they also assess written communication and self-direction heavily. A GitHub repository with real firmware projects and the ability to document your work clearly gives you a strong edge over candidates with comparable experience who can't demonstrate independent output.
Which companies hire remote embedded systems engineers?
Companies hiring remote embedded systems engineers right now include Canonical USA, Arcfield, and Boomi, based on current remote listings on Migrate Mate as of June 2026. Remote-first defense contractors, IoT platform companies, and distributed automotive software teams are among the most active employers of embedded systems engineers in fully remote roles.
Can you get a remote embedded systems engineer job with no experience?
Yes, but remote entry-level embedded roles are harder to land because employers expect you to troubleshoot and iterate independently from day one without in-person mentorship. Smaller IoT startups and open-source hardware companies are more likely to hire junior engineers remotely. A portfolio of personal firmware projects, contributions to open-source embedded repositories, or a capstone project on real hardware can substitute for professional experience and demonstrate you can work without hand-holding.
Do you need a degree for remote embedded systems engineer jobs?
Not always, though a degree in electrical engineering, computer engineering, or computer science is still listed in most job postings. Remote employers weigh demonstrated hardware and firmware skills heavily, so candidates who can show real project work, relevant certifications, and a clear command of embedded toolchains often move forward regardless of formal credentials. The closer your portfolio maps to the specific hardware platform or RTOS a team uses, the less a degree gap matters.
Which industries hire the most remote embedded systems engineers?
The sectors hiring the most remote embedded systems engineers are Technology & Software, Manufacturing, and Distribution & Wholesale, based on current remote listings on Migrate Mate as of June 2026. These sectors have embraced distributed engineering teams because their firmware and software development cycles can be managed effectively through async communication and remote lab access arrangements.
See All 27 Remote Embedded Systems Engineer Jobs
Find roles that match your experience and apply in just a few clicks.
Find Jobs