IoT: market
Data as of November 19, 2026: 222 open IoT jobs, 32% remote among jobs that state a work format; median advertised salary $8,333/mo (from 26 postings that state a salary). Source: Zorky, updated daily.
IoT Engineer (Internet of Things engineer) — engineer who creates connected devices and Internet of Things systems: devices that collect data from sensors, transmit it over the network and interact with cloud and other systems — smart devices, industrial IoT, wearables, telemetry, smart home, sensors and gateways. Unlike firmware and embedded software focused on the device itself and low level (see /research/embedded/firmware, /research/embedded/embedded-sw), IoT Engineer thinks of the system as a whole: device + connectivity + cloud; the role is broader and often less "deep low-level", but requires understanding of connectivity and the cloud part. IoT — the most "systemic" of embedded specializations. Role family: IoT Engineer (general — connected devices and systems), IoT Embedded Developer (device-side lean), IoT Platform / Backend Engineer (cloud and server side lean), IoT Solutions Architect (IoT system design), adjacent — Embedded Software, Firmware, backend, DevOps. Responsibilities: software development for connected devices, organization of connectivity (choice and configuration of protocols and data channels), integration with cloud and IoT platforms, work with sensors and telemetry, ensuring reliability and security of data transmission, device energy efficiency, sometimes — server and platform side. Stack 2026: C / C++ (device software) and microcontrollers (ESP32 — popular in IoT, ARM Cortex-M), often Python (prototypes, gateways, server side); connectivity protocols — MQTT (key IoT protocol), CoAP, HTTP; wireless technologies — Wi-Fi, Bluetooth / BLE, LoRaWAN, Zigbee, NB-IoT / cellular; IoT platforms and cloud (cloud IoT services, in RF — Yandex Cloud IoT etc.), message brokers, telemetry databases; basics of IoT security (one of the industry's main problems), Git. Top skills: cloud, c++, linux, ci/cd, aws. Among jobs with a stated work format, 32% are remote. IoT Engineer — an in-demand and broad role at the intersection of embedded, connectivity and cloud; due to its systemic nature it's slightly more remote-friendly and varied than pure embedded.
Data as of:
Key numbers for the IoT market: open jobs, median salary, observed talent pool and remote share.
The IoT market currently has 222 open roles, 188 of them freshly observed. Median salary $8,333/mo.
Among jobs with a stated work format, 32% are remote. Device-oriented part tied to hardware. The more cloud — the more remote; international companies hire on remote, especially for platform roles.
⚠ salary known for 26 of 222 jobs; remote share from 180 with a stated format; 188 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many IoT postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.
New postings per week
Chart data
| Period | New postings per week |
|---|---|
| 2026-06-01 | 13 |
| 2026-06-08 | 13 |
| 2026-06-15 | 17 |
| 2026-06-22 | 56 |
| 2026-06-29 | 33 |
| 2026-07-06 | 327 |
| 2026-07-13 | 74 |
| 2026-07-20 | 40 |
| 2026-07-27 | 29 |
| 2026-08-03 | 20 |
| 2026-08-10 | 17 |
| 2026-08-17 | 20 |
| 2026-08-24 | 19 |
| 2026-08-31 | 13 |
| 2026-09-07 | 19 |
| 2026-09-14 | 34 |
| 2026-09-21 | 75 |
| 2026-09-28 | 48 |
| 2026-10-05 | 70 |
| 2026-10-12 | 248 |
| 2026-10-19 | 118 |
| 2026-10-26 | 135 |
| 2026-11-02 | 102 |
| 2026-11-09 | 127 |
Active sources per week
Sources over the period: 128. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 6 |
| 2026-06-08 | 7 |
| 2026-06-15 | 3 |
| 2026-06-22 | 17 |
| 2026-06-29 | 22 |
| 2026-07-06 | 16 |
| 2026-07-13 | 18 |
| 2026-07-20 | 21 |
| 2026-07-27 | 19 |
| 2026-08-03 | 15 |
| 2026-08-10 | 11 |
| 2026-08-17 | 13 |
| 2026-08-24 | 16 |
| 2026-08-31 | 10 |
| 2026-09-07 | 12 |
| 2026-09-14 | 18 |
| 2026-09-21 | 24 |
| 2026-09-28 | 20 |
| 2026-10-05 | 27 |
| 2026-10-12 | 27 |
| 2026-10-19 | 34 |
| 2026-10-26 | 39 |
| 2026-11-02 | 27 |
| 2026-11-09 | 31 |
New sources connected: Jun 22 +16 · Jun 29 +12 · Jul 13 +11 · Jul 20 +10 · all weeks (21) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +5 | 13 |
| Jun 22 | +16 | 56 |
| Jun 29 | +12 | 33 |
| Jul 6 | +8 | 327 |
| Jul 13 | +11 | 74 |
| Jul 20 | +10 | 40 |
| Jul 27 | +2 | 29 |
| Aug 3 | +6 | 20 |
| Aug 10 | +4 | 17 |
| Aug 17 | +2 | 20 |
| Aug 24 | +6 | 19 |
| Aug 31 | +5 | 13 |
| Sep 7 | +2 | 19 |
| Sep 14 | +4 | 34 |
| Sep 21 | +5 | 75 |
| Oct 5 | +4 | 70 |
| Oct 12 | +6 | 248 |
| Oct 19 | +4 | 118 |
| Oct 26 | +4 | 135 |
| Nov 2 | +5 | 102 |
| Nov 9 | +1 | 127 |
The current week is not over yet and is not shown: an incomplete week would look like a drop.
Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.
Chart data
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 13 | 6 |
| 2026-06-08 | 13 | 7 |
| 2026-06-15 | 17 | 3 |
| 2026-06-22 | 56 | 17 |
| 2026-06-29 | 33 | 22 |
| 2026-07-06 | 327 | 16 |
| 2026-07-13 | 74 | 18 |
| 2026-07-20 | 40 | 21 |
| 2026-07-27 | 29 | 19 |
| 2026-08-03 | 20 | 15 |
| 2026-08-10 | 17 | 11 |
| 2026-08-17 | 20 | 13 |
| 2026-08-24 | 19 | 16 |
| 2026-08-31 | 13 | 10 |
| 2026-09-07 | 19 | 12 |
| 2026-09-14 | 34 | 18 |
| 2026-09-21 | 75 | 24 |
| 2026-09-28 | 48 | 20 |
| 2026-10-05 | 70 | 27 |
| 2026-10-12 | 248 | 27 |
| 2026-10-19 | 118 | 34 |
| 2026-10-26 | 135 | 39 |
| 2026-11-02 | 102 | 27 |
| 2026-11-09 | 127 | 31 |
Salaries over time
Median IoT salary per week, USD per month.
Median salary, USD per month
Chart data
| Period | Median | Postings with a salary per week (n) |
|---|---|---|
| 2026-10-19 | 7,880 | 21 |
| 2026-10-26 | 9,165 | 25 |
| 2026-11-02 | 10,833 | 16 |
| 2026-11-09 | 7,227 | 16 |
The series starts on Oct 19: there is no data before that.
Only postings with a USD salary and a known period (month or year), $500–$50,000 per month. Weeks with fewer than 10 such postings are left blank — that means no data, not zero.
Chart data
| Week | Median |
|---|---|
| 2026-06-01 | — |
| 2026-06-08 | — |
| 2026-06-15 | — |
| 2026-06-22 | — |
| 2026-06-29 | — |
| 2026-07-06 | — |
| 2026-07-13 | — |
| 2026-07-20 | — |
| 2026-07-27 | — |
| 2026-08-03 | — |
| 2026-08-10 | — |
| 2026-08-17 | — |
| 2026-08-24 | — |
| 2026-08-31 | — |
| 2026-09-07 | — |
| 2026-09-14 | — |
| 2026-09-21 | — |
| 2026-09-28 | — |
| 2026-10-05 | — |
| 2026-10-12 | — |
| 2026-10-19 | 7,880 |
| 2026-10-26 | 9,165 |
| 2026-11-02 | 10,833 |
| 2026-11-09 | 7,227 |
Remote work over time
Share of IoT postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-01 | 70 |
| 2026-06-08 | 58.3 |
| 2026-06-15 | 82.4 |
| 2026-06-22 | 50 |
| 2026-06-29 | 40.9 |
| 2026-07-06 | 3.2 |
| 2026-07-13 | 36.4 |
| 2026-07-20 | 60 |
| 2026-07-27 | 50 |
| 2026-08-03 | 25 |
| 2026-08-10 | — |
| 2026-08-17 | 27.8 |
| 2026-08-24 | 21.4 |
| 2026-08-31 | — |
| 2026-09-07 | 31.2 |
| 2026-09-14 | 30.4 |
| 2026-09-21 | 10.2 |
| 2026-09-28 | 47.2 |
| 2026-10-05 | 40.9 |
| 2026-10-12 | 30.3 |
| 2026-10-19 | 27.4 |
| 2026-10-26 | 40.8 |
| 2026-11-02 | 26.6 |
| 2026-11-09 | 28.3 |
The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.
Chart data
| Week | Remote |
|---|---|
| 2026-06-01 | 70 |
| 2026-06-08 | 58.3 |
| 2026-06-15 | 82.4 |
| 2026-06-22 | 50 |
| 2026-06-29 | 40.9 |
| 2026-07-06 | 3.2 |
| 2026-07-13 | 36.4 |
| 2026-07-20 | 60 |
| 2026-07-27 | 50 |
| 2026-08-03 | 25 |
| 2026-08-10 | — |
| 2026-08-17 | 27.8 |
| 2026-08-24 | 21.4 |
| 2026-08-31 | — |
| 2026-09-07 | 31.2 |
| 2026-09-14 | 30.4 |
| 2026-09-21 | 10.2 |
| 2026-09-28 | 47.2 |
| 2026-10-05 | 40.9 |
| 2026-10-12 | 30.3 |
| 2026-10-19 | 27.4 |
| 2026-10-26 | 40.8 |
| 2026-11-02 | 26.6 |
| 2026-11-09 | 28.3 |
Technologies over time
How the share of IoT postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | cloud | Python | AWS |
|---|---|---|---|
| 2026-09-14 | 45.8 | 12.5 | 20.8 |
| 2026-09-21 | 41.4 | 13.8 | 3.4 |
| 2026-09-28 | 32.1 | 17.9 | 7.1 |
| 2026-10-05 | 47.1 | 26.5 | 17.6 |
| 2026-10-12 | 43.2 | 16.8 | 16.8 |
| 2026-10-19 | 37.7 | 34 | 13.2 |
| 2026-10-26 | 46.6 | 24.1 | 13.8 |
| 2026-11-02 | 28.6 | 40.5 | 14.3 |
| 2026-11-09 | 27.8 | 40.7 | 22.2 |
The series starts on Sep 14: there is no data before that.
Share among postings with a tagged stack; the series starts on Aug 10: earlier stack tags were assigned differently. Weeks with fewer than 20 tagged postings are left blank.
Chart data
| Week | cloud | Python | C++ | AWS | Azure |
|---|---|---|---|---|---|
| 2026-08-10 | — | — | — | — | — |
| 2026-08-17 | — | — | — | — | — |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | — | — | — | — | — |
| 2026-09-14 | 45.8 | 12.5 | 4.2 | 20.8 | 0 |
| 2026-09-21 | 41.4 | 13.8 | 3.4 | 3.4 | 3.4 |
| 2026-09-28 | 32.1 | 17.9 | 10.7 | 7.1 | 14.3 |
| 2026-10-05 | 47.1 | 26.5 | 14.7 | 17.6 | 17.6 |
| 2026-10-12 | 43.2 | 16.8 | 14.7 | 16.8 | 10.5 |
| 2026-10-19 | 37.7 | 34 | 20.8 | 13.2 | 9.4 |
| 2026-10-26 | 46.6 | 24.1 | 10.3 | 13.8 | 15.5 |
| 2026-11-02 | 28.6 | 40.5 | 19 | 14.3 | 14.3 |
| 2026-11-09 | 27.8 | 40.7 | 14.8 | 22.2 | 5.6 |
Countries over time
How the share of IoT postings in each of the top countries changed, per week.
Postings in the country, %
Chart data
| Period | USA | UK | Poland |
|---|---|---|---|
| 2026-06-22 | 0 | 0 | 69.4 |
| 2026-06-29 | 8 | 4 | 36 |
| 2026-07-06 | 1.6 | 84.2 | 4.3 |
| 2026-07-13 | 22.4 | 0 | 20.7 |
| 2026-07-20 | 25.8 | 6.5 | 22.6 |
| 2026-07-27 | 8.3 | 4.2 | 41.7 |
| 2026-08-03 | — | — | — |
| 2026-08-10 | — | — | — |
| 2026-08-17 | — | — | — |
| 2026-08-24 | — | — | — |
| 2026-08-31 | — | — | — |
| 2026-09-07 | — | — | — |
| 2026-09-14 | 24 | 12 | 0 |
| 2026-09-21 | 17 | 13.2 | 3.8 |
| 2026-09-28 | 23.8 | 11.9 | 14.3 |
| 2026-10-05 | 19.2 | 1.9 | 15.4 |
| 2026-10-12 | 20.6 | 8.5 | 6.9 |
| 2026-10-19 | 33 | 1.8 | 9.2 |
| 2026-10-26 | 29.6 | 1.9 | 12 |
| 2026-11-02 | 26.1 | 5.7 | 5.7 |
| 2026-11-09 | 28 | 12.1 | 8.4 |
The series starts on Jun 22: there is no data before that.
Share among postings with a known country; the chart shows the five countries with the most postings over six months. Weeks with fewer than 20 postings with a known country are left blank. A rising share can mean a newly connected source in that country rather than market growth.
Chart data
| Week | USA | UK | Poland | Germany | Singapore |
|---|---|---|---|---|---|
| 2026-06-01 | — | — | — | — | — |
| 2026-06-08 | — | — | — | — | — |
| 2026-06-15 | — | — | — | — | — |
| 2026-06-22 | 0 | 0 | 69.4 | 2 | 2 |
| 2026-06-29 | 8 | 4 | 36 | 0 | 24 |
| 2026-07-06 | 1.6 | 84.2 | 4.3 | 1.1 | 0.5 |
| 2026-07-13 | 22.4 | 0 | 20.7 | 5.2 | 6.9 |
| 2026-07-20 | 25.8 | 6.5 | 22.6 | 0 | 3.2 |
| 2026-07-27 | 8.3 | 4.2 | 41.7 | 8.3 | 4.2 |
| 2026-08-03 | — | — | — | — | — |
| 2026-08-10 | — | — | — | — | — |
| 2026-08-17 | — | — | — | — | — |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | — | — | — | — | — |
| 2026-09-14 | 24 | 12 | 0 | 0 | 0 |
| 2026-09-21 | 17 | 13.2 | 3.8 | 3.8 | 7.5 |
| 2026-09-28 | 23.8 | 11.9 | 14.3 | 0 | 2.4 |
| 2026-10-05 | 19.2 | 1.9 | 15.4 | 5.8 | 13.5 |
| 2026-10-12 | 20.6 | 8.5 | 6.9 | 14.3 | 5.8 |
| 2026-10-19 | 33 | 1.8 | 9.2 | 8.3 | 2.8 |
| 2026-10-26 | 29.6 | 1.9 | 12 | 5.6 | 2.8 |
| 2026-11-02 | 26.1 | 5.7 | 5.7 | 18.2 | 4.5 |
| 2026-11-09 | 28 | 12.1 | 8.4 | 10.3 | 0 |
Clean market: hiring index
The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just IoT.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.
Chart data
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open IoT jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 222 |
| Open demand | 222 |
| Observed supply | — not published |
IoT — growing direction at the intersection of embedded, connectivity and cloud: more and more connected devices (industrial IoT, smart city, smart home, telemetry). Drivers 2026 in CIS: development of IoT directions at telecom operators, industrial IoT, device import substitution. Systemic nature of the role makes it broader and more varied than pure embedded.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in IoT jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 0 |
| $1–2k | 0 |
| $2–3k | 2 |
| $3–4k | 2 |
| $4–5k | 3 |
| $5–6k | 3 |
| $6–7k | 1 |
| $7–8k | 1 |
| $8–9k | 2 |
| $9–10k | 1 |
| $10–12k | 3 |
| $12–15k | 3 |
| $15–20k | 5 |
| $20k+ | 0 |
- usable for the calculation: 26 (11.7%)
- stated but not converted to USD/month: 19 (8.6%)
- not stated: 177 (79.7%)
One in ten postings offers under $3,625, one in ten over $15,625. Half of the postings offer between $4,750 and $13,416. Sample: 26.
Depends on lean: platform / cloud IoT — closer to backend pay, device-oriented — closer to embedded; the most expensive — IoT architects.
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 0 |
| $1–2k | 1,000 | 2,000 | 0 |
| $2–3k | 2,000 | 3,000 | 2 |
| $3–4k | 3,000 | 4,000 | 2 |
| $4–5k | 4,000 | 5,000 | 3 |
| $5–6k | 5,000 | 6,000 | 3 |
| $6–7k | 6,000 | 7,000 | 1 |
| $7–8k | 7,000 | 8,000 | 1 |
| $8–9k | 8,000 | 9,000 | 2 |
| $9–10k | 9,000 | 10,000 | 1 |
| $10–12k | 10,000 | 12,000 | 3 |
| $12–15k | 12,000 | 15,000 | 3 |
| $15–20k | 15,000 | 20,000 | 5 |
| $20k+ | 20,000 | — | 0 |
Which countries have the most open IoT jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| United States | 42 | 22.3% |
| Poland | 33 | 17.6% |
| Germany | 28 | 14.9% |
| India | 11 | 5.9% |
| United Kingdom | 7 | 3.7% |
| France | 6 | 3.2% |
| Romania | 5 | 2.7% |
| China | 5 | 2.7% |
| Thailand | 5 | 2.7% |
| Hong Kong | 5 | 2.7% |
| Other countries | 41 | 21.8% |
Leader by IoT job count — the US (42 positions). Demand — telecom (IoT directions of operators), large tech companies (smart devices, cloud IoT), industrial IoT (production, energy, utilities, transport, AGRO), smart device manufacturers, smart home, IoT startups, system integrators.
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| US | 42 |
| PL | 33 |
| DE | 28 |
| IN | 11 |
| GB | 7 |
| FR | 6 |
| RO | 5 |
| CN | 5 |
| TH | 5 |
| HK | 5 |
Which technologies are most often required in the same job as IoT.
Used together with
Share — how many of the 222 jobs in the IoT market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).
Top stack IoT Engineer 2026: C / C++ and microcontrollers (ESP32 — popular in IoT, ARM Cortex-M), often Python; connectivity protocols (MQTT — key, CoAP, HTTP); wireless technologies (Wi-Fi, Bluetooth / BLE, LoRaWAN, Zigbee, NB-IoT / cellular); IoT platforms and cloud (Yandex Cloud IoT etc.), message brokers, time-series databases; IoT security, energy efficiency, Git.
Common pairs: ESP32 + Wi-Fi / BLE, MQTT + cloud, sensors + microcontroller, LoRaWAN + telemetry, device + IoT platform. Learning roadmap: embedded basics (C, ESP32) → sensors and peripherals → connectivity protocols (MQTT) → wireless technologies (Wi-Fi, BLE, LoRaWAN) → cloud and IoT platforms → backend basics (for platform lean) → IoT security → end-to-end pet project (device → MQTT → cloud → dashboard).
Chart data
| Name | Count |
|---|---|
| cloud | 81 |
| python | 61 |
| c++ | 42 |
| aws | 41 |
| azure | 33 |
| docker | 23 |
| java | 18 |
| c# | 17 |
| sql | 16 |
| go | 15 |
| kubernetes | 12 |
| javascript | 10 |
How many IoT jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 63 |
| middle | 18 |
| junior | 15 |
| principal | 11 |
| lead | 8 |
Career flow: Junior → Middle → Senior → Lead / IoT Solutions Architect. IoT gives a fork — you can move both toward device (embedded) and toward cloud (backend / DevOps).
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 63 |
| middle | 18 |
| junior | 15 |
| principal | 11 |
| lead | 8 |
Who hires the most for IoT and how concentrated demand is among the largest companies.
Employers
Demand is spread across 151 employers. The largest accounts for 4.9%, the top ten for 23.4%; the remaining 76.6% is long tail.
| share | value |
|---|---|
| top-1 | 4.9% |
| top-3 | 11.7% |
| top-10 | 23.4% |
| long tail | 76.6% |
⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier
Which company sites and job boards Zorky collects IoT jobs from.
Where Zorky sees this market
Observed across 43 sources; the largest accounts for 11.7% — this market does not rest on a single channel.
IoT jobs: hh.ru («IoT engineer» / «Internet of Things engineer» / «IoT developer» / part of «embedded developer»), Habr Career, getmatch, LinkedIn, Telegram (IoT and embedded communities, job channels). Real market is wider than exact search — IoT tasks go into both embedded and backend vacancies. NB: the Embedded / IoT direction had auto-classification difficulties — the visible number may understate the market.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 114 | 0.5135 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 93 | 0.4189 |
| telegram | Telegram | Telegram | 14 | 0.0631 |
| community | сообщества и публичные профили | community & public profiles | 1 | 0.0045 |
The newest IoT jobs from company career sites.
Recent openings
- Product Manager – Mobile & IoT · US
- Embedded Linux Field Engineer for Devices/IoT
- IoT Data Engineer · AZ
- Senior Ubuntu Embedded IoT System Engineer · AZ
- Angular-Entwicklerin / Angular-Entwickler mit UX/UI-Fokus (m/w/d) in der Universitätsbibliothek · DE
- Ingénieur Exploitation IoT H/F
- Java Developer (IoT) - Presencialidad puntual en A Coruña · PL
- IoT Embedded Systems Engineer · CH
Latest open IoT Engineer jobs — most recent 10 positions with adequate description quality. NB: the role is often called «Internet of Things engineer» or goes into embedded vacancies — full list in our CRM or via the «see all» link below.
Adjacent markets
IoT Engineer — the most "systemic" role of the Embedded / IoT direction, at the intersection of device, connectivity and cloud. Borders Embedded Software and Firmware (device side — /research/embedded), backend and DevOps (platform and cloud side — /research/backend, /research/devops). Career fork — into embedded or into cloud. Comparison — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
How this is measured
- Vacancy
- an open job that cleared the quality gate and lists at least two technologies
- Observed candidate
- a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
- Matchable candidate
- not counted yet
- Window
- jobs open at the moment the snapshot was built
About the data
- Some breakdowns are hidden: their data coverage is not yet sufficient.
- Statistics are shown only where the sample clears a quality gate.
- A missing block does not mean a value of zero.
Breakdowns currently hidden: 8.
Direction: Embedded / IoT
Related specializations
Inside IoT Engineer: IoT Engineer (general — connected devices and systems), IoT Embedded Developer (device-side lean), IoT Platform / Backend Engineer (cloud and server side lean), IoT Solutions Architect (IoT system design). Adjacent roles — Embedded Software, Firmware, backend, DevOps. Comparison — in the bar below.
Frequently asked questions
The most common questions about IoT Engineer: pay, grades, stack and skills, IoT Engineer vs Embedded Software, protocols and connectivity technologies (MQTT, BLE, LoRa), what an IoT engineer does, remote, companies, how to start, Senior skills. Answers recompute automatically.
What stack and skills are most often required from IoT Engineer?
Top skills: cloud, c++, linux, ci/cd, aws. Device software: C / C++ and microcontrollers (ESP32 especially popular in IoT — built-in Wi-Fi/BLE; ARM Cortex-M), often Python (prototypes, gateways). Connectivity protocols: MQTT — key IoT protocol (lightweight messaging protocol device↔cloud through broker), also CoAP, HTTP/REST, WebSocket. Wireless technologies: Wi-Fi, Bluetooth / BLE, LoRaWAN (long-range, low power), Zigbee (smart home), NB-IoT and cellular — understand which technology to choose for the task (range, power, data volume). Cloud and IoT platforms: cloud IoT services (Yandex Cloud IoT etc.), message brokers, telemetry databases (time-series), processing of data streams from devices. Server side — for platform lean: backend, API. IoT security — critical: encryption, device authentication, secure updates (IoT defense — known painful topic of the industry). Energy efficiency — for autonomous devices. Git. The main thing: IoT engineer should think of the system as a whole — from sensor to cloud; skill set is broader than for pure embedded, but depth in each layer may be less.
IoT Engineer vs Embedded Software — what's the difference?
Difference — in breadth and focus. Embedded Software (and even more firmware) focused on the device itself and low level: microcontroller, peripherals, RTOS, optimization under tight constraints; deep but narrow — within the device (see /research/embedded/embedded-sw). IoT Engineer thinks of the system as a whole: the device is only a part, also important are connectivity (how the device transmits data) and cloud (where the data goes, how it's processed, how to control the device remotely). IoT engineer deals with the whole chain «sensor → device → network → cloud → application». Roughly: embedded software — "into the device", IoT — "across the system". By skills: embedded software has deeper low level and hardware work; IoT — broader — added connectivity protocols, wireless technologies, cloud, sometimes backend, data transmission security; but in each layer separately IoT engineer may be less deep than a narrow specialist. In practice boundaries blur: IoT project includes embedded development, and many IoT engineers came from embedded; roles overlap. Career choice: embedded software / firmware — if you like depth, low level, hardware; IoT — if you like the system as a whole, connectivity, cloud, and variety and a bit more remote flexibility matter more.
What protocols and connectivity technologies does IoT use — MQTT, BLE, LoRa?
Choice of connectivity technology — one of the key decisions in IoT, and depends on a tradeoff between range, power consumption, data volume and cost. Data exchange protocols: MQTT — main IoT protocol: lightweight, economical "publish/subscribe" protocol for message exchange between devices and cloud through a broker; almost any IoT project uses it. Also CoAP (lightweight HTTP analog for devices), HTTP/REST. Wireless technologies (transport): Wi-Fi — high speed but power-hungry; for mains-powered devices. Bluetooth / BLE (Bluetooth Low Energy) — low power, short range; wearables, smart home, phone connection. Zigbee — mesh networks of smart home. LoRaWAN — long range (kilometers) at ultra-low power, but low speed; sensors, telemetry over large areas, agriculture, utilities. NB-IoT and cellular (LTE-M, 2G/4G) — connectivity through operator networks, wide coverage; industrial IoT, tracking. The task of IoT engineer — choose protocol+technology combo for a specific task: a field sensor on battery for 5 years needs LoRaWAN + MQTT; smart speaker — Wi-Fi; fitness tracker — BLE. Understanding these tradeoffs — one of the main IoT engineer competencies.
What exactly does an IoT Engineer do?
IoT Engineer creates connected devices and systems and is responsible for the whole data chain. 1) Device software development — write firmware for connected device (often on ESP32 / ARM): collecting data from sensors, basic logic, control. 2) Connectivity organization — choose and configure connectivity technology (Wi-Fi / BLE / LoRaWAN / cellular) and protocol (MQTT etc.); ensure reliable data transmission, including under unstable network. 3) Integration with cloud / IoT platform — configure how the device connects to cloud, sends telemetry, receives commands; work with IoT platform, message broker. 4) Server / platform side — for platform lean of role: reception, storage (time-series databases) and processing of data streams from devices, API, control panels. 5) Security — transmission encryption, device authentication, secure firmware updates "over the air" (OTA) — critical and complex part of IoT. 6) Energy efficiency — for autonomous devices achieve long work from battery. 7) Prototyping — quickly assemble and check device and solution prototypes. 8) Debugging — on device, at device-connectivity, connectivity-cloud boundaries. Key: IoT engineer is responsible not for one component but for the whole system — from physical sensor to cloud application — working reliably as a whole.
What share of jobs are remote?
Among jobs with a stated work format, 32% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How to start an IoT Engineer career in 2026?
IoT — broad role at the intersection of several areas; path depends on where you enter from. Roadmap: 1) Embedded basics — C language (plus Python), microcontrollers; convenient to start with ESP32 (cheap, has Wi-Fi and BLE "out of the box" — ideal for IoT start) or Raspberry Pi. 2) Sensors and peripherals — learn to connect sensors, read data, work with interfaces (I2C, SPI, UART). 3) Connectivity protocols — MQTT (key — mandatory), HTTP/REST; understand «device ↔ broker ↔ cloud» model. 4) Wireless technologies — Wi-Fi, BLE, basic LoRaWAN, NB-IoT; understand which technology to choose for the task. 5) Cloud and IoT platforms — master cloud IoT service (Yandex Cloud IoT etc.), learn to receive and store telemetry. 6) Backend basics — if you lean toward platform part: API, databases (including time-series), stream processing. 7) IoT security — basics. 8) End-to-end pet project — assemble a real IoT system: device with sensor → MQTT → cloud → dashboard; this is the best IoT engineer portfolio because it shows understanding of the whole chain. Resources: IoT and ESP32 courses, MQTT and cloud IoT services documentation, embedded and IoT communities. IoT is good in that you can enter from both embedded and backend side, gradually mastering the missing half.
How many open jobs are in this sample?
The published sample contains 222 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.
What skills does a Senior IoT Engineer need?
Senior IoT Engineer / IoT Solutions Architect designs IoT systems as a whole and is responsible for them working as a single whole. System thinking — main skill: see the whole chain «sensor → device → connectivity → cloud → application», design it in a balanced way, understand where the bottlenecks are. Embedded side: confident development of connected device software, work with microcontrollers, sensors, energy efficiency. Connectivity: deep understanding of protocols (MQTT etc.) and wireless technologies (Wi-Fi, BLE, LoRaWAN, NB-IoT); ability to choose optimal combo for the task and ensure transmission reliability in real, unstable conditions. Cloud and platform: designing the cloud part of IoT system — reception, storage, processing of large telemetry streams, scaling, API, device management. IoT security: expertise in protecting connected devices — encryption, authentication, secure OTA updates; IoT security — known weak zone of the industry, and a strong Senior can close it. Scalability and reliability: design a system that works with thousands and millions of devices. Device management: provisioning, monitoring, fleet updates. Energy efficiency at system level. Backend skills — for platform lean. Domain expertise (industrial IoT, smart city etc.). English — for documentation. Mentoring. The main value of Senior — design IoT system that reliably and securely works as a whole, from physical sensor to cloud, in real conditions and at scale.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.