Every Skill Set You Need to Build an IoT Device from Idea to Production

You’ve sketched the product. You’ve maybe even soldered a Raspberry Pi to a sensor and gotten data into the cloud. The next move feels obvious: hire a hardware engineer.

That instinct is the single most expensive mistake software founders make.

There’s no such thing as “a hardware engineer” the way there’s “a backend engineer.” Shipping a connected device touches at least 9 distinct disciplines, from RF antenna tuning to injection-molded enclosures to FCC filings. Some of those roles take 10 years to grow. Some you can rent for $8k. And one of them, if you outsource it, will quietly sink your launch.

Here’s the full map: what each role owns, which ones to hire, which to contract, and what a realistic minimum viable team actually looks like when you’re building your first device.

The 9 IoT Device Engineering Roles

Each of these is a real skill domain with its own career track. Treating them as interchangeable is how 12-month roadmaps become 30-month ones.

1. Systems / Hardware Architect. Owns the device spec end-to-end and makes the tradeoffs between battery life, BOM cost, connectivity choice, and physical size. Roughly the “staff engineer” of the device. If nobody owns this, every other role optimizes locally and the product loses globally.

2. Electrical Engineering (EE / schematic). Picks components, draws schematics, sizes power rails, reviews datasheets. Roughly the backend architect of the device.

3. Embedded Firmware. Writes the code running on the MCU: drivers, power management, the radio stack, the state machine. Bare-metal C or an RTOS like Zephyr or FreeRTOS. Iteration-heavy and IP-sensitive.

4. RF Engineering. Antenna design, matching networks, link budget, getting through radiated emissions testing. A genuine specialty, and most generalist EEs can’t do this and shouldn’t pretend to.

5. Mechanical Engineering (ME). Enclosure design, tolerances, thermal paths, drop and ingress performance. CAD in SolidWorks or Fusion 360. Bridges industrial design and manufacturing.

6. Industrial Design (ID). Form, ergonomics, materials, color, the user-facing surface. Usually a studio, not an employee.

7. Design for Manufacturing (DFM) / Manufacturing Engineering. Translates a working prototype into something a factory can produce 10,000 of, identically, at yield. Usually lives at your contract manufacturer, and is the bridge between “it works on my desk” and “it works on a line in Shenzhen at 2am.”

8. Test Engineering. Functional test fixtures, calibration routines, yield analysis on the line. Often shared with your CM at first, brought in-house at scale.

9. Regulatory & Compliance. FCC Part 15, CE RED, UKCA, IC, safety, EMC, intentional radiator certs. Not a role you “hire” so much as an accredited lab you book months in advance.

Here’s roughly when each shows up across the lifecycle:

              IDEA   EVT   DVT   PVT    MP
Systems       ████████████████████████████
EE                  █████████████
Firmware            ██████████████████████
RF                       ███████
ID/ME            █████████████
DFM                          ████████████
Test                            ██████████
Compliance                      ███████

Systems runs the whole length without a break.

What to Hire vs. What to Contract

For your first product, the math is pretty clean. Hire the roles that need deep context on your product and iterate constantly. Contract the roles that are specialist crafts you’ll need a few times, deeply, then less.

The riskiest role to outsource is systems / electrical ownership. If no one inside the company understands the MCU choice, the regulator rating, or the antenna ground plane requirements, every design review becomes a game of telephone with your contractors. Decisions get slow and expensive, and you can only reverse them in silicon.

PCB layout is different. A senior layout designer who’s done 200 boards will do a better job in a week than a generalist EE will in a month. Pay the hourly rate.

RF works the same way, twice as severe. A two-week engagement with an RF consultant before you tape out can save you a $40k re-spin and three months of FCC re-testing. Worth every dollar.

If you’re building on Bluetooth Low Energy, the radio stack details (transmit timing, advertising intervals, antenna placement) interact with everything else. The Hubble device SDK reference applications on Nordic, Silicon Labs, and TI parts are a useful starting point for scoping how much firmware work is custom versus already solved.

The Minimum Viable Hardware Team

For a software founder shipping product #1, the in-house team is 3 people. Sometimes 4.

              ┌──────────────────────┐
              │   YOU (PM / Founder) │
              │   Product + Cloud    │
              └──────────┬───────────┘
                         │
       ┌─────────────────┼─────────────────┐
       │                                   │
┌──────▼──────────┐                 ┌──────▼─────────┐
│  HW Lead /      │                 │   Embedded     │
│  Systems + EE   │                 │   Firmware     │
└──────┬──────────┘                 └──────┬─────────┘
       │                                   │
       └────────── contractor ring ────────┘
       ID  │  PCB Layout  │  RF  │  CM/DFM  │  Test Lab

