Director, Product Infrastructure & Cloud

We need to output HTML fragment with sections: About the role? Actually the posting includes "ABOUT PER SCHOLAS:" then description of organization, then "DEPARTMENT: Curriculum Solutions", "POSITION TITLE: Director, Product Owner - Infrastructure Technology", "REPORTS TO: Sr. Director, Product Management", "DURATION: Full Time MODALITY: Remote, must be in compliance with Per Scholas office policyTravel: 25%". Then "WHO WE ARE LOOKING FOR:" etc. Then "WHAT YOU'LL DO:" with bullet points (actually paragraphs). Then "WHAT YOU'LL BRING TO US:" with Professional Qualifications etc. Then "Remote Compensation" and "Benefits & Perks". Need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if content exists. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none. Also remove duplicated lines. We need to decide which sections to include. We have: - About the role: Could be the "WHO WE ARE LOOKING FOR:" description? Actually that is more about role description. Could treat as About the role. - Responsibilities: "WHAT YOU'LL DO:" section. - Requirements: "WHAT YOU'LL BRING TO US:" includes Professional Qualifications etc. Could be Requirements. - Qualifications: maybe separate? Could combine. - Skills: maybe not explicit. - Benefits: "Benefits & Perks" section. - Pay: "Remote Compensation" section. - Schedule: maybe from "DURATION: Full Time MODALITY: Remote, must be in compliance with Per Scholas office policyTravel: 25%". That gives schedule: Full Time, Remote, Travel 25%. So we can include Schedule heading. We need to ensure we don't include headings with filler like "commensurate with experience". Not present. We need to use

