Design a smart traffic light control system
PremiumIoT systemMedium
- Signal controller
- Conflict monitor
- Emergency preemption
Quick answer
This ioT system interview question asks you to design a smart traffic light control system. 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 a smart traffic light control system: a city platform that collects detector data from every intersection, adjusts signal timing to traffic, and gives emergency vehicles a green light. The hard parts are that a wrong command must never cause conflicting greens, and every intersection must keep running when the network fails.
Each intersection has a signal controller in a roadside cabinet, vehicle detectors (loops and cameras) and a hardware conflict monitor. Controllers link to the central system over city fibre or LTE. Traffic engineers manage timing plans from a control room.
What must a smart traffic light control system do?
- Adaptive timing: Adjust green splits and cycle lengths every cycle from detector data.
- Coordination: Keep a green wave along main roads by setting offsets between neighbouring intersections.
How well must it do it?
- Safety: Conflicting greens are physically impossible; the local conflict monitor forces flashing red if it sees one.
- Local autonomy: If the link drops, the controller keeps running its time-of-day plan.
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- Signal controller
- Conflict monitor
- Emergency preemption
- Adaptive signal timing
- Time sync
- Edge autonomy
How you’ll practise
- Requirements
- Estimate
- Device and connectivity
- Ingestion and processing
- Device management and updates
- 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 a smart traffic light control system 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
- Design an autonomous vehicle fleet coordination platformIoT system · HardPremium
- Design a smart EV charging network management platformIoT system · MediumPremium
- Design a smart utility meter monitoring platformIoT system · MediumPremium
- Design a pharmaceutical cold chain monitoring platformIoT system · MediumPremium
Updated · Written by the SevyDevy team