Product Manager, HVAC Digital Sales Tools - REQ # 1443

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to extract sections: About the role (position summary), Responsibilities (essential functions), Qualifications (education, experience, skills), maybe Skills (some overlapping), Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - Position summary: description of role, driving strategy, planning, execution of portal, collaboration, etc. That's "About the role" or "Responsibilities"? Usually "About the role" is summary. We'll make a section "About the role" with paragraph(s). - Essential Functions: list of duties. That's responsibilities. We'll make a "Responsibilities" section with

  • items. - Qualifications: includes education, experience, knowledge, abilities. We'll make a "Qualifications" section with
    • items. - Skills: maybe we can combine with qualifications; but we could separate "Skills" if there is distinct list. The qualifications already includes many skill items. Could create a "Skills" section but risk duplication. The instruction: prefer few substantive sections over many thin ones. So we could combine qualifications and skills into one "Qualifications" section that includes both education/experience and skills. Or we could have "Qualifications" for education/experience and "Skills" for skill list. But we need to avoid thin sections. Let's see if we have enough content for both. Qualifications paragraph includes: B.S. in ... or equivalent experience. 3+ years’ experience in HVAC Design using VRF equipment. 3+ years’ experience in software product management or related field. Knowledge of HVAC design standards and building codes. Demonstrated experience leading agile projects... Ability to work effectively with developers... Proficiency understanding and integrating enterprise platforms such as SAP, Salesforce, Snowflake. Hands-on experience managing or developing enterprise/B2B web portals... Strong skills in eliciting business needs... Excellent communication skills... Adept at identifying, tracking, and mitigating risks... Track record of driving process enhancements... Commitment to delivering intuitive... Ability to analyze relevant KPIs... Team player demonstrating METUS core values... That's a mix of qualifications and skills. Could be one section "Qualifications & Skills". But headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to use "Qualifications" and maybe not separate Skills. Or we could use "Requirements" for education/experience and "Skills" for skill list. But we need to avoid thin sections. Let's see if we can split into two substantive sections: "Qualifications" (education + experience) and "Skills" (abilities). Both would have multiple bullet points, likely substantive enough. We also have Pay: base pay range $111,200 to $152,900, plus mention of target bonus plans, discretionary awards, 401(k), medical/dental/vision/life insurance, vacation 80 hours, sick 56 hours, 13 paid holidays, up to 12 weeks paid/unpaid leave. That's benefits and pay. Schedule: "This is a hybrid position with structured in-office days, and limited remote flexibility based on business needs, with specific schedule set by the manager in alignment with team need. Willing to travel up to 50% to for various Company meetings and training both domestically and possibly internationally." That's schedule and travel. Thus we can have sections: About the role (position summary), Responsibilities (essential functions), Qualifications (education/experience), Skills (abilities), Benefits (insurance, vacation, holidays, leave, 401k), Pay (base pay range, bonus), Schedule (hybrid, remote flexibility, travel). That's many sections but each is substantive. We must not include filler like "commensurate with experience". We have actual numbers. We must remove boilerplate: EEO, legal, application instructions, etc. Also remove duplicated lines. Also remove "About Mitsubishi Electric Trane Hvac Us" description? That's company overview; maybe we can include as part of "About the role"? But it's not about the role; it's about the company. The instruction: "Prefer a few substantive sections over many thin ones." The company overview could be considered boilerplate? It's not required but could be included as "About the company". However allowed headings list does not include About the company. Only About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add a section for company overview. We could incorporate relevant info into About the role? But it's not about the role. Better to omit it, as it's not required and not in allowed headings. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit company overview, we are losing substantive info. But maybe it's considered boilerplate? It's not navigation/legal/EEO, but it's about the company. The instruction didn't explicitly say to remove company overview, but we must preserve all substantive information. However the allowed headings list does not have a slot for company overview. Could we include it as a paragraph under About the role? That might be stretching but could be considered part of role context. The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add other headings. We could incorporate company overview into About the role as a paragraph, but that might be mixing. However the instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it." So we can fold minor metadata into a short

      . Company overview might be considered minor metadata? It's not metadata about the job, but it's about the company. Could be considered acceptable to include as a short paragraph under About the role. But we need to preserve all substantive information; we can include it as a paragraph within About the role. Thus About the role section will contain the position summary paragraph plus maybe a brief company overview sentence. Now we need to strip out boilerplate: EEO, legal, application instructions, etc. Also remove duplicated lines. Also remove "We offer an excellent compensation and benefits package including 401(K)." That's duplicate of benefits; we already have benefits. Also remove "In compliance with federal law, all persons hired will be required to verify identity..." etc. That's legal boilerplate; remove. Also remove "We are an equal employment opportunity employer..." etc. Remove. Also remove "The Company will not discharge..." etc. Remove. Also remove "To view the EEO is The Law Poster..." etc. Remove. Also remove "Applicants with a disability who need assistance..." etc. Remove. Also remove "More information is available at www.mitsubishicomfort.com ." Might be considered company info; we could keep as part of About the role? It's a URL; maybe we can keep as part of company overview. But it's not essential; but we can keep. Now we need to format. We'll produce:

      About the role

      Position summary: The Product Manager, MPro Sales Tools, will drive the strategy, planning, and execution of Mitsubishi Electric Trane HVAC US (METUS) next-generation sales portal, designed to empower customers and partners with rich data, seamless integration across DSB, SAP, Salesforce, and Snowflake, and intuitive digital workflows. This role requires close collaboration with cross-functional agile teams, stakeholder engagement, and direct contribution to product vision and continuous improvement. Managing and incorporating continuous improvement methodologies—such as LEAN UX and Agile best practices—will be central to delivering best-in-class web portal experiences that meet business goals and exceed customer expectations.

      Mitsubishi Electric Trane HVAC US (METUS) is a 50/50 joint venture between Trane Technologies and Mitsubishi Electric US, providing ductless and VRF systems in the United States and Latin America, marketing Zoned Comfort Solutions® and VRF technology.

      Then Responsibilities:

      Responsibilities

      • Acts as a primary liaison between METUS sales, marketing, UX, product management, operations, development, testing teams, and customers.
      • Coordinates and oversees product releases and major launches to ensure smooth integration into business operations.
      • Conducts weekly engagements with customers to gather requirements, define new features, user stories, and establish acceptance criteria.
      • Collaborates with the SCRUM team to establish realistic development timelines and deliverables.
      • Partners with product marketing to develop and execute effective communication strategies for market entry.
      • Trains support teams, enabling them to provide service resulting in a high level of customer success and satisfaction.
      • Identifies, documents, and prioritizes system issues and facilitate timely resolution.
      • Supports product testing and ensures compliance with market and regulatory requirements during new product introductions.
      • Manages projects effectively within established timelines and budget constraints.
      • Aligns internal and external resources to ensure the achievement of product and business goals.
      • Willing to travel up to 50% for various Company meetings and training both domestically and possibly internationally.
      • Perform other duties as assigned.
      Note: Travel item maybe belongs to Schedule but we can keep here; but we have Schedule section later. Might duplicate. Better to keep travel under Schedule. So remove travel from Responsibilities. Qualifications (education/experience):

      Qualifications

      • B.S. in Mechanical Engineering, Computer Science, Information Science, Management Information Systems or related field or equivalent experience.
      • 3+ years’ experience in HVAC Design using VRF equipment.
      • 3+ years’ experience in software product management or related field.
      • Knowledge of HVAC design standards and building codes.
      Skills:

      Skills

      • Demonstrated experience leading agile projects from inception to completion, ensuring delivery within established scope, timeline, and quality standards.
      • Ability to work effectively with developers, designers, business stakeholders, and external partners to deliver integrated digital solutions.
      • Proficiency understanding and integrating enterprise platforms such as SAP (ERP), Salesforce (CRM), and Snowflake (data analytics).
      • Hands-on experience managing or developing enterprise/B2B web portals, ideally in an industrial or manufacturing setting.
      • Strong skills in eliciting business needs from diverse stakeholders and translating them into actionable product requirements and user stories.
      • Excellent communication skills for liaising among technical teams, business users, and executive leadership to ensure project transparency and alignment.
      • Adept at identifying, tracking, and mitigating risks and removing impediments to ensure smooth project progress.
      • Track record of driving process enhancements, leveraging methodologies like LEAN UX and