Skip to content

SKILL.md

Latest commit

 

History

History
66 lines (51 loc) · 4.41 KB

SKILL.md

File metadata and controls

66 lines (51 loc) · 4.41 KB
Raw
name hr-iot
description Help HR and recruiting teams hire and assess Internet of Things (IoT) engineering candidates, spanning device firmware, connectivity, and cloud/edge integration. Use when asked to write an IoT engineer job description, create IoT interview questions, assess an IoT candidates skills across the stack, build an IoT engineering leveling framework, or similar IoT-hiring tasks.
metadata
author version
Tuan Duc Tran
1.0.1

HR IoT hiring

Helps HR and technical recruiters hire IoT engineers who work across device firmware, connectivity protocols, and cloud/edge integration — a role that spans multiple technical layers more than most single-discipline engineering roles.

Supported tasks

  • Writing job descriptions for IoT engineer roles spanning device, connectivity, and cloud layers
  • Building a leveling framework for IoT engineering roles
  • Creating screening questions distinguishing full-stack IoT experience from single-layer specialization
  • Designing interview exercises covering connectivity protocols (MQTT, BLE, LoRaWAN, Zigbee)
  • Drafting interview questions on device provisioning, OTA updates, and fleet management
  • Building a glossary of IoT terminology for non-technical recruiters
  • Creating a skills matrix mapping candidates across device, connectivity, and cloud layers
  • Drafting reference-check questions focused on shipped connected-device products
  • Designing a sourcing strategy for niche IoT specialties (industrial IoT, smart home, wearables)
  • Building compensation benchmarking guidance for IoT engineering roles
  • Creating onboarding plans for new IoT engineering hires
  • Auditing job postings for unrealistic full-stack IoT skill expectations

Key prompts

Job descriptions and leveling

  1. "Write a job description for an IoT engineer role spanning device firmware and cloud connectivity."
  2. "Build a leveling framework distinguishing junior, mid, and senior IoT engineers."
  3. "Explain the difference between an IoT engineer and an embedded firmware engineer for a recruiter."
  4. "Create a glossary of IoT terms (MQTT, BLE, edge computing, OTA) for non-technical recruiters."
  5. "Draft a job description for an industrial IoT engineer role, distinct from consumer smart-home IoT."

Screening and technical evaluation

  1. "Create screening questions distinguishing full-stack IoT experience from single-layer (device-only or cloud-only) specialization."
  2. "Draft interview questions covering connectivity protocol trade-offs (MQTT vs. LoRaWAN vs. BLE) for different use cases."
  3. "Design an interview exercise covering device provisioning and fleet management at scale."
  4. "Build a skills matrix mapping a candidate's experience across device, connectivity, and cloud layers."
  5. "Draft interview questions about OTA firmware update strategy and rollback safety."

Sourcing and evaluation

  1. "Draft a sourcing strategy for finding engineers with industrial IoT or smart-home experience."
  2. "Draft reference-check questions focused on a candidate's role in a shipped connected-device product."
  3. "Create compensation benchmarking guidance for IoT engineering roles by specialization and region."
  4. "Draft onboarding guidance for a new IoT engineering hire covering device lab and cloud access setup."
  5. "Audit this job posting for unrealistic expectations of full-stack mastery across every IoT layer."

Tips

  • Map candidates against the specific layers (device, connectivity, cloud/edge) the role actually requires rather than expecting mastery of all three.
  • Weight fleet-scale operational experience (OTA updates, device provisioning at scale) heavily for production IoT roles.
  • Be specific about the connectivity protocols and use case (industrial vs. consumer) in job postings.
  • Verify claimed IoT experience against shipped, real-world connected-device products where possible — IoT is a broad label and interview depth on hardware constraints, protocol choices, and production deployment reveals genuine expertise.

Common mistakes

  • Writing job postings expecting deep expertise across device, connectivity, and cloud layers simultaneously.
  • Underweighting operational, fleet-scale concerns (OTA safety, device provisioning) in favor of prototype-level skills.
  • Treating IoT experience as interchangeable across very different domains (industrial vs. consumer vs. wearables).
  • Failing to distinguish device-layer firmware skills from cloud/backend integration skills in screening.