Home / Jobs / IoT Product Manager
Mid-Level (2-5 years)

IoT Product Manager

This isn't just about software; you'll be working with actual physical 'things' that connect to the internet. You'll own a specific IoT product or device, from figuring out what customers really need to making sure it actually works in the real world. It's a tricky balance between the fast pace of software and the much slower, more complex world of hardware. If you like seeing your work come to life in tangible products, this could be for you.

Job ID
JD-TECH-IOPM-002
Department
Technical Roles
NOS Level
Level 5-6
OFQUAL Level
Level 5-6
Experience
Mid-Level (2-5 years)

Role Purpose & Context

Role Summary

The IoT Product Manager is responsible for managing the feature set and backlog for a specific connected device or product line. You'll spend your days translating customer problems into clear requirements for our engineering teams, making sure our IoT products actually solve real-world issues and delight users. You'll sit right at the intersection of hardware, firmware, cloud, and software, acting as the glue that holds it all together, which, honestly, is harder than it sounds. When you do this job well, our devices just work – customers love them, and we see fewer support tickets. When it's not going so well, devices might go offline, updates fail, or we build something nobody wants. The challenge? It’s constantly juggling the slow, rigid pace of hardware development with the agile demands of software, all while keeping a close eye on the bottom line. The reward? Seeing a physical product you helped create out in the wild, making a real difference to our customers.

Reporting Structure

Key Stakeholders

Internal:

External:

Organisational Impact

Scope: This role directly impacts the success of our individual IoT products. Your work ensures that what we build actually meets market needs, stays competitive, and contributes to our revenue goals. Get it right, and we launch successful products; get it wrong, and we waste time and money on things nobody wants, or worse, products that fail in the field and damage our reputation.

Performance Metrics

Quantitative Metrics

  1. Metric: Feature Adoption Rate
  2. Desc: Percentage of active devices using a newly released feature.
  3. Target: Achieve 70% adoption within 3 months of release for key features.
  4. Freq: Monthly, tracked via cloud telemetry data.
  5. Example: If we launch a new power-saving mode, we'd expect 70% of eligible devices to be using it within 90 days. You'd track this in our analytics dashboards.
  6. Metric: Device Uptime & Connectivity
  7. Desc: Overall availability and reliability of your owned devices in the field.
  8. Target: Maintain 99.9% uptime for your specific product's fleet.
  9. Freq: Daily/Weekly, monitored through AWS IoT Core/Azure IoT Hub logs.
  10. Example: If your device fleet experiences 0.1% downtime, that's roughly 8.7 hours of outage per device per year. You'll be on top of this, spotting trends and working with engineering to fix issues.
  11. Metric: Sprint Goal Completion Rate
  12. Desc: Percentage of committed user stories and tasks completed within a sprint.
  13. Target: Consistently achieve 85% or higher sprint goal completion.
  14. Freq: Bi-weekly, reviewed during sprint retrospectives in Jira.
  15. Example: If the team commits to 10 stories in a sprint, you'd aim to get 8 or 9 done. This shows you're planning well and unblocking the team effectively.
  16. Metric: Support Ticket Reduction (Feature-Specific)
  17. Desc: Decrease in customer support tickets directly related to your product's features post-release.
  18. Target: Reduce tickets for new features by 15% quarter-over-quarter.
  19. Freq: Quarterly, analysing support desk data.
  20. Example: After releasing a new device provisioning flow, you'd look to see a 15% drop in 'device setup issues' tickets compared to the previous quarter. If you don't, you need to figure out why.

Qualitative Metrics

  1. Metric: Cross-Functional Collaboration
  2. Desc: How well you work with different teams – hardware, firmware, software, sales – to get things done.
  3. Evidence: Engineering teams tell us you provide clear, actionable requirements. Sales feels you understand their customer needs. You're seen as the go-to person for questions about your product, not a blocker. You proactively bring teams together to solve problems, rather than waiting for things to blow up.
  4. Metric: Product Vision & Roadmap Clarity
  5. Desc: How clearly you articulate the 'what' and 'why' for your product, both internally and externally.
  6. Evidence: Your product backlog is well-organised and prioritised. You can explain the next 3-6 months of development for your product to anyone, from an engineer to a sales rep, and they'll get it. People understand the problem we're solving and how your features contribute.
  7. Metric: Proactive Problem Identification
  8. Desc: Your ability to spot potential issues (technical, market, customer) before they become big problems.
  9. Evidence: You're often the first to flag a potential component shortage, a looming firmware bug, or a shift in customer behaviour based on telemetry data. You don't just react; you anticipate. You bring solutions or options to the table, not just problems.
  10. Metric: Customer Empathy & Feedback Integration
  11. Desc: How effectively you understand customer pain points and translate them into product improvements.
  12. Evidence: You regularly talk to customers or support teams. Your feature proposals clearly link back to customer feedback or market needs. You can articulate the 'user story' behind every major piece of work, not just the technical spec. People see you as the voice of the customer.

