A guide to hiring IoT designers
An IoT product is a small device and a lot of software around it. The person who uses it sees a few lights, maybe a screen, a phone app and a stream of alerts. If those parts do not agree with each other, people can lose patience at set-up, however good the hardware is. An IoT designer is the person who plans that whole experience. This guide covers what the job includes, how it differs from nearby roles, what to ask before you hire and how to test a candidate.
What an IoT designer works on
The work spreads across four places where a person meets a connected product.
- The device itself: buttons, lights, sounds, small screens and what each one tells the user.
- Set-up and pairing: getting the device on the network and linked to an account without a manual.
- The app: controls, status, schedules and settings on a phone, a tablet or the web.
- Data and alerts: dashboards, charts and messages that turn raw readings into something a person can act on.
A good designer keeps all four in view at once, because a change in one place usually changes another.
How this role differs from nearby roles
An IoT designer plans how the product feels and behaves. An IoT developer builds the firmware, the connections and the cloud side that make it work. A general UI/UX designer usually works on web and mobile screens and may never have designed for a device that loses its connection. If your product has no physical part, the UI/UX page is probably the better fit. If you need the person who writes code that runs on the chip, see our page for a firmware engineer.
Design problems that only connected products have
- The device is offline, and the app must say so in plain words and show the last known state.
- A command is sent, but the device has not answered yet. The screen needs a clear waiting state.
- Several people share one device, each with a different level of access.
- A battery runs low, and the product has to warn the user early without nagging.
- An update runs while the device is in use, and nothing should surprise the user.
- A sensor reports something odd. Is it a fault in the device or a real event?
Ask every candidate how they would handle two or three of these. The answers show whether they have worked on real devices or only on app screens.
Decide what you need before you hire
- Whether the product is for homes, shops, factories, vehicles or something else, because each setting has different users and different tolerance for mistakes.
- Which parts need design now: the first-time set-up, the main app, the dashboard or the device controls.
- Whether the hardware already exists or is still changing.
- Who writes the firmware and the app, and how the designer will work with them.
- Whether you also need physical design for the case and controls. Tell us in the first call and we will say honestly whether we can match that skill.
Reading an IoT designer’s portfolio
Look for connected products, not only app screens. Ask which flows the person designed, such as pairing, schedules or alerts, and what changed after real people tried them. A good case study shows the problem, the options that were dropped and the final result. Screens that only look nice, with no story about how the device behaved, say little about the job.
Interview questions to try
- Describe the set-up flow you designed for a device. Where did users get stuck, and what did you change?
- How should an app show that a device is offline without alarming the user?
- A dashboard shows many readings. How do you decide what goes on the first screen?
- How do you design alerts so people read them and do not switch them off?
- How do you work with a firmware engineer when the hardware cannot do what the design needs?
Listen for real examples with a cost and a trade-off. Be careful with anyone who talks only about visual style.
Run a small paid design task
Hand every finalist the same short brief about your product. Good choices are the set-up flow for a new device, the screen that shows a device that went offline, or a simple dashboard for a few sensors. Pay for the time. Compare how well each person handles failure, how clear their notes are and whether they ask good questions about the hardware before they draw anything.
Match experience to the stage
At the idea stage you need someone who can sketch flows quickly and test them with paper or a clickable demo before any hardware exists. Once a device is being built, you need a designer who can talk to engineers about limits such as screen size, battery and connection range. For a product already in customers’ hands, a designer who reads support tickets and usage data and fixes the biggest problems first brings the most value.
Give them tools and a rhythm
Share the device, or a test unit, as early as you can. Designing for something you have never held leads to mistakes. Add the design files, the product notes, the support questions you hear most and a short weekly call. Ask for small changes that can be tested, not a big redesign at the end.
Mistakes to avoid
- Designing the app first and the device later, so the two feel like different products.
- Treating set-up as a small task. For many products it is the first and the most important moment.
- Showing every reading on one screen instead of the few the user needs.
- Skipping tests with real people in real rooms, where the signal is weak and the lighting is poor.
- Handing the design files and tool accounts to a contractor instead of keeping them in your company.
The device software needs its own expert. Our page on how to hire an IoT developer explains that side of the work.















