Operations Specialist - ESS CS Team

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: 1. Company Overview - this is prose, should be

2. Position Overview - prose,

3. Primary Responsibilities - this has sub-sections: Accounting Operations, RMA Management, Warehouse and Inventory Operations, Other Duties. Each of these has bullet points. Should I make them subsections? The rules say use

for section headings like "Responsibilities". The posting has "Primary Responsibilities" as a heading, then sub-headings. I think I should use

for "Primary Responsibilities" and then maybe

for sub-sections? But the rules only mention

for section headings. It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention sub-headings. However, the content has clear sub-sections under Primary Responsibilities. I could either: - Make "Primary Responsibilities" an

and then each sub-section as

(but not specified) - Or make each sub-section an

? But that would be many headings. - Or keep "Primary Responsibilities" as

and then use

• for all bullet points, grouping them under the sub-sections with maybe labels? But the rules say use
  • for any list of duties/requirements/benefits. Looking at the example headings: "Responsibilities" is a section. The posting has "Primary Responsibilities" with sub-categories. I think the best is to have an

    for "Primary Responsibilities" and then for each sub-category, maybe use a

    ? But the instruction says only

    for section headings. However, it doesn't forbid other heading levels. But to be safe, I'll use

    for main sections only. The sub-categories could be presented as within list items? Or separate lists with a heading? The instruction: "Use

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

      for prose." It doesn't say we can't have multiple lists under one heading. I'll structure as: -

      Company Overview

      with

      -

      Position Overview

      with

      -

      Primary Responsibilities

      then for each sub-section (Accounting Operations, RMA Management, Warehouse and Inventory Operations, Other Duties) I'll create a
      with a leading
      • Accounting Operations
      ? That seems odd. Better to have separate
      for each sub-section, each preceded by a

      ? But the instruction says only

      for section headings. However, the example includes "Responsibilities" as a heading. The sub-sections are part of responsibilities. I think using

      is acceptable as it's semantic HTML. But the instruction might be strict. Let me re-read: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings. But to be safe, I'll use

      for the main sections only, and for sub-sections I'll use in a

      or just start the list with a bolded label? Actually, the instruction says "Use

      • for any list of duties/requirements/benefits". So I can have multiple
        under one

        . I'll separate each sub-section with a

        Accounting Operations

        then a

        . That seems clean. Next: "Key Knowledge, Skills and Abilities" - this is a list of skills/abilities. Should be

        Skills

        or

        Key Knowledge, Skills and Abilities

        ? The example includes "Skills". I'll use

        Key Knowledge, Skills and Abilities

        and then
        • for each bullet. "Education and Experience" - this is a list of requirements. Could be

          Requirements

          or

          Education and Experience

          . The example includes "Requirements". I'll use

          Education and Experience

          and then
          • . "Travel" - this is a single line. Could be part of Requirements or separate. The instruction says include a section ONLY when the posting has real, specific content. Travel is a specific requirement. I could include it as a

            under Education and Experience or as a separate

            Travel

            with

            . But the example includes "Schedule". Travel is not exactly schedule. I'll include it as a

            under Education and Experience or as a separate small section. Since it's a single line, I'll add it as a

            after the list. Also note: "Korean-English bilingual preferred" is a requirement. "A Bachelor’s Degree, or equivalent 1+ years work experience in customer service; or 1+ years work experience in logistics" - that's two bullet points. Now, remove boilerplate: The posting doesn't have cookie/navigation/legal/EEO/scam-warning. It has "Contract Operations Specialist - ESS CS Team Irvine, CA - on-site 5 days a week" - that's the job title and location. 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 I should not include the job title as a heading. The location and schedule (on-site 5 days a week) could be folded into a short

            maybe under a "Schedule" section? But the instruction says never create Schedule section unless the posting actually states them. The posting states "Irvine, CA - on-site 5 days a week". That's schedule and location. I could include a

            Schedule

            with

            On-site, 5 days a week in Irvine, CA.

            But the example includes "Schedule". However, the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state schedule (on-site 5 days a week). So I can include a Schedule section. Also location is mentioned. I'll include a

            Schedule

            with

            On-site, 5 days a week in Irvine, CA.

            Also "Travel 20% of travel may be required" - that's travel, not schedule. Could be under Requirements or separate. I'll include it in the Education and Experience section as a bullet or separate paragraph. Now, let's write the HTML. Structure:

            Company Overview

            LG Energy Solution Vertech, Inc. (LGES Vertech) is a leading provider of grid-scale integrated energy storage systems, delivering safe, reliable, and high‑performance solutions to customers worldwide. Powered by our proprietary AEROS® energy operating system, we use advanced monitoring and controls to help customers optimize system performance and maximize the value of their energy storage assets. At LGES Vertech, you’ll be part of a collaborative, team‑oriented organization that aspires to be humble, hungry, and smart, working together to transform the energy landscape and create a more sustainable future. We value innovation, accountability, and growth. For more information, visit www.lgensol-vt.com.

            Position Overview

            The ESS Residential CS Operations Specialist is a position created by LG Energy Solution’s rapid growth within the North American ESS battery market. Reporting to the Sr. Operation Specialist, this role will be responsible for customer account management and other CS tasks as designated by the Team / Part Leader.

            Primary Responsibilities

            Accounting Operations

            • Serve as the main point of contact for TRR (Truck Roll Reimbursement), Compensation, and Downtime Compensation payment-related matters.
            • Communicate effectively between ASC, 3rd parties, and installers to resolve payment issues.
            • Verify and process invoices in alignment with the RMA policy, ensuring all required documentation and conditions are met.
            • Update and manage invoice data and case statuses in HubSpot CRM.
            • Collaborate with management and external teams to approve payments and resolve pending invoice issues.
            • Maintain master files for TRR, Compensation, and Downtime Compensation to ensure organized record-keeping.
            • Process and verify invoices related to warehouse operations, inventory movements, and retrievals, ensuring compliance with internal policies and supporting documentation.
            • Liaise with logistics partners, warehouse staff, and customers to resolve discrepancies in inventory-related invoicing.

            RMA Management

            • Serve as the dedicated account manager for TRR for B2B customers, provide necessary report to the customer periodically ensuring their needs are met efficiently and building strong professional relationships.
            • Act as the main communication channel for TRR, Compensation, and Downtime Compensation payments, addressing customer concerns, and resolving issues proactively.
            • Understand and oversee the RMA process, including approvals at Tier 3 level in the ECS/ERP system.
            • Conduct detailed reviews of RMA submissions, including verifying battery serial numbers, error codes, and supporting documents.
            • Coordinate with technical teams, CIC (Customer Interaction Center), and logistics to ensure proper handling and shipping of replacement units.
            • Provide updates and support to the CIC team as needed.

            Warehouse and Inventory Operations

            • Monitor and manage inventory levels at third-party (3PL) warehouses, ensuring accuracy between WMS (Warehouse Management System) records and physical stock.
            • Coordinate with 3PL warehouse partners to resolve discrepancies between system data and on-site inventory.
            • Oversee the retrieval of unreturned batteries from customers, installers, and third-party sites, ensuring timely return and proper record-keeping.
            • Arrange and track the shipment of new RMA replacement units to grid sites, and the return of defective (failed) units from customer sites to the warehouse.

            Other Duties

            • Manage recall data for labor reimbursements.
            • Process and track FedEx invoices and maintain related master files for reporting.
            • Provide support for B2B account-related reports and activities, leveraging prior account-specific knowledge.

            Key Knowledge, Skills and Abilities

            • High degree of tact and professionalism in interpersonal communications and teamwork with internal and/or external customers.
            • Clearly and concisely communicate to customers both in-person and remotely via phone, email, etc.
            • Excellent customer service and follow-through skills.
            • High level of work ethic, productivity, efficiency, and attendance.
            • Adhere to all Company policies/procedures, safety regulations, local/state/federal employment laws.
            • High level of organization and attention to detail.
            • Ability to work with colleagues from several different nationalities and native languages.
            • Multi-task in a fast-paced, deadline driven and constantly changing environment.
            • Prioritize