• for any list of duties/requirements/benefits. The sections have paragraphs with sentences; we can convert bullet-like sentences? The text uses colon and sentences but not explicit bullet list. However we can treat each sentence as list item? The instruction: Use
  • for any list of duties/requirements/benefits. The posting does not have explicit bullet list markers, but we can infer that each duty is a sentence separated by line breaks? In the text, after "WHAT YOU'LL DO:" there are paragraphs each starting with bold headings like "Roadmap Ownership & Strategic Alignment:" then description. That's like subheadings. We could treat each bold heading as a list item? Might be better to keep as

    for prose and only use

    • if there is an explicit list. Since there is no explicit bullet list, we can keep as

      . However the instruction says "Use

      • for any list of duties/requirements/benefits". If we don't have a list, we don't need to use
        . So we can keep paragraphs. But we could also convert each duty paragraph into
        • under a
          . That might be safer: treat each duty as a list item. However we risk altering meaning? Probably acceptable. Similarly for requirements: "Professional Qualifications" includes multiple bullet-like sentences separated by periods. Could make list. Benefits: list of items. We'll produce sections:

          About the role

          with paragraph describing role (from WHO WE ARE LOOKING FOR: maybe also include ABOUT PER SCHOLAS? That's about organization, not role. The instruction: About the role heading for section about role. We'll put the description from "WHO WE ARE LOOKING FOR:" plus maybe the earlier sentences about role? We'll include that paragraph.

          Responsibilities

          with
          • each duty.

            Requirements

            with
            • each requirement (Professional Qualifications bullet points). Also maybe include "Preferred Qualifications"? Could be separate but we can combine.

              Benefits

              with
              • each benefit.

                Pay

                with paragraph about salary.

                Schedule

                with paragraph about Full Time, Remote, Travel 25%. We must not include headings with empty content. Now extract content. Let's copy relevant sections. ABOUT PER SCHOLAS: description of organization. Might be considered "About the role"? Actually it's about the organization. Could be part of About the role? But we already have About the role for role description. The organization description could be considered part of About the role? Might be okay to include in About the role as context. But we must not invent. We'll include it as part of About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put organization info there? Might be okay. But we also have WHO WE ARE LOOKING FOR: which is more role-specific. We'll combine both. Let's extract WHO WE ARE LOOKING FOR: paragraph after that heading up to "WHAT YOU'LL DO:". Text: "Per Scholas is seeking a dynamic, strategic, and results-oriented Product Owner to lead our Infrastructure Technology curriculum portfolio. In this role, you will serve as the vertical subject-matter expert (SME) and curriculum product owner-translating labor market intelligence, employer demand, technical standards, and instructional research into high-quality, scalable learning products that drive learner outcomes, credential attainment, and job placement. You will own discovery, define the learner's experience intent, translate infrastructure technology requirements into clear learning objectives and measurable assessments, and partner cross-functionally through build, launch, and continuous improvement.You bring an infrastructure technology background with fluency across data center operations, low voltage systems, critical facilities, facilities controls, and building automation. You understand electrical and HVAC-adjacent environments, are familiar with Data Center Infrastructure Management (DCIM) platforms and Critical Monitoring Systems (CMS), and can translate real-world occupational requirements into clear learning objectives, competency maps, hands-on labs, safety-aligned scenarios, and measurable performance assessments." We'll put that as About the role. Now Responsibilities: after "WHAT YOU'LL DO:" we have several sections: Roadmap Ownership & Strategic Alignment: paragraph. Curriculum Discovery, Requirements Translation, and Design Leadership: paragraph. Stakeholder Advisory & External Enablement: paragraph. Product Owner Enablement & Cross-Functional Leadership: paragraph. Operational Excellence, Measurement, and Governance: paragraph. Systems, Process, and Cross-Functional Integration: paragraph. We'll make each a
              • . Now Requirements: after "WHAT YOU'LL BRING TO US:" we have Professional Qualifications bullet points (actually sentences separated by periods). Then "Preferred Qualifications" then "Personal Characteristics". We'll treat Professional Qualifications as Requirements. Could also include Preferred Qualifications as part of Requirements? We'll include both as list items under Requirements. Professional Qualifications list: - 6+ years of hands-on infrastructure technology experience in data center operations, low voltage systems, critical facilities, facilities technology, building automation, facilities controls, or closely related technical environments. - 3+ years of experience working with or supporting data centers, critical facilities, facilities operations, electrical-adjacent, HVAC-adjacent, or building systems environments. - 2+ years of product ownership, curriculum development, technical training, program design, technical enablement, or workforce development experience. - Active Technical Portfolio: Must be prepared to discuss real-world infrastructure projects, diagrams, facilities workflows, monitoring scenarios, lab designs, implementation plans, or technical documentation during the interview process. - Proven ability to translate technical and occupational requirements into structured learning objectives, competency-based outcomes, hands-on labs, and assessable performance measures. - Product Design discipline: experience managing a backlog, writing clear requirements, aligning stakeholders, documenting decisions, and driving execution from discovery through launch. - Executive communication strength: ability to synthesize infrastructure technology complexity into clear tradeoffs, decisions, risks, and measurable outcomes. Preferred Qualifications: - Experience developing or evaluating technical training content, labs, simulations, job aids, and performance-based assessments for infrastructure technology occupations. - Familiarity with workforce development or scaled training delivery environments (multi-site, standardized delivery, instructor enablement). - Experience with OSHA, EPA, NFPA-related safety practices, DCIM platforms, Critical Monitoring Systems, low voltage training, data center operations, facilities controls, or building automation. Personal Characteristics: maybe not required but could be included under Requirements? It's more about traits. Could be included as Requirements as well. We'll include them as list items. Personal Characteristics: - Outcomes-oriented: prioritizes learner job readiness, employer relevance, safety, and occupational competency over activity or output volume. - High standards with psychological safety: balances rigor, clarity, accountability, and technical precision with supportive collaboration. - Systems thinker: improves repeatability, documentation, governance, and process discipline across cross-functional teams. - Strong collaborator: builds alignment across Product, Design, Delivery, and Operations; leads through influence and crisp decision-making. Now Benefits: after "Benefits & Perks" we have paragraphs: - Holidays & PTO: Full-Time Per Scholas team members enjoy over 40 days of paid time off each year through a mix of holidays, vacation, and sick/personal time! All employees are eligible for Holiday pay upon hire (a total of 22 holidays annually, including a week off for Independence day and a week before the New Year). Full-Time Benefits Eligible employees also receive 80 Wellness Hours to use for Sick, Safe, or Personal reasons and accrue Vacation at a rate of 8 hours at the beginning of every month, supporting rest, recharge, and work-life balance. Vacation accruals increase with tenure. Part-time employees are afforded time off on a prorated basis and in accordance with local requirements. - Comprehensive Medical Coverage: Benefit eligible employees can choose from multiple medical plans through Cigna or Kaiser Permanente (where available), with options to fit your needs. Eligible employees also have access to a Health Reimbursement Account (HRA) that reimburses eligible out-of-pocket expenses, up to $4,000 for individuals and $8,000 for families. - Dental and Vision Insurance: Eligible employees can select from two dental plan options and a vision plan. Employees who waive medical coverage receive employer paid dental and vision premiums. - Retirement Savings: 401(k) plan with a current 100% employer match on contributions up to 6%, eligible employees are offered entry and full vesting after 90 days with the company. - Employee Assistance Program (EAP): Free, confidential (cut off). We'll include as is. We'll make each bullet as
              • . Pay: after "Remote Compensation" we have: "For this role specifically, we are targeting a salary of $100,000, with a range of $95,000 to $100,000. The salary difference is typically determined by several factors, including the candidate's geographic location and alignment with qualifications and experience." We'll put that as paragraph under Pay. Schedule: from "DURATION: Full Time MODALITY: Remote, must be in compliance with Per Scholas office policyTravel: 25%". We'll parse: Full Time, Remote, must be in compliance with Per Scholas office policy, Travel: 25%. We'll make paragraph. Now we need to output only HTML fragment, no markdown. Let's craft. We'll start with

                About the role

                ...

                Then

                Responsibilities

                • ...
                ...
                Then

                Requirements

                • ...
                ...
                Then

                Benefits