IoT: market

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

Top skills: c++, python, solid, agile, javascript. 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.

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.

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.

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.

Partly, and more than on average in embedded. 12% of IoT jobs are remote or hybrid. IoT — relatively more remote-friendly embedded role due to systemic nature: cloud and platform part, server development, integrations, design, work with telemetry data are done well remotely. The more the role leans toward platform / cloud, the more remote it is (approaches backend). Caveat: device-oriented part of IoT remains tied to hardware — development and debugging of device firmware, checking sensors, testing connectivity on real equipment require access to "hardware" and sometimes field conditions. Therefore full full-remote is realistic for platform IoT roles; for device-oriented ones — more often hybrid. International companies hire Russian-speaking IoT engineers, including on remote, especially for cloud and platform part. Overall — better with remote than firmware, but worse than pure backend.

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.

8 active open IoT Engineer jobs in Zorky CRM sample — niche segment. Real market is wider: IoT — broad role at the intersection of embedded, connectivity and cloud, and IoT tasks go into both embedded and backend vacancies; the role is called «IoT engineer», «Internet of Things engineer», «IoT developer», part goes as «embedded developer» or «backend» with IoT lean — exact-term search doesn't catch everything. Geography: Russia / remote / Belarus. Sources: hh.ru, Habr Career, getmatch, LinkedIn, Telegram (IoT and embedded communities, job channels). Demand grows — more and more connected devices (industrial IoT, smart city, telemetry). NB: the Embedded / IoT direction historically had auto-classification difficulties for vacancies — the visible number may understate the market.

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.