Energy Analyst

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, navigation, legal, EEO, etc. Also remove application instructions. Include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. Here we have salary range: "The annual base salary range for this position is $72,600.00 - $95,000.00." So we can include Pay section with that info. Schedule: "Hybrid work schedule" mentioned: "you’ll work out of our Raleigh, NC OR Morris Plains, NJ. location on a Hybrid work schedule." So schedule info present: hybrid schedule. So include Schedule section. Benefits: there is a Benefits section with details. So include Benefits. Qualifications: there is a "YOU MUST HAVE" list and "WE VALUE" list. Those are qualifications. So we can have a Qualifications section with both required and preferred? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications. Also maybe Skills? There's a list of skills like strong attention to detail, communication, etc. Could be Skills section. But we can also include them under Qualifications. However we have separate headings allowed: Skills. Might be better to separate required experience (Qualifications) and skills (Skills). But we need to ensure we don't create thin sections. Let's see content: Responsibilities: list of responsibilities after "Responsibilities KEY RESPONSIBILITIES". There's a bullet list (though not formatted as bullets but sentences). We'll convert to

  • . Qualifications: "YOU MUST HAVE" list (4 items). Then "WE VALUE" list (many items). Could split into Required Qualifications and Preferred Qualifications, but we only have Qualifications heading. Could include both under Qualifications with sub-lists? But we must use
    • for any list. Could have two
      under Qualifications: one for Required, one for Preferred. Or we could have separate sections: Requirements and Qualifications. The instruction list includes Requirements as possible heading. Could use Requirements for the "YOU MUST HAVE" and Qualifications for the "WE VALUE". But they said "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use both Requirements and Qualifications. Let's do that: Requirements heading for mandatory experience; Qualifications heading for preferred/valued experience and skills. Skills: maybe we can extract skills like strong attention to detail, organizational skills, written/verbal communication, ability to manage multiple priorities, coordinate activities. Those could go under Skills. But we need to avoid duplication. Let's structure: - About the role: maybe a short paragraph summarizing role from first paragraph: "As an Energy Analyst here at Honeywell, you will provide technical expertise to resolve complex issues and deliver exceptional customer service. You will report directly to our Program Manager, and you’ll work out of our Raleigh, NC OR Morris Plains, NJ. location on a Hybrid work schedule." That's prose. - Responsibilities: list of responsibilities from after "Responsibilities KEY RESPONSIBILITIES". We'll extract each sentence as list item. - Requirements: the "YOU MUST HAVE" list (4 items). We'll list each. - Qualifications: the "WE VALUE" list (many items). We'll list each. - Skills: maybe we can extract from the "WE VALUE" list items that are skills: "Strong attention to detail and organizational skills.", "Strong written and verbal communication skills.", "Ability to manage multiple priorities and coordinate activities across internal and external stakeholders." Those could be Skills. But they are already in WE VALUE list. To avoid duplication, maybe we just keep Qualifications and not separate Skills. However the instruction allows Skills section but not required. We could omit Skills if we think it's thin. But we have those skill statements; we could put them under Skills and keep Qualifications for experience/education. Let's see: WE VALUE list includes both experience and skills. Could split: Qualifications for education/experience, Skills for soft skills. That seems reasonable. Thus: Qualifications (education/experience): Associate’s degree or higher in Engineering, Computer Science, or a related discipline. Experience reviewing energy calculations and applying technical reference manuals (TRMs), program guidelines, or regulatory requirements. Experience working with utility representatives, evaluation, measurement and verification (EM&V) teams, information technology teams, or other program partners. Experience identifying program risks, managing changes, and supporting continuous improvement initiatives. Experience developing or enhancing data reports to support program reporting requirements. Experience analyzing program data and identifying trends in program delivery. Skills: Strong attention to detail and organizational skills. Strong written and verbal communication skills. Ability to manage multiple priorities and coordinate activities across internal and external stakeholders. Pay: salary range. Schedule: Hybrid work schedule (Raleigh, NC or Morris Plains, NJ location). Benefits: list of benefits. We must not include boilerplate like "Learn more (https://...)" maybe we can keep the link? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn more (https://benefits.honeywell.com/)" is maybe considered navigation? It's a link to benefits page; could be considered supplementary but not essential. Might be okay to keep? Safer to remove it as it's not substantive content about the job. Similarly "Learn more (https://www.honeywell.com/us/en)" about Honeywell description maybe considered boilerplate? The "About Honeywell" paragraph is substantive about company; we could keep that as part of About the role? Actually we have About Honeywell paragraph describing the company; that's not about the role but could be considered company overview. The instruction says include a section ONLY when the posting has real, specific content for it. The "About Honeywell" is generic company description; could be considered boilerplate but it's specific to Honeywell. Might be okay to keep as part of About the role? But we already have About the role paragraph. Could add a separate section "About Honeywell" but not in allowed headings list. Not needed. Probably we should omit the generic company description to stay focused on job. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About Honeywell paragraph is substantive about the company, but not about the job. Might be considered boilerplate but it's specific to Honeywell. However typical job postings include that; but the instruction didn't forbid company description. It said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. So we could keep it as a paragraph maybe under a heading "About Honeywell"? Not in allowed headings list but we could just include as a

      without heading? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. So we could incorporate the company description into the About the role paragraph or maybe omit. I'd omit to keep focused. Thus final HTML:

      About the role

      As an Energy Analyst here at Honeywell, you will provide technical expertise to resolve complex issues and deliver exceptional customer service. You will report directly to our Program Manager, and you’ll work out of our Raleigh, NC or Morris Plains, NJ location on a Hybrid work schedule.

      Responsibilities

      • Support the development and review of all program data for integrity and align IT strategy to provide effective project management expertise for Operations & IT teams.
      • Support Business leaders to define requirements and assist with execution of data solutions to support overall project delivery.
      • Review Energy Calculations of varying complexity to align with the regional and industry TRM for all measures of the program.
      • Interface with internal and external partners to ensure that all data updates are delivered on-time and within scope.
      • Stay abreast of all changes to the TRM, providing feedback on proposed changes, and guiding the team to implement those changes.
      • Develop and/or enhance data reports to support the regular required reporting submissions.
      • Analyze data for trends in program delivery.
      • Quality control activities and data integrity reviews.
      • Provide support in preparing reports and metrics related to program activities.
      • Stay informed about updates and changes to program guidelines, calculations, and requirements provided by the utility or the state BPU.
      • Monitor project update progress and interact with utility representatives from EM&V and IT to ensure alignment of data and results.
      • Project updates communication plans and timeline.
      • Risk identification and change management.
      • Align actions to IT priorities.
      • Lead continuous improvements.
      • Interact with program partners to promote program and gather information.

      Requirements

      • 2+ years of experience working with external partners, customers, utility representatives, or data providers.
      • 2+ years of experience working with relational databases, data analysis, or data reporting.
      • 2+ years of experience supporting energy efficiency programs, utility programs, rebate programs, or related energy services.
      • 2+ years of experience performing data quality reviews, analyzing program data, or preparing reports and metrics.

      Qualifications

      • Associate’s degree or higher in Engineering, Computer Science, or a related discipline.
      • Experience reviewing energy calculations and applying technical reference manuals (TRMs), program guidelines, or regulatory requirements.
      • Experience working with utility representatives, evaluation, measurement and verification (EM&V) teams, information technology teams, or other program partners.
      • Experience identifying program risks, managing changes, and supporting continuous improvement initiatives.
      • Experience developing or enhancing data reports to support program reporting requirements.
      • Experience analyzing program data and identifying trends in program delivery.

      Skills

      • Strong attention to detail and organizational skills.
      • Strong written and verbal communication skills.
      • Ability to manage multiple priorities and coordinate activities across internal and external stakeholders.

      Pay

      The annual base salary range for this position is $72,600.00 - $95,000.00.

      Schedule

      Hybrid work schedule (Raleigh, NC or Morris Plains, NJ location).

      Benefits

      • Employer subsidized Medical, Dental, Vision, and Life Insurance
      • Short-Term and Long-Term Disability
      • 401(k) match
      • Flexible Spending Accounts
      • Health Savings Accounts
      • Employee Assistance Program (EAP)
      • Educational Assistance
      • Parental Leave
      • Paid Time Off (for vacation, personal business, sick time, and parental leave)
      • 12 Paid Holidays
      Check for any duplicated content: we have responsibilities list includes some items that were also