Primary Traits

Supporting Traits

Primary Motivators

  1. Motivator: Seeing Tangible Impact
  2. Daily: You'll get a real kick out of seeing your product in customers' hands, solving their problems. It's not just code on a screen; it's a physical device doing something useful.
  3. Motivator: Solving Complex, Multi-Disciplinary Puzzles
  4. Daily: You thrive on the challenge of bringing together hardware, software, and cloud to create a cohesive product. It's like solving a giant, constantly evolving puzzle.
  5. Motivator: Driving Innovation in a Growing Field
  6. Daily: The IoT space is constantly evolving, and you'll be at the forefront, exploring new technologies and figuring out how to apply them to real products.

Potential Demotivators

Honestly, this role isn't for everyone. You'll spend a fair bit of time trying to explain to software-focused teams why a 'simple' change to the hardware isn't simple at all and requires months, not weeks. You'll deal with the constant whack-a-mole of supply chain issues, where one component finally becomes available, only for another to go out of stock. You'll also build features or even entire devices that, for various reasons (market shift, cost, technical blockers), never actually make it to production. If you need every piece of your work to ship, you'll find this frustrating.

Common Frustrations

  1. The Tyranny of Hardware Timelines: Explaining for the tenth time that a 'minor' hardware tweak means a 6-month board re-spin and new regulatory certifications.
  2. The 'Full-Stack' Blame Game: When a device goes offline, it's often a five-way finger-pointing match between hardware, firmware, connectivity, cloud, and the application team. You're the UN peacekeeper.
  3. Supply Chain Whack-a-Mole: You finally secure that microcontroller, then the cellular module suddenly has a 52-week lead time. Your roadmap is always at the mercy of global logistics.
  4. Physics is Undefeated: Dealing with real-world issues like battery degradation, RF interference in dense areas, or devices being installed in metal boxes where they shouldn't be.
  5. The Long Tail of Old Firmware: Supporting customers who refuse to update, meaning you're maintaining backend compatibility for multiple firmware versions, some with known quirks.

What Role Doesn't Offer

  1. A purely software-focused environment with rapid iteration cycles.
  2. Complete control over every aspect of the product, especially hardware components.
  3. A role where you're always building something completely new; sometimes it's about optimising existing products.
  4. Predictable, routine work; expect unexpected issues with devices in the field.

ADHD Positives

  1. The fast-paced, constantly changing nature of IoT problem-solving can be engaging and stimulating.
  2. The need to jump between different technical domains (hardware, software, cloud) can suit those who thrive on variety.
  3. The role often involves visualising complex systems, which can be a strength for many with ADHD.

ADHD Challenges and Accommodations

  1. Managing multiple, often conflicting priorities and long-term hardware timelines can be challenging. We use visual roadmaps and clear prioritisation frameworks to help.
  2. Documentation, while essential, can be tedious. We encourage using AI tools for drafting and provide templates to simplify the process.
  3. We offer flexible working arrangements to help manage energy levels and focus, and encourage regular check-ins to re-prioritise.

Dyslexia Positives

  1. Strong spatial reasoning and systems thinking, often associated with dyslexia, are highly valuable for understanding complex IoT architectures.
  2. The emphasis on verbal communication and problem-solving in cross-functional meetings can be a strength.
  3. Visual tools like Miro for brainstorming and diagramming are heavily used.

Dyslexia Challenges and Accommodations

  1. Reading and writing extensive technical documentation (PRDs, specs) can be demanding. We use tools with dictation and text-to-speech features, and encourage visual aids.
  2. Proofreading detailed requirements or release notes might require extra time. We promote peer review and AI-powered grammar checkers.
  3. We can provide access to assistive technologies and offer flexible deadlines for written deliverables when needed.

Autism Positives

  1. The logical, systematic nature of troubleshooting complex IoT systems can be a strong fit.
  2. A preference for clear, direct communication and factual analysis is highly valued in technical product management.
  3. The opportunity to deep-dive into specific technical domains (e.g., wireless protocols, sensor data) can be very rewarding.

