Role Description L3Harris, Mission Networks, is seeking a Systems Engineer to join our team as a Lead Systems / Software Engineer supporting various programs, IRADs and proposals. This role will be for leading various pr…
Remote Embedded Engineer jobs
Embedded engineers write the software that runs inside devices — from consumer gadgets to cars and medical equipment — working close to the hardware in C and C++ under tight resource limits.
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
Open embedded engineer roles
2 shown of 17,736 · sorted by freshness
join our team working towards this goal, we would love to hear from you! Role Overview We are looking for a Senior Embedded Firmware Engineer to design, develop, test, and maintain firmware for embedded systems built aro…
What embedded engineers earn remotely
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $34–$47 | $70k–$98k |
| Mid level | $47–$65 | $98k–$135k |
| Senior | $62–$84 | $130k–$175k |
National ranges — remote pay usually tracks the employer's base market.
What employers ask for
The skills these listings keep naming
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
What does the volatile keyword do, and when do you need it?
Explain it prevents the compiler optimizing away reads/writes, with the classic cases: hardware registers and variables shared with ISRs. Precision matters here.
How do you debug a device that crashes intermittently in the field?
Talk about logging within constraints, watchdog data, reproducing environmental conditions, and instrumented builds. Field debugging method is a core competency.
Walk me through what happens from power-on to your main loop running.
Cover reset vector, startup code, memory initialization, and clock configuration. Comfort with the boot path signals genuine low-level experience.
How do you write an interrupt service routine safely?
Keep it short, defer work to the main loop or a task, protect shared data, and avoid blocking calls. Mention the race conditions you are preventing.
How do you handle a memory-constrained target — say 64KB of RAM?
Discuss static allocation, avoiding heap fragmentation, measuring stack usage, and linker-map analysis. Concrete numbers from a past project help.
How do you test firmware?
Unit tests off-target with mocked hardware, hardware-in-the-loop rigs, and on-target integration tests. Acknowledging what is hard to test is part of a good answer.
Tell me about a hardware/software interaction bug you solved.
The best stories involve a scope or logic analyzer and a datasheet detail everyone missed. Show the collaboration with hardware engineers.
Resume tips that move the needle
For embedded engineers specifically — generic advice costs you here
Name the microcontroller families, RTOSes, and protocols per project — embedded hiring screens on exact platform matches.
Describe the products you shipped and their constraints (battery life achieved, memory footprint, certification requirements).
Include debugging tooling experience — JTAG, oscilloscopes, logic analyzers — as it separates firmware engineers from application developers.
Mention safety or regulatory work (MISRA, ISO 26262, FDA) if you have it; those doors are hard to open otherwise.
Personal hardware projects with write-ups carry real weight in this field — link one if it is presentable.
Where this role goes
Typical progression
Applying for embedded engineer jobs remotely?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.