The 3-person core:

1. Hardware lead / systems architect. Often doubles as your EE for schematics. This is your first hire and probably your most senior one. You want someone who’s shipped 2+ products to mass production, rather than 15 years at one big company on a single chip family.

2. Embedded firmware engineer. Owns the code on the device. Should be comfortable with low-power design and the specific radio stack you’re using. Tight collaboration with the hardware lead is the whole job.

3. You. Product, cloud, vendor management, fundraising. You’re the integrator across software, hardware, and business.

The 4th hire depends on what’s hurting: a mechanical engineer if you’re iterating on enclosure weekly, or a second firmware engineer if your device logic is genuinely complex (multiple sensors, complex power states, OTA, security).

Wrap that core with a stable of trusted contractors you can call: an ID studio, a PCB layout house, an RF consultant, a compliance lab, and a contract manufacturer that does DFM seriously.

One more piece: a fractional hardware advisor who’s shipped 3+ connected products is the highest-leverage hire a software founder can make in their first month. Eight hours a month, somewhere between $3k and $8k. They’ll save you from picking the wrong MCU, the wrong CM, and the wrong radio. All three are expensive mistakes.

Sequencing: Who You Need, When

Hire for the phase you’re in, not the phase you’re imagining 18 months out.

Concept    ─►  EVT     ─►  DVT       ─►  PVT       ─►  MP
Systems+FW     +EE depth   +ME           +Test eng     +Quality
               +ID studio  +Compliance   +DFM ramp     +Supply chain
                           +CM lock-in

• Concept / breadboard. Systems architect plus firmware. Often the same person. You’re proving the basic loop works.
• EVT (Engineering Validation). Add EE depth, engage an ID studio, get a first custom PCB into hands. First antenna and power-draw measurements happen here.
• DVT (Design Validation). Add ME for the production-intent enclosure. Engage your compliance lab. Lock in your contract manufacturer. The boring expensive work starts here.
• PVT (Production Validation). Test engineering shows up, often via your CM. DFM cycles intensify. You’re building units on the actual line with the actual fixtures.
• Mass Production. Quality engineering, supply chain, and sustaining engineering enter the picture.

Hire a test engineer in EVT and they’ll be bored for 6 months and quit. Wait until PVT to engage a compliance lab and you’ll miss your launch by a quarter. Sequencing is most of the game.

Your Next Move This Week

You don’t need to staff the org chart of a Fortune 500 hardware company to ship product #1. You need 3 in-house engineers who deeply own systems, firmware, and product, plus a tight contractor ring for the specialist work.

Draft your hiring plan against the 9 disciplines. Mark each one in-house, contract, or “not yet.” Identify the single internal owner of the device end-to-end. Book a fractional advisor this month.

For the full arc of getting from breadboard to factory floor, see our prototype-to-production guide. And if BLE or satellite connectivity is part of the picture, the Hubble integration guides are a reasonable place to scope the firmware effort.

Frequently Asked Questions

What roles do you need to build an IoT device?

Nine skill domains: systems architecture, electrical engineering, embedded firmware, RF engineering, mechanical engineering, industrial design, design for manufacturing, test engineering, and regulatory compliance. Not every role needs to be a full-time hire. For a first product, 3 in-house engineers plus a contractor network is typical.

Should I outsource PCB design?

PCB layout, yes. A specialist layout designer will do better work in less time than a generalist EE. Schematic design and component selection should stay in-house with your EE, because those decisions interact with firmware, power, and cost in ways your contractors won’t see.

What is the minimum team for a hardware startup?

Three people: a hardware lead who can own systems and schematic-level EE, an embedded firmware engineer, and a founder/PM running product and cloud. Add a fourth (mechanical or a second firmware engineer) when iteration speed in one of those areas becomes the bottleneck.

Is RF engineering really worth contracting separately?

For almost every team building a first product, yes. RF is a deep specialty, and antenna performance directly affects range, battery life, and certification. A short engagement with an RF consultant before you commit to a PCB layout is one of the cheapest forms of insurance in hardware.

When should I engage a contract manufacturer?

Around the start of DVT. Earlier than that, you don’t have a stable enough design for them to give meaningful DFM feedback. Later than that, and you’re locking in tooling decisions without their input. A good CM will participate in design reviews before you tape out final boards.

Hubble Network provides global Bluetooth connectivity directly from satellites, letting hardware teams ship connected devices without designing in cellular modems or managing carrier relationships. See how it works →