IoT and Smart Systems Engineer · path guide

IoT and Smart Systems Engineer: path guide

Read this before you start. It explains what the role is, what you'll be able to do at the end, which core lessons you need, how to set up your tools, what it may cost and how long it really takes.

The role

An IoT and smart systems engineer builds connected devices and the systems around them: the firmware on a small chip, the sensors and parts it talks to, the way its data reaches the cloud, and the way thousands of devices are kept secure and up to date. They work with limits a web app rarely meets: a battery that must last a year, a few hundred kilobytes of memory, networks that drop for days, power that can be cut mid-write, and devices nobody can reach once they're installed. They read datasheets, write drivers, plan power budgets, design messaging that copes with drops, and release signed updates in stages. Success is measured by devices that keep working, and keep their data, in the place they're installed, not by how they behave on the developer's desk.

Everyday applications

• A water tank monitor in a village that reports a failed pump within the hour and runs for over a year on one battery.
• A cold-chain tracker in a lorry that logs temperatures without signal and uploads them at the depot.
• A smart meter that keeps hourly readings through a week-long network outage, and counts each one once.
• A farm soil sensor that sends a reading only when something changes, and checks in every hour so silence means a problem.
• A firmware fix that reaches 5% of devices first, rolls back by itself on any device where it fails, and stops before it reaches the rest.

What you'll be able to do

By the end of the path you will be able to:

1. PO1 Explain how embedded and IoT systems differ from computers and web apps, and plan a device for the place it's installed (IO1).
2. PO2 Write and organise firmware in MicroPython-style Python with a wake cycle, non-blocking timing and planned memory, and test it without hardware (IO2).
3. PO3 Work out a device's power use, use sleep modes and radio time well, and write and check a power budget for a year or more on a battery (IO3).
4. PO4 Make firmware reliable with interrupts, tasks, watchdogs, retries and safe state through resets and power cuts (IO4).
5. PO5 Read and drive the physical world with GPIO, ADC and PWM, drive loads safely, and judge a sensor's accuracy (IO5).
6. PO6 Talk to chips over I2C, SPI and UART, and write a driver from a datasheet that checks, waits, retries and saves power (IO6).
7. PO7 Send data from devices to the cloud with MQTT or CoAP, with good topics, QoS, status, last wills and per-device security (IO7).
8. PO8 Keep data through drops and power cuts with a flash buffer, backoff and edge filtering, and handle duplicates and gaps on the server (IO8).
9. PO9 Secure devices and update them safely with signed images, two slots, trial boots, rollback and staged rollouts (IO9).
10. PO10 Combine all of this in three tested projects and a capstone on the JalSetu practice kit (IO10).

The coverage of each outcome by lessons, quizzes and the path test is listed at the end of this guide.

How it compares with neighbouring paths

The difference in one line: other paths build for computers that are always on and reachable; this path builds for small devices that sleep, lose power and lose signal, in places you can't get to.

Before you start: core lessons to know

The path opens after you pass the final examination. These core modules matter most; revisit them if the entry diagnostic shows a gap:

Setup guide

Tested on 2 November 2026 on Linux. Versions change, so check each tool's official page when you install. The practice kit pins its packages in requirements.txt, so everyone installs the same versions.

Install:

1. Install Python 3.11 or newer from python.org. Check: python --version (or python3 --version) prints 3.11 or newer.
2. Download the starter kit from this path's Projects page and unzip it. In a terminal, go to the jalsetu folder.
3. Create and activate a virtual environment: python -m venv venv, then source venv/bin/activate (on Windows, venv\Scripts\activate).
4. Run pip install -r requirements.txt. It installs the three packages and their dependencies (about 46 MB) in under a minute on a good connection.
5. Run python tools/simulate.py --days 7. You should see a report of wakes, Wi-Fi attempts, charge used and battery life.

Verify your setup: run pytest in the jalsetu folder. In the starter all 28 tests fail on purpose; what matters is that the tests start, list 28 checks and finish, which takes a few seconds.

Windows and macOS: we could only verify Linux on 2 November 2026, so Windows and macOS are marked "not verified" in the kit. The commands are the same apart from activating the virtual environment.

Hardware and accounts

• Computer: a laptop from the last 6 to 8 years with 4 GB of memory and about 500 MB of free disk space.

• No hardware or paid accounts are needed. The kit runs on your own computer, with a simulated board, sensor, flash, Wi-Fi, update server and MQTT broker. JalSetu's water committee, site and device (listed by ID only) and its tank readings are invented, and the current figures are illustrative. Passing the tests shows your firmware handles these cases; it doesn't prove a real board, sensor or network behaves the same way.

• Optional: if you try real hardware, use low voltages, follow each part's datasheet, keep water away from the electronics, and keep Wi-Fi passwords and keys out of shared files.

Workload

Times are realistic estimates for a learner who has finished the core programme. They are not measured averages.

At 8 to 10 hours a week that is about 14 to 18 weeks.

How completion works

You complete the path when all of these are true, as shown on your completion record:

• every lesson is marked done;
• every module quiz is passed (70% or more);
• the path test is passed (70% or more);
• the three projects and the capstone are self-checked complete, with evidence links and your explanations.

Projects are self-checked for now: you tick the marking guide yourself and save your evidence on this device. Review by a team is planned for later; until then nothing on this site says a reviewer has approved your work. Progress is saved in this browser only, so download a backup from My progress now and then.

Outcome coverage