Remote Embedded Software Engineer Jobs
Remote embedded software engineer jobs are in active demand across the U.S., with remote-first firms and distributed hardware-software teams hiring for firmware, RTOS, and driver development roles in sectors from automotive and medical devices to consumer electronics and defense. Employers hiring remotely right now include Canonical USA, Arcfield, and Boomi. Find a role that fits below and apply directly.
Find JobsOverview
Showing 5 of 27+ Remote Embedded Software 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 Software Engineer Jobs
Find roles that match your experience and apply in just a few clicks.
Find JobsRemote Embedded Software 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 software engineer jobs.
- Proficiency in C or C++ for bare-metal and RTOS-based embedded development
- Experience with real-time operating systems such as FreeRTOS, VxWorks, or Zephyr
- Familiarity with communication protocols including UART, SPI, I2C, CAN, and Ethernet
- Hands-on debugging with JTAG, oscilloscopes, logic analyzers, and in-circuit emulators
- Bachelor's degree in electrical engineering, computer engineering, or computer science
- Knowledge of low-level hardware-software integration including memory-mapped I/O and interrupt handling
Tips for Your Remote Embedded Software Engineer Job Search
Apply early to remote roles that fit
Migrate Mate lists remote embedded software engineer openings from across the U.S. in one place, so you can find roles matched to your stack and apply directly. Remote positions at distributed teams fill fast, so applying within the first few days of a posting matters.
Show firmware work in a public repository
Remote hiring managers can't watch you work, so your GitHub does the talking. Commit real firmware projects, RTOS configurations, and driver code with clear README files that explain the hardware target, toolchain, and what you solved. Undocumented code tells remote employers nothing.
Demonstrate async debugging communication
Remote embedded roles require you to describe hardware-software problems in writing, not on a whiteboard. Practice writing concise bug reports that include signal traces, memory maps, and reproduction steps. Showing this skill in your cover letter or a writing sample separates you from candidates who only demo in person.
Target remote-first firmware and IoT companies
Search specifically for companies that describe themselves as remote-first or fully distributed, not just remote-friendly. Remote-first IoT product companies and firmware consultancies have workflows built for distributed engineers, which means better tooling, documented processes, and less pressure to relocate later.
Prepare for hardware-in-the-loop remote interviews
Many remote embedded hiring processes include a take-home exercise using a development board you source locally or one the company ships to you. Have a known-good setup ready, practice narrating your debugging process in writing, and confirm your home lab has the tools the role requires before the interview stage.
Remote Embedded Software Engineer Jobs: Frequently Asked Questions
How do I get a remote embedded software engineer job?
Target companies that run distributed hardware-software teams, such as remote-first firmware consultancies, IoT product companies, and defense contractors with distributed engineering organizations. Remote employers screen for self-directed debugging habits, clear written communication about hardware-software interfaces, and hands-on fluency in C, C++, RTOS platforms, and debugging tools like JTAG and oscilloscopes. A public GitHub with firmware projects and documented async communication skills gives you a clear edge.
Which companies hire remote embedded software engineers?
Employers currently hiring remote embedded software engineers include Canonical USA, Arcfield, and Boomi, per current remote listings on Migrate Mate as of June 2026. These range from remote-first IoT and medical device companies to distributed defense and automotive teams that hire embedded engineers regardless of location.
Can you get a remote embedded software engineer job with no experience?
Yes, but remote entry-level embedded roles are competitive because employers expect you to debug hardware-software issues independently from day one. IoT startups and small firmware consultancies are most likely to hire entry-level remote candidates. A strong GitHub with personal microcontroller or RTOS projects, contributions to open-source embedded projects, or a completed internship with documented remote deliverables can substitute for professional experience.
Do you need a degree for remote embedded software engineer jobs?
Not always. Many remote employers in IoT, defense contracting, and firmware development weigh demonstrated skills over credentials, especially when candidates can show shipped firmware, documented embedded projects, or proficiency with specific toolchains like Zephyr, FreeRTOS, or Yocto. A degree in electrical engineering or computer engineering is preferred for some hardware-adjacent roles, but a strong portfolio and relevant certifications often carry equal weight.
Which industries hire the most remote embedded software engineers?
Remote embedded software engineer roles concentrate in Technology & Software, Manufacturing, and Distribution & Wholesale, based on current remote listings on Migrate Mate as of June 2026. These sectors rely on distributed engineering teams to develop and maintain firmware across product lines without requiring engineers to be co-located with hardware labs full time.
See All 27 Remote Embedded Software Engineer Jobs
Find roles that match your experience and apply in just a few clicks.
Find Jobs