Autism Challenges and Accommodations

  1. Navigating complex social dynamics and unspoken expectations in cross-functional negotiation can be tough. We aim for direct, transparent communication and provide clear meeting agendas.
  2. Unexpected changes in priorities or technical issues can be disruptive. We try to communicate changes clearly and provide as much notice as possible.
  3. We offer quiet working spaces, allow for remote work when appropriate, and support the use of noise-cancelling headphones to manage sensory input.

Sensory Considerations

Our office environment is typically a mix of open-plan and quiet zones. There can be moderate noise levels in collaborative areas, but we have dedicated focus rooms and encourage the use of noise-cancelling headphones. We also offer flexible working from home, which can help manage individual sensory needs. Social interactions are frequent but generally structured around specific tasks and projects, rather than constant informal chatter.

Flexibility Notes

We believe in output over presence. We're happy to discuss flexible working patterns, including adjusted hours or a hybrid remote/office setup, to ensure you can do your best work. We focus on results, not how many hours you spend at your desk.

Key Responsibilities

Experience Levels Responsibilities

  1. Level: Mid-Level Professional (IoT Product Manager)
  2. Responsibilities: Own the product backlog and roadmap for a specific IoT device or feature set. That means you're figuring out what needs to be built next, and why, for your area.
  3. Translate high-level business goals into detailed user stories and clear technical requirements for hardware, firmware, and cloud engineering teams. Get this wrong, and they'll build the wrong thing.
  4. Coordinate the full product lifecycle for your assigned device, from concept validation (is this even a good idea?) through to launch and ongoing maintenance. You'll be the go-to person.
  5. Work closely with engineering teams during development, answering questions, unblocking issues, and ensuring what's being built matches the original intent. You're their first port of call.
  6. Analyse device telemetry data and customer feedback to identify opportunities for product improvement or to spot potential issues. This means digging into dashboards and talking to real users.
  7. Help plan and execute Over-the-Air (OTA) firmware updates, making sure we roll them out safely and effectively to avoid 'bricking' devices.
  8. Collaborate with sales and marketing to develop compelling product messaging and launch materials, making sure they understand what we've built and why it matters to customers.
  9. Supervision: You'll typically have weekly check-ins with your Senior Product Manager to discuss progress, roadblocks, and strategic alignment. For routine tasks, you'll work independently, but you'll escalate novel or high-risk problems for guidance. Think of it as having a safety net, but we expect you to be walking the tightrope yourself most of the time.
  10. Decision: You'll have full ownership over the prioritisation of your product's backlog and the detailed feature specifications within your assigned scope. You can make routine technical decisions (e.g., specific data fields in a telemetry payload) but you'll need to consult your Senior PM on significant changes to the product roadmap, major architectural shifts, or any budget decisions over, say, £5,000 for a new component or tool. Any external commitments or public statements about the product will need approval.
  11. Success: You'll know you're succeeding when your engineering teams consistently deliver features that align with your requirements, customers are happy with your product's performance, and you're seen as the expert for your specific device. Also, hitting those feature adoption and uptime targets we talked about earlier is a big one.

Decision-Making Authority

Save 15-25 Hours Weekly with AI-Powered Product Management

Let's be real, product management can be a slog of documentation, data analysis, and repetitive tasks. But what if you could offload a significant chunk of that to an intelligent assistant? We're building an AI Productivity Hub specifically for our Technical_roles team, and as an IoT Product Manager, you'll be at the forefront of using these tools to supercharge your day.

ID:

Tool: PRD & User Story Generation

Benefit: Use an AI assistant (like ChatGPT or Copilot) trained on our existing documentation and product guidelines. You'll draft initial Product Requirements Documents (PRDs), user stories, and acceptance criteria from your high-level feature briefs in minutes, not hours. Think of it as having a highly efficient junior PM who never sleeps.

ID:

Tool: Anomaly Detection in Telemetry

Benefit: Stop manually sifting through endless logs. You'll use AI/ML models built into our analytics platforms (like Datadog or custom solutions) to automatically flag anomalies, predict component failures, or identify unusual device usage patterns across millions of data points. This means you'll spot problems before they become crises.

ID:

Tool: Competitive Hardware Teardown Analysis

Benefit: Want to know what our competitors are up to? Use AI-powered visual analysis tools to quickly scan competitor hardware teardown reports and datasheets. It'll automatically summarise key components, estimate Bill of Materials (BOM) costs, and highlight differences in design philosophy, saving you days of manual research.

