Hardware Product Lead: V2X DC Bidirectional Charging

We need to output HTML fragment with sections: h3 headings for sections present: About the role? Actually we have "About Emporia Energy" maybe treat as About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. We need to include sections only when posting has real specific content. We have content: About Emporia Energy (mission etc). Could map to "About the role"? Actually "About Emporia Energy" is about company, not role. But we can treat as "About the role"? Might be better to have "About Emporia Energy" as a section heading? The instruction says use those example headings but not limited? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings if applicable. We have "About Emporia Energy" which could be "About the role"? Not exactly. Maybe we can use "About the role" to contain the description of role overview and mission? But we also have separate "Role Overview". Could combine. Better to follow the posting: sections: About Emporia Energy (company description), Mission, Vision and Values (maybe part of About), Role Overview, Responsibilities, Required Qualifications & Skills, Desired Qualifications & Skills, What We Offer (Compensation, Benefits, Career Growth). Also we have Pay (compensation) and Benefits. We need to avoid boilerplate like EEO etc. Remove that. We need to output only HTML fragment. Let's structure:

About Emporia Energy

...

Mission, Vision and Values

...

Role Overview

...

Responsibilities

• ...
...

Required Qualifications & Skills

• ...
...

Desired Qualifications & Skills

• ...
...

Compensation

The expected base salary range is $145,000 - $190,000, plus stock options. The offered salary will depend on numerous factors, including but not limited to work experience, skills, and internal equity considerations. The base salary does not include benefits or other incentives.

Benefits

• medical/dental/vision insurance
• 401(k)
• employee stock option program
• paid holidays plus unlimited PTO
• discounts on Emporia products and partner offerings

Career Growth

Be part of a fast-growing company at the forefront of home energy innovation.

We should not include Schedule (not present). Also we should not include Pay heading separate? We used Compensation. The instruction list includes Pay as example; we can use Pay heading. But we have compensation details. Use

Pay

maybe. But they said use those example headings; we can use Pay. Let's use Pay. Thus:

Pay

...

Benefits as above. Career Growth maybe not in list but we can include as section if content exists. It's okay. We must not include boilerplate like EEO etc. Now ensure we preserve all substantive information. Need to include details from About Emporia Energy paragraph, Mission Vision Values, Role Overview paragraphs, Responsibilities bullet points (need to capture all). Let's extract. About Emporia Energy paragraph: "Emporia is a leading technology company revolutionizing home energy by providing affordable, integrated solutions that empower homeowners to optimize energy usage to reduce costs and carbon footprint. Emporia’s Home Energy Management Platform is a powerful software system that connects their Vue Home Energy Monitor, Level 2 EV Charger, Smart Plugs, Home Battery, and third-party thermostats and appliances. By automating energy use through real-time monitoring and scheduling, the platform optimizes consumption, reduces costs, and simplifies home energy management—all within one intuitive app. With over 400,000 U.S. homes running Emporia’s energy management and EV charging hardware, we are now launching a national Third-Party Owned (TPO) home battery Virtual Power Plant — placing industrial-rated home batteries in residential homes to deliver power redundancy, utility cost savings, and grid peak demand services. By reducing energy waste and saving customers money, we’re helping create a healthier planet and a brighter future. For more information, visit emporiaenergy.com." Mission, Vision and Values: "Emporia was founded in 2018 with a clear purpose to revolutionize home energy, generate tangible customer savings, and accelerate the transition to a lower carbon future. We are striving to become the world's leading home energy management platform and build the largest virtual power plant. Customers First: We deliver exceptional service with empathy and responsiveness, building lasting trust in every interaction.Own the Outcome: We think like owners, taking responsibility for results and holding ourselves and each other accountable.Win Together: We succeed together through honesty, humility and humanity.Grit Gets it Done: We work hard, stay passionate, and persevere through challenges.Better Every Day: We challenge the status quo, take smart risks and aim to improve 1% every day." Role Overview: multiple paragraphs. Need to capture all. Let's copy role overview text: "Emporia's DC bidirectional program pairs white-labeled power electronics from an inverter supplier with the Vehicle Integration Board, the piece Emporia designs in-house. The design is in-flight. It needs one clear owner to drive it through validation, certification, and launch: the supplier on one side, our own board development on the other. Every Emporia hardware product moves through the same product development lifecycle (PDLC): Concept, Feasibility, EVT, DVT, PVT, Launch & Ramp, and Sustaining/EOL. This program is already well into design, so the weight of this role sits from EVT forward: program management, execution, and go-to-market rather than early concept work. The Product Lead is the DRI, the single-person decision maker for product definition, development, and launch. They do not necessarily do all the work, but they ensure the work gets done. Where this description says "own," it means accountable for the decision and the outcome, not doing the work alone. AI is what lets one person cover this much ground: draft the PRD and business case yourself, build initial concepts and designs, then spend your time on what AI cannot touch, like OEM and utility negotiations, certification, gate reviews, and unblocking the team. You report to SVP Product and own the program from here through Launch & Ramp, then hand the DRI role to Operations and Sustaining, moving into a supporting role. Bidirectional charging only works when the vehicle, the home, and the utility all cooperate, so launch depends as much on automotive OEM approval and utility interconnection as on the hardware. We move quickly by being disciplined, not by skipping process. The same stage-gates and deliverables stay in place: PRD, PCD, business case, design reviews, launch readiness. AI should accelerate the work to be done and minimize and remove hand offs along the way." Now Responsibilities: we have sections with bullet-like sentences. Need to convert each to

