IoT Developer
You connect physical things to software, and deal with the fact that they lose signal.
No degree needed Moderate to hard — the difficulty is breadth plus unreliable networks.
Can I actually do this?
More open without a degree than embedded work, because much of the job sits on the software side — devices, a message broker, a backend, a dashboard. Hobby projects genuinely count. The honest caution is that security in this field has a poor record, and being the person who takes it seriously is a real differentiator.
Who it suits. People who want to write software with a physical consequence.
Runway. A year or so. It spans two fields, which is the cost.
Coming from backend work? The cloud side will feel familiar; the new part is that your clients are unreliable, battery-powered and occasionally underwater. Embedded Systems Engineer Backend Developer
Also advertised as
The route
Four stations, in order. Each one is a thing you finish before the next matters.
-
Station one
Learn it free
Only the best few, deliberately. Every one of these is free to use — the pill on each card says exactly what is and isn't free.
MQTT specification
Free to learn · no certificate
The messaging protocol most of this field runs on — an open OASIS standard, free to read. Understanding quality-of-service levels is the thing that separates working systems from flaky ones.
Verified 2026-07-28
ESP-IDF — getting started
Free to learn · no certificate
Cheap, capable, well-documented hardware to build real things on. Free docs.
Verified 2026-07-28
OWASP Cheat Sheet Series
Free to learn · no certificate
Connected devices are a standing security embarrassment, largely through default credentials and unencrypted transport. Free.
Verified 2026-07-28
-
Station two
Attest strategically
Nothing worth buying. There is no settled certification for this field, and a working connected device you can demonstrate is worth more than one would be. Spend the money on hardware.
Nothing here is worth paying for
No credential needed
Nothing worth buying. There is no settled certification for this field, and a working connected device you can demonstrate is worth more than one would be. Spend the money on hardware.
Checked 2026-07-28
-
Station three
Prove it
A certificate says you passed a test. These say you can do the job.
A device reporting to a dashboard you built
End to end: sensor, network, storage, display. The whole chain is the point.
Graceful behaviour when the network drops
Show what happens offline and how it recovers. This is the actual engineering.
A device you secured properly
No default credentials, encrypted transport, a way to update firmware. Document it — most of this field does not.
-
Station four
Get hired
Search these exact titles
Who hires for this. Manufacturing, agriculture, logistics, utilities, smart buildings, and hardware startups.
A working end-to-end demonstration is checkable in minutes and rare, which is why built projects carry here. That is our reasoning about what is inspectable, not a verified hiring statistic.
On salaryWe don't publish salary estimates. Numbers copied between blogs drift from reality, and a wrong number costs you real negotiating power. When we have a verified public source, it goes here with its date.
Where this route continues
- Embedded Systems Engineer — deeper toward the hardware
- Backend Developer — deeper toward the platform
- Embedded Systems Engineer — sideways move
- Backend Developer — sideways move
This page last verified 2026-07-28 · How we verify
MQTT specification, ESP-IDF getting started and the OWASP Cheat Sheet Series fetched and READ 2026-07-28.