$125k - $180k
Our employees work at the cutting edge of AI cloud infrastructure alongside some of the most experienced and innovative leaders and engineers in the field. Where we work Headquartered in Amsterdam and listed on Nasdaq, N…
Engineering & IT · Kansas City, MO
Embedded Engineer jobs in Kansas City, MO
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.
259
Open roles today
$32–$79/hr
Typical pay range
$110k
Median, full-time
1
Fresh in this list
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.
01
Open embedded engineer roles
6 shown of 259 · sorted by freshness
including software development, air and missile defense, and systems engineering. IERUS develops value for our defense and commercial customers... ...packages. To learn more, please visit Overview: As an Embedded Develop…
$150k - $180k
those who need it most, come join our team. About the Position We are seeking a highly skilled and ambitious Lead Software Engineer to join our dynamic team. You will play a pivotal role in shaping the development of our…
electric vehicle revolution. Position Summary The Software Engineer will contribute to the development, calibration, and testing of... ...Must have 2-3 years of C programming experience on Embedded controllers. Working e…
difference for the world as part of a company leading the electric vehicle revolution. Position Summary The Senior Embedded Software Validation Engineer is responsible for the validation, verification, and testing of emb…
$55k - $65k
trusted technology partner that empowers businesses to stay secure, connected, and future-ready. The team is hiring a Junior Network Engineer to support the design, implementation, and troubleshooting of network environm…
02
What embedded engineers earn in Kansas City
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $32–$44 | $66k–$92k |
| Mid level | $44–$61 | $92k–$127k |
| Senior | $59–$79 | $122k–$164k |
Adjusted for the Kansas City market from national ranges.
03
What employers ask for
The skills these listings keep naming
C and C++Microcontrollers (ARM Cortex-M)RTOS (FreeRTOS, Zephyr)Hardware protocols (SPI, I2C, UART)Reading schematics and datasheetsDebugging with scopes and JTAGMemory and power constraintsRust or Python (a plus)Version control and CI for firmware
04
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.
05
Resume tips that move the needle
For embedded engineers specifically — generic advice costs you here
01
Name the microcontroller families, RTOSes, and protocols per project — embedded hiring screens on exact platform matches.
02
Describe the products you shipped and their constraints (battery life achieved, memory footprint, certification requirements).
03
Include debugging tooling experience — JTAG, oscilloscopes, logic analyzers — as it separates firmware engineers from application developers.
04
Mention safety or regulatory work (MISRA, ISO 26262, FDA) if you have it; those doors are hard to open otherwise.
05
Personal hardware projects with write-ups carry real weight in this field — link one if it is presentable.
06
Where this role goes
Typical progression
01
Junior Embedded Engineer
02
Embedded Engineer
03
Senior Embedded Engineer
04
Principal Firmware Engineer
Ten quiet minutes a day
Applying for embedded engineer jobs in Kansas City?
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.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.