Embedded Software: 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++, linux, python, git, agile. Languages: C — the main embedded language (must, most firmware is written in it), C++ (increasingly, especially on more powerful microcontrollers), less often Rust (growing interest), sometimes assembly. Microcontrollers: ARM Cortex-M (dominant), STM32, ESP32, AVR; in CIS — domestic chips (Milandr, ELVEES) due to import substitution. RTOS: real-time operating systems — FreeRTOS, Zephyr; understanding of tasks, scheduler, synchronization. Peripherals and interfaces: UART, SPI, I2C, CAN, USB, GPIO, interrupts, timers, ADC/DAC. On-hardware debugging: JTAG/SWD debuggers, work with oscilloscope and logic analyzer — without these embedded is impossible. Low-level understanding: memory, registers, interrupts, real time, optimization for constraints. Reading datasheets and basic understanding of schematics. Tools: Git, build systems (CMake, Make), specific IDEs and toolchains. English — for documentation (all chip technical documentation is English). The main thing: embedded values deep system understanding of "hardware" and the low level — that's what distinguishes an embedded engineer from a regular programmer.

Three close embedded roles, differing by level at which the engineer works. Firmware Engineer — lowest level, closest to "silicon": firmware running directly on hardware (bare-metal), peripheral drivers, bootloaders, bring-up of new boards; often without an OS or with a minimal one (see /research/embedded/firmware). Embedded Software Engineer — general level of embedded software: device application logic on microcontroller, work with RTOS, peripherals; broader than pure firmware, includes both low-level and application. Embedded Linux Engineer — upper level of embedded: devices on which full Linux runs (more powerful processors — routers, gateways, complex electronics); both embedded skills and deep Linux knowledge needed (see /research/embedded/embedded-linux). Roughly by level: firmware — "directly on hardware", embedded software — "microcontroller with RTOS", embedded Linux — "device with Linux". In practice the boundaries blur, terms mix in vacancies, one engineer often works at several levels. Career flow: people move between these roles freely; embedded developer can deepen into firmware or rise into embedded Linux.

C — mandatory and primary: it's the main language of embedded development, most firmware is written in it, it exists in any embedded project, and without confident C you don't enter the profession. C gives direct control over memory and hardware, compact code, predictability — what's critical under tight constraints. C++ — increasingly in demand, especially on more powerful microcontrollers and in modern projects: it allows writing more structured and safer code, and many teams transition to C++ (often a limited subset — without heavy features unsuitable for embedded). Rust — growing interest in embedded (memory safety without runtime), but still niche: real vacancies are few, this is rather "for the future". Strategy 2026: learn C mandatorily and deeply (foundation), then C++ (expands market, many modern projects on it); Rust — by desire and interest, as additional skill. But the language in embedded is only half the matter: even ideal C knowledge is useless without understanding of hardware — microcontrollers, peripherals, interrupts, real time, debugging on the board. Embedded is "C + deep understanding of what this C runs on".

Embedded developer creates the software that controls a device. 1) Study task and hardware — understand what the device should do, study the microcontroller and peripherals from datasheets, figure out schematics at the needed level. 2) Software development — write firmware in C / C++: initialization, work with peripherals (sensors, displays, communication), device business logic, interrupt handling, real-time control. 3) Work with RTOS — if the project is on a real-time OS: organize tasks, synchronization, resource distribution. 4) Peripheral drivers — implement or configure work with UART, SPI, I2C, CAN, USB etc. 5) On-hardware debugging — the main and most specific part: run the code on a real board, through a debugger (JTAG/SWD), oscilloscope, logic analyzer find why something doesn't work; embedded bugs are often at the intersection of software and hardware. 6) Optimization — fit within memory, speed, power consumption constraints. 7) Bring-up — launch of software on a new board. 8) Testing on the device, sometimes as part of a system. Key difference from regular development: embedded engineer works at the intersection of software and hardware, under tight constraints and real-time, and a significant part of the work happens "with a soldering iron and oscilloscope" next to the real device.

