Director, Product Management
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. The posting includes: Role Overview (like About the role), Key Responsibilities, Required Qualifications, Preferred Qualifications, Success Measures. Also maybe Business Ownership etc but those are part of responsibilities. We need to decide which sections to include: About the role (role overview), Responsibilities (Key Responsibilities), Qualifications (maybe combine Required and Preferred? Could separate but they said prefer few substantive sections over many thin ones. Could have Qualifications section containing both required and preferred? But they gave examples of headings: Requirements, Qualifications, Skills. Could use Qualifications for required, and maybe Skills for preferred? However preferred qualifications are more like preferred experience. Could treat as Qualifications (required) and Skills (preferred). Or we could have Requirements (maybe required) and Qualifications (preferred). Let's decide: Use About the role
for Role Overview. Responsibilities
for Key Responsibilities. Qualifications
for Required Qualifications. Skills
for Preferred Qualifications. Success Measures
maybe not in list but could be considered as something like "Success Measures" not in given list but we could still include if real content. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those. So we can add Success Measures as heading. Ensure we don't create sections with filler. All have content.
We need to use - for any list of duties/requirements/benefits, and
for prose. So we need to convert paragraphs into
. For bullet lists, we need to detect bullet points. The text includes many sentences but not explicit bullet list markers. However we can treat each responsibility as separate bullet? The instruction: use
- for any list of duties/requirements/benefits. The posting has enumerated responsibilities but not bullet list. We could still wrap each responsibility sentence in
- inside a
. But we need to decide if it's a list. The responsibilities are multiple paragraphs each starting with a bold heading like "Product Strategy and Roadmap". Could treat each as a list item. Similarly for qualifications: each bullet? Not explicit bullet. Safer to keep as for prose, not list. But instruction says use
- for any list of duties/requirements/benefits. If we don't have explicit list markers, we could still treat as list? Might be safer to keep as
for prose, as they didn't explicitly say we must convert to list if not bullet. However they said "any list of duties/requirements/benefits". The responsibilities are a list of duties. So we should make a list.
Thus we need to parse the responsibilities section into items. The responsibilities section includes headings like "Product Strategy and Roadmap", "Hardware, Firmware, and Platform Definition", etc. Each has multiple sentences. We could make each heading as a list item with its description inside maybe
inside
- . Simpler: each heading as
- with the paragraph(s) inside.
Similarly for qualifications: Required Qualifications list items each line? Could treat each sentence as list item.
Preferred Qualifications similarly.
Success Measures also list.
We'll produce HTML:
About the role
Role OverviewThe Director of Edge Devices Product Management will lead ...
But we need to remove duplicated lines? The Role Overview paragraph is long; we keep as is.
We must not repeat job title as heading; we are using About the role.
We must not include Job ID etc.
We must remove boilerplate: none present.
Now produce HTML.
Let's craft.
We'll need to escape any HTML special characters? Not needed.
We'll produce:
About the role
The Director of Edge Devices Product Management will lead the strategy, roadmap, and lifecycle management for connected hardware and software products serving commercial fleet, transportation, logistics, construction, field service, asset-intensive customers, and Industrial Equipment OEMs. This leader will define and deliver rugged, scalable, and cost-effective telematics devices, vehicle and equipment gateways, accessories, sensors, and edge-connected solutions that collect high-quality vehicle and machine data and enable fleet safety, compliance, maintenance, utilization, sustainability, asset productivity, equipment uptime, and operational efficiency use cases. This role sits at the intersection of hardware, firmware, embedded systems, wireless connectivity, cloud platforms, data pipelines, customer operations, OEM partner requirements, and go-to-market execution. The ideal candidate is a product leader who can translate real-world fleet and industrial equipment problems into differentiated hardware capabilities, balance performance and cost trade-offs, and partner deeply with engineering, supply chain, operations, sales, support, customers, and equipment manufacturers to bring reliable products to market at scale.
Then Responsibilities:
Responsibilities
- Product Strategy and RoadmapOwn the multi-year hardware product vision, strategy, and roadmap for fleet vehicle telematics devices, gateways, asset trackers, sensors, accessories, and related edge platforms. Define product requirements based on customer needs, market trends, competitive analysis, regulatory requirements, fleet workflows, and business priorities. Prioritize roadmap investments across new product introductions, platform refreshes, cost reductions, reliability improvements, feature expansion, and end-of-life planning. Establish clear product positioning and value propositions for fleet operators, channel partners, Industrial Equipment OEMs, equipment dealers, upfitters, and internal commercial teams. Build product strategies that support both aftermarket installations and OEM-embedded programs, including factory-fit, dealer-installed, and private-label telematics models.
- Hardware, Firmware, and Platform DefinitionTranslate fleet, vehicle, and industrial equipment use cases into detailed hardware and firmware requirements covering vehicle and machine data acquisition, GNSS performance, cellular connectivity, Bluetooth, Wi-Fi, sensor interfaces, power management, diagnostics, I/O, edge processing, and over-the-air updates. Guide product decisions involving OBD-II, J1939, CAN bus, RP1226, BLE, Wi-Fi, LTE Cat-M, LTE Cat-1, 5G, GNSS, accelerometers, battery performance, antennas, ruggedization, environmental requirements, equipment controller interfaces, auxiliary I/O, and machine sensor integrations. Partner with engineering to define scalable architectures that support vehicle gateways, asset tracking, video telematics, driver identification, maintenance, compliance, EV, mixed-fleet use cases, industrial equipment monitoring, remote diagnostics, and OEM equipment data services. Ensure hardware products deliver reliable telemetry, accurate signals, robust installation experiences, and consistent operation across diverse vehicle classes, industrial equipment types, duty cycles, vibration profiles, power environments, and field conditions. Define capabilities for OEM-focused programs such as embedded telematics modules, equipment gateway variants, service tool compatibility, white-label configurations, provisioning workflows, and secure device identity management.
- Customer Discovery and Market InsightEngage directly with fleet customers, Industrial Equipment OEMs, equipment dealers, installers, drivers, technicians, service organizations, operations leaders, and partners to identify pain points and validate product requirements. Use field observations, pilot results, telemetry data, support trends, win/loss analysis, and competitive intelligence to inform product decisions. Represent the voice of the customer in executive planning, roadmap reviews, engineering trade-off discussions, and launch readiness decisions. Understand Industrial Equipment OEM business models, including factory integration, dealer service networks, equipment lifecycle management, warranty analytics, remote diagnostics, utilization reporting, and aftermarket service revenue opportunities.
- Execution, Launch, and Lifecycle ManagementLead cross-functional execution from concept through requirements, business case, development, validation, certification, pilot, launch, scale, and end-of-life. Partner with program management to manage milestones, risks, dependencies, and decision points across hardware, firmware, cloud, manufacturing, supply chain, support, and go-to-market teams. Drive field validation, beta programs, installation readiness, firmware release planning, quality gates, and launch criteria. Coordinate OEM program readiness across hardware configuration, firmware baselines, manufacturing test processes, documentation, service support, provisioning, certification, and partner launch timelines. Own lifecycle decisions including SKU rationalization, cost optimization, component obsolescence, warranty performance, returns analysis, and product refresh planning.
- Business Ownership and Commercial EnablementDevelop business cases that balance customer value, revenue potential, gross margin, bill of materials cost, certification cost, development effort, operational complexity, and long-term platform leverage. Partner with sales, marketing, finance, and operations on pricing, packaging, launch plans, sales enablement, competitive positioning, and customer adoption. Support strategic customer engagements, RFP/RFI responses, OEM partner discussions, executive briefings, reseller enablement, and industry events as the product expert for telematics hardware and connected equipment solutions. Partner with business development and sales to structure OEM programs, including product variants, minimum order quantities, branding, data ownership expectations, support models, commercial terms, and long-term lifecycle commitments. Define and monitor product success metrics including attach rate, activation rate, device reliability, installation success, telemetry quality, warranty rate, margin goals, OEM program penetration, and customer retention and satisfaction.
- Leadership and Team DevelopmentLead, mentor, and develop a team of product managers responsible for hardware and software platforms, accessories, integrations, and adjacent telematics capabilities. Build strong operating rhythms for roadmap planning, market research and trends, prioritization, executive communication, and cross-functional decision-making. Create a culture of customer obsession, technical rigor, data-informed decision-making, accountability, and high-quality execution.
Qualifications (Required):
Qualifications
- 10+ years of product management experience, including significant ownership of hardware, software, IoT, telematics, automotive, industrial equipment, OEM, or connected-device products.
- 5+ years of people leadership experience, including hiring, coaching, and developing product managers or cross-functional product leaders.
- Demonstrated success launching commercially successful hardware products from concept through scale in B2B, SaaS-enabled, subscription, or connected-device business models.
- Strong technical fluency in embedded systems, firmware, vehicle data, wireless connectivity, device-to-cloud architectures, telemetry quality, and hardware development trade-offs.
- Experience working with engineering, firmware, supply chain, manufacturing, operations, support, sales, marketing, finance, legal, and executive stakeholders.
- Ability to communicate complex technical and business topics clearly to customers, executives, engineering teams, and commercial audiences.
- Bachelor’s degree in engineering, computer science, product management, business, or a related technical field.
Skills (Preferred):
Skills
- Deep experience in fleet vehicle telematics, connected vehicle platforms, commercial transportation, logistics technology, field service, construction equipment, Industrial Equipment OEMs, heavy equipment, powered assets, or asset tracking.
- Familiarity with regulatory and certification requirements such as FCC, CE, ISED, PTCRB, carrier approvals, ELD and Tachograph related ecosystem needs, safety standards, and regional connectivity requirements.
- Experience with automotive, commercial vehicle, and equipment data standards including CAN, OBD-II, J1939, RP1226, diagnostic trouble codes, engine hours, od
- for any list of duties/requirements/benefits, and
for prose. So we need to convert paragraphs into
. For bullet lists, we need to detect bullet points. The text includes many sentences but not explicit bullet list markers. However we can treat each responsibility as separate bullet? The instruction: use
- for any list of duties/requirements/benefits. The posting has enumerated responsibilities but not bullet list. We could still wrap each responsibility sentence in
- inside a
- . But we need to decide if it's a list. The responsibilities are multiple paragraphs each starting with a bold heading like "Product Strategy and Roadmap". Could treat each as a list item. Similarly for qualifications: each bullet? Not explicit bullet. Safer to keep as
- for any list of duties/requirements/benefits. If we don't have explicit list markers, we could still treat as list? Might be safer to keep as
for prose, as they didn't explicitly say we must convert to list if not bullet. However they said "any list of duties/requirements/benefits". The responsibilities are a list of duties. So we should make a list. Thus we need to parse the responsibilities section into items. The responsibilities section includes headings like "Product Strategy and Roadmap", "Hardware, Firmware, and Platform Definition", etc. Each has multiple sentences. We could make each heading as a list item with its description inside maybe
inside
- . Simpler: each heading as
- with the paragraph(s) inside.
Similarly for qualifications: Required Qualifications list items each line? Could treat each sentence as list item.
Preferred Qualifications similarly.
Success Measures also list.
We'll produce HTML:
About the role
Role OverviewThe Director of Edge Devices Product Management will lead ...
But we need to remove duplicated lines? The Role Overview paragraph is long; we keep as is. We must not repeat job title as heading; we are using About the role. We must not include Job ID etc. We must remove boilerplate: none present. Now produce HTML. Let's craft. We'll need to escape any HTML special characters? Not needed. We'll produce:About the role
The Director of Edge Devices Product Management will lead the strategy, roadmap, and lifecycle management for connected hardware and software products serving commercial fleet, transportation, logistics, construction, field service, asset-intensive customers, and Industrial Equipment OEMs. This leader will define and deliver rugged, scalable, and cost-effective telematics devices, vehicle and equipment gateways, accessories, sensors, and edge-connected solutions that collect high-quality vehicle and machine data and enable fleet safety, compliance, maintenance, utilization, sustainability, asset productivity, equipment uptime, and operational efficiency use cases. This role sits at the intersection of hardware, firmware, embedded systems, wireless connectivity, cloud platforms, data pipelines, customer operations, OEM partner requirements, and go-to-market execution. The ideal candidate is a product leader who can translate real-world fleet and industrial equipment problems into differentiated hardware capabilities, balance performance and cost trade-offs, and partner deeply with engineering, supply chain, operations, sales, support, customers, and equipment manufacturers to bring reliable products to market at scale.
Then Responsibilities:Responsibilities
- Product Strategy and RoadmapOwn the multi-year hardware product vision, strategy, and roadmap for fleet vehicle telematics devices, gateways, asset trackers, sensors, accessories, and related edge platforms. Define product requirements based on customer needs, market trends, competitive analysis, regulatory requirements, fleet workflows, and business priorities. Prioritize roadmap investments across new product introductions, platform refreshes, cost reductions, reliability improvements, feature expansion, and end-of-life planning. Establish clear product positioning and value propositions for fleet operators, channel partners, Industrial Equipment OEMs, equipment dealers, upfitters, and internal commercial teams. Build product strategies that support both aftermarket installations and OEM-embedded programs, including factory-fit, dealer-installed, and private-label telematics models.
- Hardware, Firmware, and Platform DefinitionTranslate fleet, vehicle, and industrial equipment use cases into detailed hardware and firmware requirements covering vehicle and machine data acquisition, GNSS performance, cellular connectivity, Bluetooth, Wi-Fi, sensor interfaces, power management, diagnostics, I/O, edge processing, and over-the-air updates. Guide product decisions involving OBD-II, J1939, CAN bus, RP1226, BLE, Wi-Fi, LTE Cat-M, LTE Cat-1, 5G, GNSS, accelerometers, battery performance, antennas, ruggedization, environmental requirements, equipment controller interfaces, auxiliary I/O, and machine sensor integrations. Partner with engineering to define scalable architectures that support vehicle gateways, asset tracking, video telematics, driver identification, maintenance, compliance, EV, mixed-fleet use cases, industrial equipment monitoring, remote diagnostics, and OEM equipment data services. Ensure hardware products deliver reliable telemetry, accurate signals, robust installation experiences, and consistent operation across diverse vehicle classes, industrial equipment types, duty cycles, vibration profiles, power environments, and field conditions. Define capabilities for OEM-focused programs such as embedded telematics modules, equipment gateway variants, service tool compatibility, white-label configurations, provisioning workflows, and secure device identity management.
- Customer Discovery and Market InsightEngage directly with fleet customers, Industrial Equipment OEMs, equipment dealers, installers, drivers, technicians, service organizations, operations leaders, and partners to identify pain points and validate product requirements. Use field observations, pilot results, telemetry data, support trends, win/loss analysis, and competitive intelligence to inform product decisions. Represent the voice of the customer in executive planning, roadmap reviews, engineering trade-off discussions, and launch readiness decisions. Understand Industrial Equipment OEM business models, including factory integration, dealer service networks, equipment lifecycle management, warranty analytics, remote diagnostics, utilization reporting, and aftermarket service revenue opportunities.
- Execution, Launch, and Lifecycle ManagementLead cross-functional execution from concept through requirements, business case, development, validation, certification, pilot, launch, scale, and end-of-life. Partner with program management to manage milestones, risks, dependencies, and decision points across hardware, firmware, cloud, manufacturing, supply chain, support, and go-to-market teams. Drive field validation, beta programs, installation readiness, firmware release planning, quality gates, and launch criteria. Coordinate OEM program readiness across hardware configuration, firmware baselines, manufacturing test processes, documentation, service support, provisioning, certification, and partner launch timelines. Own lifecycle decisions including SKU rationalization, cost optimization, component obsolescence, warranty performance, returns analysis, and product refresh planning.
- Business Ownership and Commercial EnablementDevelop business cases that balance customer value, revenue potential, gross margin, bill of materials cost, certification cost, development effort, operational complexity, and long-term platform leverage. Partner with sales, marketing, finance, and operations on pricing, packaging, launch plans, sales enablement, competitive positioning, and customer adoption. Support strategic customer engagements, RFP/RFI responses, OEM partner discussions, executive briefings, reseller enablement, and industry events as the product expert for telematics hardware and connected equipment solutions. Partner with business development and sales to structure OEM programs, including product variants, minimum order quantities, branding, data ownership expectations, support models, commercial terms, and long-term lifecycle commitments. Define and monitor product success metrics including attach rate, activation rate, device reliability, installation success, telemetry quality, warranty rate, margin goals, OEM program penetration, and customer retention and satisfaction.
- Leadership and Team DevelopmentLead, mentor, and develop a team of product managers responsible for hardware and software platforms, accessories, integrations, and adjacent telematics capabilities. Build strong operating rhythms for roadmap planning, market research and trends, prioritization, executive communication, and cross-functional decision-making. Create a culture of customer obsession, technical rigor, data-informed decision-making, accountability, and high-quality execution.
Qualifications
- 10+ years of product management experience, including significant ownership of hardware, software, IoT, telematics, automotive, industrial equipment, OEM, or connected-device products.
- 5+ years of people leadership experience, including hiring, coaching, and developing product managers or cross-functional product leaders.
- Demonstrated success launching commercially successful hardware products from concept through scale in B2B, SaaS-enabled, subscription, or connected-device business models.
- Strong technical fluency in embedded systems, firmware, vehicle data, wireless connectivity, device-to-cloud architectures, telemetry quality, and hardware development trade-offs.
- Experience working with engineering, firmware, supply chain, manufacturing, operations, support, sales, marketing, finance, legal, and executive stakeholders.
- Ability to communicate complex technical and business topics clearly to customers, executives, engineering teams, and commercial audiences.
- Bachelor’s degree in engineering, computer science, product management, business, or a related technical field.
Skills
- Deep experience in fleet vehicle telematics, connected vehicle platforms, commercial transportation, logistics technology, field service, construction equipment, Industrial Equipment OEMs, heavy equipment, powered assets, or asset tracking.
- Familiarity with regulatory and certification requirements such as FCC, CE, ISED, PTCRB, carrier approvals, ELD and Tachograph related ecosystem needs, safety standards, and regional connectivity requirements.
- Experience with automotive, commercial vehicle, and equipment data standards including CAN, OBD-II, J1939, RP1226, diagnostic trouble codes, engine hours, od
for prose, not list. But instruction says use
- for any list of duties/requirements/benefits. If we don't have explicit list markers, we could still treat as list? Might be safer to keep as