. Let's extract bullet points: Definition & Business Case: Closing Out Concept - Take over the PRD and PCD, close the open requirements, and lock the interface between the supplier's power electronics and our Vehicle Integration Board. - Own the business case and unit economics yourself, with AI as-needed: supplier cost, board cost, installed cost, and the price the market will carry. - Keep competitive positioning current and recommend go/no-go at each remaining stage gate. Program Delivery: EVT, DVT & PVT - Own getting it built, validated, and certified on schedule. - Own the schedule and gate reviews across the inverter supplier, our in-house board development, test, and Operations, holding the critical path in one place. - Work with Manufacturing Operations to hold the inverter supplier to specs, cost, quality, schedule, and roadmap. - Drive the Vehicle Integration Board through development and validation: electrical, firmware, bring-up, and test. - Drive the safety and interconnection path with Engineering and Compliance, including where the supplier's certifications end and system-level listing begins: UL 9741, ISO 15118, IEEE 1547, UL 1741 SB, and the labs and AHJ dialogue. - Know what their platform can and cannot do before committing to it. - Drive automotive OEM engagement to a validated, approved vehicle list at launch, including compatibility testing and each OEM's own approval process. - Work utility interconnection in every launch territory, and unblock the program yourself rather than waiting for someone else to raise it. Launch: Mass Production Ramp & Go-to-Market - Get the product to market and selling. - Own go-to-market working with Marketing, BD, and Customer Support: positioning, pricing, launch messaging, and the installer and channel readiness the product needs to sell. - Land the OEM side of launch: the approved vehicle list, partner coordination, and clear customer-facing compatibility guidance. - Own the ramp: first installs, commissioning results, early field performance, and the go/no-go on scaling. - Make the final call on when and how it ships, then hand off to Operations and Sustaining with baseline metrics, known issues, and the rationale behind key decisions. Sustaining & EOL: Supporting Role - After ramp, Operations and Sustaining own the product. Your role here reduces. - Be the person who knows why decisions were made. You are no longer the DRI. - Answer roadmap, customer-impact, and escalation questions when asked, supporting the resolution. - Carry field and quality lessons into your next program. Driving AI Adoption: Across Every Phase - Native AI-use runs through the whole job. Gates, deliverables, and approvals stay in place. The waiting between them goes away. Push that on the team, not just yourself. - Automate and optimize the manual, slow, or expensive steps you find in the PDLC. - Push yourself and the broader team to challenge the default approach without diluting the deliverable. - Use AI to build at the edge of capability. - Exemplify AI-enabled execution, encouraging Engineering, Operations, and partners to push past their traditional approach and deliver faster. - Build and share your own tools, prompts, and workflows instead of asking for headcount. - Be honest about where AI is not working, and feed real evidence back into how Emporia adopts it. Now Required Qualifications & Skills: list bullet points. Extract: - 5+ years across product management and program or delivery management for hardware, with full ownership through launch. - Strong program management across a mixed build: experience holding a white-label, ODM, or contract partner to specs, cost, and schedule while an in-house team delivers a critical component. - A track record as a DRI, accountable for outcomes and not just definition, comfortable with ambiguity and parallel workstreams, and willing to hand off cleanly at ramp. - Experience with EV charging, power electronics, inverters, or other grid-connected hardware. - Experience in a certification-heavy environment, and comfort owning a safety and interconnection approval path end to end. - Experience working with automotive OEMs, utilities, or other institutional partners whose approval gates your launch. - Heavy, fluent use of AI tools (Claude, ChatGPT, Grok or similar), plus a habit of building your own tooling instead of asking for headcount, and getting others to adopt it. - Business sense: you can own a business case, unit economics, and margin trade-offs leadership will bet on. - Strong cross-functional leadership: you lead through influence and escal