SevyDevy

Design an IoT device provisioning service

PremiumIoT systemMedium

  • X.509 certificates
  • Mutual TLS
  • Secure element

Quick answer

This ioT system interview question asks you to design an IoT device provisioning service. Aim for a design that collects data from many devices and acts on it reliably, then explain device connections, ingestion, storage and trade-offs. Interviewers want to see how you handle unreliable networks, device scale and data volume.

The problem

Design an IoT device provisioning service: the system that gives every device a unique identity at the factory, registers it on first boot, assigns it to the right customer and region, and later rotates or revokes its certificates. The hard parts are keeping private keys secret, stopping cloned devices and handling activation peaks.

A device maker builds 30 million devices a year in 6 factories for consumers and business customers. Devices run in three regional clouds (US, EU and India). Each device has a secure element that can create and keep a private key.

What must an IoT device provisioning service do?

  • Factory identity: Every device leaves the factory with a unique key pair and a birth certificate signed by the maker's CA.
  • First-boot registration: A new device connects to one global endpoint, proves its identity and receives its region, owner and an operational certificate.
4 more requirementsUnlock to see all

How well must it do it?

  • Key secrecy: Private keys are created inside the secure element and never leave it, not even at the factory.
  • No clones: The same identity used from two places at once is detected and blocked.
2 more requirementsUnlock to see all

What scale should you design for?

Use these numbers in your estimates.

The scale numbers unlock with this questionUnlock

Key concepts

  • X.509 certificates
  • Mutual TLS
  • Secure element
  • Device identity
  • Certificate rotation
  • Device claiming

How you’ll practise

6 short steps · save and come back any time
  1. Requirements
  2. Estimate
  3. Device and connectivity
  4. Ingestion and processing
  5. Device management and updates
  6. Wrap-up

Lala, personalized to you, gives a hint when you ask and reviews your design when you are ready.

What do interviewers look for?

In any IoT system design round.

  • Clarifies device count, message rate and payload size
  • Handles devices that go offline and reconnect
  • Plans ingestion that absorbs bursts
  • Separates hot real-time data from long-term storage
  • Covers device identity, updates and security
  • Explains what runs on the device and what runs in the cloud

Questions people ask about this interview question

Which design type is this question?
It is an ioT system question. You design an IoT device provisioning service and explain your choices the way you would in an interview.
Is this question asked at entry level?
It is marked Medium. Entry-level engineers can practise it, but it expects you to reason about requirements and trade-offs, not only list components.
What should I cover first?
Start with the devices, what they send, how often and what must happen with it. Agree on scope with the interviewer before you design anything.
Can I practise it for free?
It is a premium question. Sign up and unlock it once for 10 credits; it then stays unlocked. When you finish, Lala, your personalized AI mentor, can review your design for 30 credits.

Related questions

Updated · Written by the SevyDevy team

Premium questionSign up free, then unlock it