Limited. 15% of embedded jobs are remote or hybrid, and this is one of the least remote-oriented development areas for two reasons. 1) Physical hardware — embedded development is tied to development boards, device prototypes, measurement equipment (oscilloscope, logic analyzer, soldering station); a significant part of debugging can't be done without access to "hardware". Partly this is solved by remote access to test benches, but not fully. 2) Classified enterprises — in CIS a large share of embedded development falls on the defense industry and classified instrument-making enterprises, where remote work is restricted or prohibited, and often a clearance is required. Therefore embedded is more often an office or hybrid role; fully remote positions occur (product companies, IoT, software for more powerful platforms), but noticeably fewer than in web development. If remote work is critical for you, this is an important factor when choosing embedded as a specialization.

Embedded requires both programming and understanding of electronics — the entry threshold is higher than in web. Roadmap: 1) C language — master deeply: pointers, memory, bitwise operations, structures; this is the foundation. 2) Electronics and digital logic basics — how microcontroller, power, signals work; be able to read simple schematics. 3) Microcontrollers — take a real development board (STM32, ESP32, Arduino as the simplest start) and start programming: GPIO, interrupts, timers. 4) Peripherals and interfaces — UART, SPI, I2C; connect sensors, displays, modules. 5) RTOS — basics of real-time operating systems (FreeRTOS). 6) On-hardware debugging — learn to use a debugger, oscilloscope, logic analyzer. 7) C++ — add (expands market). 8) Reading datasheets — a key embedded engineer skill. 9) Pet projects — assemble and program real devices; embedded portfolio is working projects on hardware. Resources: embedded and microcontroller courses (Otus etc.), STM32 / ESP32 documentation, embedded communities, profile university programs (instrument-making, radio engineering, microelectronics — embedded more than other IT directions is tied to specialized education). Prepare to buy development boards and basic equipment — practice on real hardware is mandatory.

301 active open Embedded Software jobs in Zorky CRM sample — niche segment. Real market: embedded — a narrow area compared to web development, there are objectively few vacancies, and a significant part of the market — defense and classified enterprises whose vacancies are not fully represented in open sources. The role is called «embedded software developer», «embedded developer», «embedded software engineer», «microcontroller programmer», «software engineer» (in instrument-making). Geography: Russia / remote / Belarus. Sources: hh.ru, Habr Career, getmatch, LinkedIn, Telegram (embedded communities and job channels). Demand is narrow but resilient, with shortage of qualified personnel; in RF additionally supported by electronics import substitution. SPb — one of the strongest embedded centers. NB: the Embedded / IoT direction historically had auto-classification difficulties for vacancies — the visible number may understate the market.

Senior Embedded Software Engineer designs embedded systems and solves what no one else in the team can. C / C++ at expert level: deep mastery of C, confident C++ for embedded, understanding of what the code compiles into and how it runs on specific hardware. Embedded software architecture: design firmware structure, abstraction layers (HAL), modularity; make decisions accounting for tight constraints. Real-time systems: deep understanding of RTOS, scheduling, synchronization, determinism, interrupt handling; guarantee real-time behavior. Hardware: freely read datasheets and schematics, understand the microcontroller at register and peripheral level, work at the intersection of software and hardware, participate in board bring-up. Expert debugging: find the most complex bugs at the intersection of software and hardware — with oscilloscope, logic analyzer, tracing; diagnose memory, timing, interference problems. Optimization: for memory, speed, power consumption — at a level requiring understanding of the compiler and processor architecture. Low-level protocols and communication: interfaces, sometimes communication stack. Testing: approaches to testing embedded (which is harder than in web — real or emulated hardware is needed). Domain expertise: deep knowledge of the area (telecom, medtech, industrial automation). English — for technical documentation. Mentoring. The main value of Senior — design a reliable embedded system working in tight constraints and real time, and defeat bugs at the intersection of software and hardware.