Remote Embedded Jobs
Remote Embedded jobs are open across the U.S. at remote-first firms and distributed teams in defense, automotive, consumer electronics, and industrial IoT. Employers hiring remote embeddeds right now include Canonical USA, Arcfield, and Boomi. See the openings below and apply to the ones that match your experience.
Find Remote Embedded JobsOverview
Showing 5 of 27+ Remote Embedded 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 Jobs
Find roles that match your experience and apply in just a few clicks.
Find Remote Embedded JobsRemote Embedded 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 jobs.
- Proficiency in C and C++ for resource-constrained microcontroller environments
- Experience with at least one real-time operating system such as FreeRTOS or Zephyr
- Familiarity with communication protocols including SPI, I2C, UART, and CAN
- Hands-on debugging using oscilloscopes, logic analyzers, and JTAG interfaces
- Bachelor's degree in electrical engineering, computer engineering, or computer science
- Experience reading hardware datasheets and writing or modifying board support packages
Tips for Your Remote Embedded Job Search
Build a firmware portfolio employers can review async
Host documented embedded projects on GitHub with clear READMEs, hardware schematics, and build instructions. Remote hiring managers evaluate candidates before any call, so your code and documentation need to tell the full story without you in the room.
Apply early to remote roles that fit
Migrate Mate lists remote embedded openings from across the U.S. in one place, so you can find roles that match your stack and apply directly. Early applicants get more attention before a posting gets saturated.
Demonstrate async communication in your application
Remote embedded teams run on written communication. Use your cover letter and any take-home assignments to show you can explain a debugging process, a design decision, or a hardware constraint clearly in writing, without a whiteboard.
Highlight remote lab and tooling experience
Call out experience with remote debugging tools, JTAG and SWD probe setups, CI pipelines for embedded targets, and any workflow that let you validate hardware without being physically present. These details signal readiness for distributed team environments.
Prepare for asynchronous technical interviews
Remote embedded interviews often include take-home code challenges or async architecture reviews instead of live coding. Practice writing thorough inline comments and decision rationale, because reviewers will judge your thought process from the artifact alone.
Remote Embedded Jobs: Frequently Asked Questions
How do I get a remote embedded job?
Target companies with distributed engineering teams, such as remote-first product companies and defense contractors with geographically spread departments. Remote embedded employers screen heavily for self-direction, clear async written communication, and the ability to debug hardware issues without an in-person lab. Hands-on experience with RTOS, bare-metal C or C++, and solid version control habits gives candidates a clear edge in remote hiring.
Which companies hire remote embeddeds?
Companies hiring remote embeddeds right now include Canonical USA, Arcfield, and Boomi, based on current remote listings on Migrate Mate as of June 2026. Remote-first product companies and distributed engineering teams in defense, automotive, and IoT are the most consistent sources of remote embedded openings.
Can you get a remote embedded job with no experience?
Yes, but remote entry-level embedded roles are harder to land because you'll be expected to work independently from day one. The strongest entry path is building a public portfolio of real firmware projects on GitHub, contributing to open-source embedded projects, or completing a well-documented personal hardware build. Remote-first startups in IoT and consumer electronics are the most likely to consider candidates who can demonstrate applied skills over a formal work history.
Do you need a degree for remote embedded jobs?
Not always. Many remote embedded employers weigh demonstrated firmware skills, a strong project portfolio, and verifiable experience with specific toolchains over a formal degree. Roles requiring security clearance or safety-critical certifications often do list a degree as a requirement, but a sizeable share of remote embedded postings treat relevant hands-on experience as a valid alternative.
Which industries hire the most remote embeddeds?
Most remote embedded openings sit in Technology & Software, Manufacturing, and Distribution & Wholesale, per 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 every engineer to be co-located with hardware.
See All 27 Remote Embedded Jobs
Find roles that match your experience and apply in just a few clicks.
Find Remote Embedded Jobs