Hardware Product Manager

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate. We need to parse the posting: It includes "About PassiveLogic®" (company description) maybe not needed as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections for those headings only if content exists. We have content: About The Role (heading). That's "About the role". So we can have

About the role

with prose. Then "What You’ll Do" corresponds to Responsibilities. So

Responsibilities

with list of duties. Then "What You’ll Bring" includes requirements, qualifications, skills. We need to split into Requirements, Qualifications, Skills maybe. The posting lists many bullet-like sentences. We need to preserve all substantive info. We can create sections: Requirements (maybe core requirements), Qualifications (education/experience), Skills (specific skills). But we must not create sections with filler. We need to decide based on content. The posting includes: "You must have A technical or engineering background, including a BS/MS/PhD or related degree in electrical, mechanical, systems, manufacturing, or another deeply technical field." That's qualification. "Proven experience: 5+ years of experience in product management, technical product management, or a closely related product role, including direct responsibility for electronics hardware products." That's requirement/experience. "Experience guiding electronics hardware through multiple stages of the product lifecycle..." etc. "Electronics hardware product experience: A strong working understanding of electronics hardware development, including product requirements, printed circuit boards, embedded firmware, prototypes, verification and validation, certification, manufacturing readiness, and product release." "Exceptional Communication Skills: ..." "Organized and strategic: ..." "Collaborative mindset: ..." "Adaptability: ..." "Problem solving: ..." "You should have Experience shipping electronics hardware: Demonstrated ability to define and successfully launch electronics hardware products in a complex, cross-functional environment." "HVAC controls experience: Experience with HVAC control hardware, building automation systems, direct digital controls, controllers, sensors, actuators, thermostats, or related equipment is strongly preferred." "Strong product management skills: Proven ability to conduct customer discovery, define product requirements, prioritize roadmaps, build business cases, make tradeoffs, and measure product outcomes." "Hardware and software systems thinking: Experience managing products in which electronics hardware, embedded firmware, cloud or application software, and customer workflows must operate as one cohesive system." "Product documentation experience: The ability to create clear product requirement documents, use cases, acceptance criteria, decision records, launch plans, and leadership updates." "Alignment with Leadership: Ability to stay closely aligned with leadership (including the CEO) throughout the development process to ensure product vision and goals are met." "Passion for Design and Sustainability: Strong passion for thoughtful product design, sustainability, and green building, integrating these values into product strategy and decision-making." "It’s helpful to have HVAC and building controls knowledge: Experience with HVAC equipment, control sequences, building automation systems, direct digital controls, field controllers, sensors, actuators, or building-management-system integrations." "Electronics technical knowledge: Familiarity with printed circuit boards, microcontrollers, embedded firmware, power supplies, wired and wireless communications, enclosures, environmental constraints, and hardware test practices." "Hardware commercialization knowledge: Familiarity with bills of materials, component lifecycle management, certification, cost targets, supplier relationships, manufacturing, and production ramp." "Relevant industry experience: Experience working in building automation, HVAC, energy systems, IoT, industrial controls, robotics, or another industry that combines electronics hardware with software and real-world control." Then "Compensation, Benefits & Perks:" list: Competitive compensation, Generous equity share package, Medical, dental and vision coverage, Disability and life Insurance options, Flex PTO, Team-building events, Free catered lunch in the office Monday — Friday, Free ski pass (We are at the base of Big Cottonwood Canyon), Free National Park pass. Thus we have Benefits section. Pay: Not explicitly stated besides "Competitive compensation". That's vague but maybe considered pay? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "Competitive compensation" which is a statement about pay, albeit vague. Should we include Pay section? It says "Competitive compensation" is a statement about compensation. It's not a specific number but it's still stating compensation. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive compensation". So we can include Pay section with that phrase. However we also have Benefits section already. Schedule: Not mentioned. No schedule info. So we should not create Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to decide how to split content into these sections. We could put: - About the role: the paragraph under "About The Role" (starting "This is a career-defining opportunity..."). - Responsibilities: the bullet list under "What You’ll Do". We'll convert each sentence into

. - Requirements: maybe the core mandatory requirements: technical background, 5+ years experience, experience guiding hardware through lifecycle, electronics hardware product experience, exceptional communication skills, organized and strategic, collaborative mindset, adaptability, problem solving, experience shipping electronics hardware, HVAC controls experience (strongly preferred? maybe requirement?), strong product management skills, hardware and software systems thinking, product documentation experience, alignment with leadership, passion for design and sustainability. That's a lot; but we can treat many as requirements. - Qualifications: education (BS/MS/PhD), maybe also "You must have A technical or engineering background..." could be qualification. But we already used that in requirements. Might be overlapping. Better to follow typical sections: Requirements (must-haves), Qualifications (nice-to-haves), Skills (specific skills). However the posting mixes. Given instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But they ask to use those headings if content exists. We could decide to have only Requirements and Skills, and maybe Benefits and Pay. But we need to follow the instruction: use headings for those sections if we have content. It doesn't say we must include all; we can omit if no real specific content. So we could omit Qualifications if we think it's covered elsewhere. But we have education requirement which is qualification. Could put under Requirements. Simplify: Use sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We'll put education and experience under Requirements. Skills: communication, organized, collaborative, adaptability, problem solving, technical knowledge (electronics, HVAC, etc.), product management skills, systems thinking, documentation, leadership alignment, passion for design/sustainability, HVAC knowledge, electronics technical knowledge, hardware commercialization knowledge, relevant industry experience. That seems okay. Now we need to output only HTML fragment, no markdown fences. We'll produce:

