Jobs · Administrative · Illinois

Customer Program Associate

WEC Energy Group · Chicago, IL · 1 mo ago
Administrative$68k/yrFull-time
We need to output HTML fragment with sections: About Us (maybe heading "About Us"? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings if appropriate? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So likely we should use those headings exactly if content exists. The posting includes "About Us" section, "Job Summary", "Job Responsibilities", "Minimum Qualifications", "Preferred Qualifications". Also includes Pay Range. No explicit Benefits or Schedule beyond mention hybrid with potential for 50% travel. That's schedule info? Could be schedule: hybrid with potential for 50% travel. That's schedule info. Benefits: they mention competitive pay and benefits but not specifics. So we should not create Benefits section unless specifics given. They said "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay is stated (range). Schedule: they mention hybrid with potential for 50% travel. That's schedule info. So we can include Schedule section. Benefits: they mention "competitive pay and benefits" but no detail; we should not create Benefits section because no specifics. So we will include sections: About Us (maybe "About the role"? But we have About Us content. Could use "About the role" heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those exact headings. However the posting has "About Us" and "Job Summary". We could map About Us to "About the role"? But that might misrepresent. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must only use those exact headings, but they are examples. Probably we can use headings that match content: About Us, Job Summary, Responsibilities, Minimum Qualifications, Preferred Qualifications, Pay, Schedule. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those as headings if they exist. Since we have About Us, we could use About the role as heading and put About Us content there. But that might be okay. However they also said "Do NOT repeat the job title as a heading (the page already shows it)". So we shouldn't add extra heading for job title. Using About the role is fine. We need to decide: Should we follow the examples strictly? Usually these tasks expect you to use those exact headings when applicable. Let's see: The posting includes "About Us" which is similar to "About the role". Could map. "Job Summary" could be considered part of About the role? Might be redundant. But we could have a section "About the role" containing both About Us and Job Summary. However they said "Prefer a few substantive sections over many thin ones." So combining About Us and Job Summary into About the role makes sense. Responsibilities: we have Job Responsibilities. Requirements: we have Minimum Qualifications (maybe Requirements). Qualifications: we have Preferred Qualifications. Skills: we could extract skills from qualifications but maybe not needed. Could create Skills section from preferred qualifications? But they said prefer few substantive sections; we could skip Skills if not explicit. Pay: we have Pay Range. Schedule: we have hybrid with potential for 50% travel. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. We need to use

for each heading. Use
  • for any list of duties/requirements/benefits. For prose use

    . We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to include all content from About Us, Job Summary, Responsibilities, Minimum Qualifications, Preferred Qualifications, Pay Range, Schedule (hybrid with potential for 50% travel). Also maybe mention location: Chicago, Illinois. That's substantive; include in About the role maybe. We must not include Job ID/requisition numbers (none). Remove cookie/navigation/legal/EEO etc. The posting includes EEO statement at end; we must remove that. Also remove "Learn more at WEC Energy Group will only employ those who are legally authorized to work in the United States..." etc. That's legal boilerplate; remove. Also remove "End Date: 09/25/2026" maybe? That's metadata; could be considered minor metadata; we could fold into short p or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." End Date is minor metadata; we could drop it or include in a short p. Probably drop it. Also remove "Pay Range Minimum: $68,436.68 Pay Range Maximum: $102,655.28 The pay range reflects..." We need to keep pay range info. That's substantive. We need to keep "This position is currently hybrid with potential for 50% travel." That's schedule. Now craft HTML. Structure:

    About the role

    WEC Business Services LLC, a subsidiary of WEC Energy Group, is seeking a Customer Program Associate in our Chicago, Illinois location. This position is currently hybrid with potential for 50% travel. WEC Energy Group is one of the nation’s largest electric generation and distribution and natural gas delivery holding companies serving 4.7 million customers across the Midwest. We are committed to providing clean, reliable, and affordable energy in an environmentally sustainable manner. Customers are the heart of our business, and we work every day to help grow and support communities where we provide vital energy services. As a Fortune 500 company, we value and develop our employees who are making a difference in a mission that matters. We don’t just offer a job; we provide fulfilling careers where safety and well-being are paramount. Join our team and experience first-hand our commitment to your success. We offer competitive pay and benefits to recognize your hard work and dedication. If you’re talented, energetic and ready for a career with a future, we want you on our team. We are powered by a diverse and inclusive workforce fueled by the pride in what we do. If you're driven by the passion to change lives, this is the place for you.

    But note we already mentioned hybrid schedule in About the role; maybe better to put schedule in its own section. However we already included schedule info in About the role; but we also need a Schedule section. To avoid duplication, we could keep schedule info only in Schedule section and not repeat in About the role. But About the role currently includes "This position is currently hybrid with potential for 50% travel." If we move that to Schedule section, we should remove from About the role. Let's do that: About the role excludes schedule line. Thus About the role paragraph: WEC Business Services LLC, a subsidiary of WEC Energy Group, is seeking a Customer Program Associate in our Chicago, Illinois location. WEC Energy Group is one of the nation’s largest electric generation and distribution and natural gas delivery holding companies serving 4.7 million customers across the Midwest. We are committed to providing clean, reliable, and affordable energy in an environmentally sustainable manner. Customers are the heart of our business, and we work every day to help grow and support communities where we provide vital energy services. As a Fortune 500 company, we value and develop our employees who are making a difference in a mission that matters. We don’t just offer a job; we provide fulfilling careers where safety and well-being are paramount. Join our team and experience first-hand our commitment to your success. We offer competitive pay and benefits to recognize your hard work and dedication. If you’re talented, energetic and ready for a career with a future, we want you on our team. We are powered by a diverse and inclusive workforce fueled by the pride in what we do. If you're driven by the passion to change lives, this is the place for you. Now Job Summary: we could incorporate into About the role? But we already have About the role; maybe we should have separate section for Job Summary? But we limited sections to those headings; we could add Job Summary as part of About the role or maybe we could have a separate section "About the role" includes About Us and Job Summary. Let's include Job Summary content in About the role after the location sentence? Actually we omitted location sentence; we could add Job Summary after location. Let's restructure: About the role: includes location sentence, then Job Summary paragraph. Thus:

    About the role

    WEC Business Services LLC, a subsidiary of WEC Energy Group, is seeking a Customer Program Associate in our Chicago, Illinois location.

    The Customer Program Associate supports the development and implementation of comprehensive engagement strategies and activities to support the company’s natural gas energy efficiency goals. This role will support the residential and business programs and will involve close collaboration with internal and external teams to ensure program success including goals, budget and customer satisfaction. The Customer Program Associate brings a high level of professionalism, exceptional communication skills, and strong organizational abilities, with a proven talent for managing details and driving successful outcomes. Successful candidates will embrace the opportunity to learn on the job, develop expertise in energy efficiency programs, and contribute to meaningful work that supports a clean energy future.

    That preserves both. Now Responsibilities:

    Responsibilities

    • Support the planning, coordination, and execution of customer energy efficiency programs and related initiatives, including support for multiple program offerings and customer engagement activities
    • Lead the Trade Ally (program partner contractors) development effort, with a focus on strengthening and expanding the network of participating contractors
    • Build, maintain and enhance relationships with customers, trade allies, implementation contractors, and utility stakeholders to ensure successful program delivery and a positive customer experience
    • Conduct field visits, customer site visits, trade ally meetings to gain firsthand insight into program delivery, customer interactions, and operational challenges
    • Support outreach efforts to customers and trade allies to promote program participation and engagement
    • Identify opportunities for program improvements and support implementation efforts
    • Support the development, tracking and reporting of program metrics
    • Lead daily customer experience support for assigned programs and initiatives, including management of customer inquiries and issue resolution
    • Plan and implement customer satisfaction surveys and reports
    • Assists with departmental ad hoc projects as needed
    Now Requirements (Minimum Qualifications):

    Requirements

    • Bachelors degree required. Preferred majors: Business Administration, Marketing, Engineering, Public Policy, Social Sciences, or related discipline
    • Entry level with some relevant experience preferred
    • ...
    • ...
    . Now Qualifications (Preferred Qualifications):

    Qualifications

    • Experience in program coordination, project management, customer-facing operations, account management, energy efficiency, utilities, or a related field
    • Strong project management, analysis, decision making and problem-solving skills
    • Knowledge of or interest in learning the utility and energy efficiency industries. Experience supporting program implementation, operations, customer engagement, or project coordination is preferred
    • Excellent interpersonal and communication skills (both written and verbal)
    • Experience working with customers, contractors, vendors, external partners, or other stakeholders in a customer service, program support, project coordination, or business operations capacity
    • Demonstrated ability to build and maintain productive relationships with customers, contractors, trade allies, and internal team members
    • Excellent

Similar jobs