ID:

Tool: Multi-Audience Release Notes

Benefit: Draft one detailed technical changelog for a new firmware release, and then use an AI assistant to instantly rewrite and tailor it for different audiences. Get a high-level summary for executives, a benefits-focused version for marketing, and a simplified guide for end-users, all ready in moments. No more hours spent tweaking wording for different teams.

Expect to save 15-25 hours weekly on repetitive tasks. Weekly time savings potential
You'll be using 3-5 core AI tools, integrated into your workflow. Typical tool investment
Explore AI Productivity for IoT Product Manager →

12-15 specific tools & techniques with implementation guides

Competency Requirements

Foundation Skills (Transferable)

These are the bedrock skills everyone at Zavmo needs. They're not specific to IoT, but you won't get far without them. Think of them as your professional toolkit.

Functional Skills (Role-Specific Technical)

Now we're getting into the nitty-gritty – the specific skills and tools you'll use day-to-day to manage our IoT products. These are the practical abilities that will make you effective in this role.

Technical Competencies

Digital Tools

Industry Knowledge

Regulatory Compliance Regulations

Essential Prerequisites

Career Pathway Context

We're looking for someone who's already got a couple of years under their belt in product or a closely related technical discipline. You might have been an Associate Product Manager, a Business Analyst in a tech company, or even a Software Engineer who's been heavily involved in product decisions. We don't expect you to be an expert in everything, but you should have a solid foundation and be ready to take ownership of a specific product area.

Qualifications & Credentials

Emerging Foundation Skills

Advancing Technical Skills

Future Skills Closing Note

The key here isn't to become a deep technical expert in every single one of these areas. Instead, it's about building enough understanding to ask the right questions, challenge assumptions, and make informed product decisions. Your role is to bridge the gap, and that gap is constantly widening with new tech. Keep learning, keep asking, and you'll thrive.

Education Requirements

Experience Requirements

You'll need roughly 2-5 years of experience in product management, or a closely related technical role (like a Technical Business Analyst, Embedded Software Engineer, or Systems Engineer) where you had significant exposure to product strategy and customer needs. We're looking for someone who has already owned a product backlog, written detailed requirements, and worked directly with engineering teams to ship features, ideally for a physical or connected product. This isn't your first rodeo, but you're still keen to learn and grow.

Preferred Certifications

Recommended Activities

Career Progression Pathways

Entry Paths to This Role

Career Progression From This Role

Long Term Vision Potential Roles

Sector Mobility

The skills you'll gain as an IoT Product Manager are highly transferable. You could move into other product management roles in different industries (e.g., SaaS, FinTech, MedTech), or even transition into more strategic roles like Technical Programme Management, Solutions Architecture, or even into a startup founder position. The ability to bridge technical and business needs for complex systems is always in demand.

How Zavmo Delivers This Role's Development

DISCOVER Phase: Skills Gap Analysis

Zavmo maps your current competencies against all requirements in this job description through conversational assessment. We evaluate your foundation skills (communication, strategic thinking), functional skills (CRM expertise, negotiation), and readiness for career progression.

Output: Personalised skills gap heat map showing strengths and priorities, estimated time to competency, neurodiversity accommodations.

DISCUSS Phase: Personalised Learning Pathway

Based on your DISCOVER results, Zavmo creates a personalised learning plan prioritised by impact: foundation skills first, then functional skills. We adapt to your learning style, pace, and neurodiversity needs (ADHD, dyslexia, autism).

Output: Week-by-week schedule, each module linked to specific job responsibilities, checkpoints and milestones.

DELIVER Phase: Conversational Learning

Learn through conversation, not boring modules. Zavmo uses 10 conversation types (Socratic dialogue, role-play, coaching, case studies) to build competence. Practice difficult QBR presentations, negotiate tough renewals, and handle churn conversations in a safe AI environment before facing real clients.

Example: "For 'Stakeholder Mapping', Zavmo will guide you through analysing a complex enterprise account, identifying key decision-makers, and building an engagement strategy."

DEMONSTRATE Phase: Competency Assessment

Zavmo automatically builds your evidence portfolio as you learn. Every conversation, practice scenario, and application example is captured and mapped to NOS performance criteria. When ready, your portfolio supports OFQUAL qualification claims and demonstrates competence to employers.

Output: Competency matrix, evidence portfolio (downloadable), qualification readiness, career progression score.

Discover Your Skills Gap Explore Learning Paths
↑