About the role

This is a career-defining opportunity to play a crucial role in a hyper-scale AI company that is transforming the future of autonomous systems, energy, and the built environment. As a Hardware Product Manager at PassiveLogic, you will own the product vision, strategy, roadmap, and lifecycle for electronics hardware that powers autonomous building control. You will translate customer, market, and business needs into clear product requirements, guide cross-functional teams through development and launch, and ensure our hardware delivers meaningful value in real-world HVAC and building-control applications.

Responsibilities

• Lead hardware product strategy and roadmaps: Define the vision, positioning, priorities, and lifecycle strategy for electronics hardware products, balancing customer value, technical feasibility, business impact, and long-term platform goals.
• Translate customer needs into product requirements: Develop a deep understanding of building owners, operators, engineers, installers, and other users. Convert their needs into clear requirements, use cases, acceptance criteria, and product decisions.
• Drive cross-functional product development: Partner with electrical, mechanical, firmware, software, systems, design, test, manufacturing, supply chain, and quality teams from early concept through validation, launch, and ongoing product improvement.
• Make informed product tradeoffs: Evaluate customer value, technical performance, cost, schedule, reliability, manufacturability, and supply-chain constraints to make clear recommendations and keep the product aligned with its intended outcomes.
• Shape HVAC and building-control solutions: Apply your understanding of controls, connected devices, and the built environment to ensure our electronics hardware integrates effectively with HVAC equipment and building systems.
• Give teams the context they need to make good decisions: Clearly communicate product strategy, requirements, priorities, decisions, progress, and risks to stakeholders, creating alignment from engineering teams through company leadership.

Requirements

• A technical or engineering background, including a BS/MS/PhD or related degree in electrical, mechanical, systems, manufacturing, or another deeply technical field.
• 5+ years of experience in product management, technical product management, or a closely related product role, including direct responsibility for electronics hardware products.
• Experience guiding electronics hardware through multiple stages of the product lifecycle, from customer discovery and requirements definition through validation, launch, and ongoing improvement.
• A strong working understanding of electronics hardware development, including product requirements, printed circuit boards, embedded firmware, prototypes, verification and validation, certification, manufacturing readiness, and product release.
• Experience shipping electronics hardware: Demonstrated ability to define and successfully launch electronics hardware products in a complex, cross‑functional environment.
• HVAC controls experience: Experience with HVAC control hardware, building automation systems, direct digital controls, controllers, sensors, actuators, thermostats, or related equipment is strongly preferred.
• Strong product management skills: Proven ability to conduct customer discovery, define product requirements, prioritize roadmaps, build business cases, make tradeoffs, and measure product outcomes.
• Hardware and software systems thinking: Experience managing products in which electronics hardware, embedded firmware, cloud or application software, and customer workflows must operate as one cohesive system.
• Product documentation experience: Ability to create clear product requirement documents, use cases, acceptance criteria, decision records, launch plans, and leadership updates.
• Alignment with leadership: Ability to stay closely aligned with leadership (including the CEO) throughout the development process to ensure product vision and goals are met.
• Passion for design and sustainability: Strong passion for thoughtful product design, sustainability, and green building, integrating these values into product strategy and decision‑making.

Skills

• Exceptional communication skills: Articulating the “what” and “why” behind product decisions with clarity and precision across engineering, operations, customers, partners, and leadership.
• Organized and strategic: Skilled in creating product roadmaps, prioritizing opportunities, coordinating dependencies, and ensuring product decisions support customer needs, technical goals, and business objectives.
• Collaborative mindset: Working closely with electrical, mechanical, firmware, software, systems, test, manufacturing, quality, supply chain, sales, and customer‑facing teams to deliver a cohesive hardware product.
• Adaptability: Comfortable in a fast‑paced startup environment where customer insight evolves, priorities shift, and teams must learn and iterate quickly.
• Problem solving: Owning issues, clarifying underlying customer and business needs, bringing the right people together, and driving decisions through resolution.
• HVAC and building controls knowledge: Experience with HVAC equipment, control sequences, building automation systems, direct digital controls, field controllers, sensors, actuators,