Director, Product Infrastructure & Cloud
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content.
We have content: About Per Scholas (mission etc). That's like "About the role"? Actually "About Per Scholas" is about organization, not role. Could treat as "About the role"? But we have "WHO WE ARE LOOKING FOR:" which is description of role. Also "WHAT YOU'LL DO:" responsibilities. "WHAT YOU'LL BRING TO US:" qualifications. Also "Remote Compensation" gives Pay. Also "Benefits & Perks" gives Benefits.
We need to strip boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to preserve all substantive info.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not include Job ID etc.
We must not create sections with filler like "commensurate with experience". We have actual pay range: $95,000 to $100,000, targeting $100k. So we can include Pay section.
Benefits: we have details.
Schedule: not given (full time). Could we infer? It says Full Time MODALITY: Remote. Schedule not specified; we should not create Schedule section unless posting actually states them. It does not give schedule details (like hours). So omit Schedule.
We need sections: About the role? Could use "About the role" heading for WHO WE ARE LOOKING FOR? Or maybe "About the role" is generic. But we have "WHO WE ARE LOOKING FOR:" which is description of role. Could map to "About the role". Or we could use "Responsibilities" for WHAT YOU'LL DO. "Requirements" or "Qualifications" for WHAT YOU'LL BRING TO US. "Benefits" for Benefits & Perks. "Pay" for Remote Compensation.
Also maybe include "About Per Scholas" as a separate section? Not in list but could be "About the organization"? Not required. But we could include as a
before sections? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Likely we should stick to those headings. So we need to map content to those headings.
Thus:
About the role
-> content from WHO WE ARE LOOKING FOR: description of role, SME, etc.
Responsibilities
-> WHAT YOU'LL DO: list of duties.
Qualifications
-> WHAT YOU'LL BRING TO US: Professional Qualifications, Preferred Qualifications, Personal Characteristics.
Maybe also Skills? Could separate but we can put under Qualifications.
We need to use - for any list of duties/requirements/benefits. So for responsibilities we should list each bullet as
- . The text is long paragraphs with sentences separated by periods. We need to extract list items. The posting uses colon headings and then paragraphs. We can break into list items based on sentences or bullet-like sections. The instruction: Use
- for any list of duties/requirements/benefits. So we need to identify lists. The responsibilities section includes multiple bullet-like items: Roadmap Ownership & Strategic Alignment, Curriculum Discovery..., Stakeholder Advisory..., Product Owner Enablement..., Operational Excellence..., Systems, Process... Each is a heading with description. We can treat each as a list item with heading maybe inside
- . That's okay.
Similarly qualifications: Professional Qualifications (list of items), Preferred Qualifications (list), Personal Characteristics (list). We'll make
- .
Benefits: list of items: Holidays & PTO, Comprehensive Medical Coverage, Dental and Vision Insurance, Retirement Savings, Employee Assistance Program. We'll list.
Pay: we can just put
with salary range.
We must not repeat job title as heading.
We must not include minor metadata like Job ID etc.
We must preserve all substantive information: need to include details like remote, travel 25%, reports to Sr. Director, Product Management, duration full time, modality remote, must be in compliance with Per Scholas office policy. That info could go under About the role maybe? Or we could add a short
after About the role? But we cannot create extra headings not in list unless we embed in
. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should only use those headings. Additional info can be placed in paragraphs under those sections.
Thus About the role paragraph can include: Per Scholas is seeking a dynamic, strategic, and results-oriented Product Owner to lead our Infrastructure Technology curriculum portfolio. Reports to Sr. Director, Product Management. Full Time, Remote, must be in compliance with Per Scholas office policy, Travel: 25%.
Now we need to ensure we don't include boilerplate like "Learn more by visiting PerScholas.org and follow us on LinkedIn, X, Facebook, Instagram, and YouTube." That's about Per Scholas but maybe considered boilerplate? It's promotional but still substantive? Might be considered navigation/footer. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That line is not exactly those but could be considered promotional. Might be okay to keep? It's not required. Safer to remove it as it's like a call to action. Also the states list: "Per Scholas candidates must reside in one of the following states..." That's substantive eligibility requirement. Should we include? It's about location eligibility. Could be placed under About the role or Qualifications. It's substantive. We'll include as a paragraph under About the role maybe.
Also "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 policy Travel: 25%" We already captured some.
We need to avoid repeating the job title as heading. We'll not.
Now construct HTML.
We'll start with About the role
then
containing the description.
Then
Responsibilities
then with - items.
Then
Qualifications
then with - items (maybe nested? but we can just list each bullet as
- with internal for subheadings).
Then
Benefits
then .
Then Pay
then .
We must not include Schedule.
Let's extract details.
About the role content:
- 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.
- Reports to Sr. Director, Product Management.
- Full Time, Remote, must be in compliance with Per Scholas office policy.
- Travel: 25%.
- Per Scholas candidates must reside in one of the following states, provided the position does not carry a specific office location requirement: AZ, CA, CO, FL, GA, IL, IN, KS, MD, MA, MI, MO, NC, NJ, NY, OH, PA, TX, WA.
We can combine into paragraph(s). Use
for prose; we can have multiple
under the section.
Now Responsibilities items:
From WHAT YOU'LL DO:
- Roadmap Ownership & Strategic Alignment:
* Own and maintain the multi-year curriculum product roadmap for Infrastructure Technology, with clear prioritization criteria, explicit tradeoffs, and documented decisions across market-driven, customized, and alumni offerings.
* Establish and maintain a disciplined Operating Rhythm, including discovery-to-delivery planning, milestone tracking, and monthly portfolio reviews tied to outcomes and capacity.
* Lead end-to-end product lifecycle management, including opportunity intake, discovery, evaluation, build decisions, implementation, adoption, performance improvement, and strategic sunsetting.
* Define and uphold curriculum product standards (quality, consistency, accessibility, safety alignment, assessment rigor, credential alignment) and ensure adoption across the portfolio.
- Curriculum Discovery, Requirements Translation, and Design Leadership:
* Serve as the primary curriculum strategy lead in partner and funder discovery-translating infrastructure technology requirements into learning objectives, assessments, hands-on labs, and curriculum design intent.
* Assume accountability for the analysis and design phase of new and existing curricula by setting clear design requirements, acceptance criteria, and readiness-to-build decisions for infrastructure technology products.
* Ensure curriculum alignment to occupational roles, industry standards, and certification requirements, including CompTIA A+, Server+, CDCP, OSHA, EPA 608, NFPA-related safety practices, and relevant infrastructure technology expectations.
* Establish durable "definition of done" criteria for curriculum releases (learning objectives, assessments, instructional assets, lab requirements, delivery readiness, and measurement plan).
- Stakeholder Advisory & External Enablement:
* Act as a lead consultant for internal and external stakeholders-including donors, executive leadership, government partners, and employer partners-to shape infrastructure technology curriculum strategy and delivery commitments.
* Spearhead the narrative and content development for client/funder-facing curriculum materials (e.g., solution decks, portfolio overviews, proposals), ensuring accuracy, clarity, and alignment to outcomes, while partnering with Product Operations for packaging, version control, and distribution.
* Support grant and contract requirements by translating compliance, credential, safety, reporting, and employer-alignment needs into product requirements, measurement plans, and deliverable timelines.
- Product Owner Enablement & Cross-Functional Leadership:
* Lead through influence across Product, Design, Delivery, Instructor Development, Evaluation, and Operations to ensure high-quality instructional output and consistent use of product discovery practices.
* Coach cross-functional partners and subject-matter experts on discovery, scoping, learning experience intent, assessment strategy, and tradeoff decisions-protecting focus on the highest-impact work.
* Serve as the primary intake and prioritization lead for new infrastructure technology product requests, optimizing departmental capacity and protecting the team from scope creep.
- Operational Excellence, Measurement, and Governance:
* Own, define, and actively track curriculum product KPIs, using them to drive roadmap decisions, accountability, and continuous improvement across infrastructure technology offerings.
* Partner with Product Operations to maintain curriculum documentation standards, decision logs, and a reliable system of record for portfolio artifacts (course catalog, product briefs
- for any list of duties/requirements/benefits. Use
for prose. We must not include Job ID etc. We must not create sections with filler like "commensurate with experience". We have actual pay range: $95,000 to $100,000, targeting $100k. So we can include Pay section. Benefits: we have details. Schedule: not given (full time). Could we infer? It says Full Time MODALITY: Remote. Schedule not specified; we should not create Schedule section unless posting actually states them. It does not give schedule details (like hours). So omit Schedule. We need sections: About the role? Could use "About the role" heading for WHO WE ARE LOOKING FOR? Or maybe "About the role" is generic. But we have "WHO WE ARE LOOKING FOR:" which is description of role. Could map to "About the role". Or we could use "Responsibilities" for WHAT YOU'LL DO. "Requirements" or "Qualifications" for WHAT YOU'LL BRING TO US. "Benefits" for Benefits & Perks. "Pay" for Remote Compensation. Also maybe include "About Per Scholas" as a separate section? Not in list but could be "About the organization"? Not required. But we could include as a
before sections? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Likely we should stick to those headings. So we need to map content to those headings. Thus:
About the role
-> content from WHO WE ARE LOOKING FOR: description of role, SME, etc.Responsibilities
-> WHAT YOU'LL DO: list of duties.Qualifications
-> WHAT YOU'LL BRING TO US: Professional Qualifications, Preferred Qualifications, Personal Characteristics. Maybe also Skills? Could separate but we can put under Qualifications. We need to use- for any list of duties/requirements/benefits. So for responsibilities we should list each bullet as
- . The text is long paragraphs with sentences separated by periods. We need to extract list items. The posting uses colon headings and then paragraphs. We can break into list items based on sentences or bullet-like sections. The instruction: Use
- for any list of duties/requirements/benefits. So we need to identify lists. The responsibilities section includes multiple bullet-like items: Roadmap Ownership & Strategic Alignment, Curriculum Discovery..., Stakeholder Advisory..., Product Owner Enablement..., Operational Excellence..., Systems, Process... Each is a heading with description. We can treat each as a list item with heading maybe inside
- . That's okay. Similarly qualifications: Professional Qualifications (list of items), Preferred Qualifications (list), Personal Characteristics (list). We'll make
- .
Benefits: list of items: Holidays & PTO, Comprehensive Medical Coverage, Dental and Vision Insurance, Retirement Savings, Employee Assistance Program. We'll list.
Pay: we can just put
with salary range. We must not repeat job title as heading. We must not include minor metadata like Job ID etc. We must preserve all substantive information: need to include details like remote, travel 25%, reports to Sr. Director, Product Management, duration full time, modality remote, must be in compliance with Per Scholas office policy. That info could go under About the role maybe? Or we could add a short
after About the role? But we cannot create extra headings not in list unless we embed in
. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should only use those headings. Additional info can be placed in paragraphs under those sections. Thus About the role paragraph can include: Per Scholas is seeking a dynamic, strategic, and results-oriented Product Owner to lead our Infrastructure Technology curriculum portfolio. Reports to Sr. Director, Product Management. Full Time, Remote, must be in compliance with Per Scholas office policy, Travel: 25%. Now we need to ensure we don't include boilerplate like "Learn more by visiting PerScholas.org and follow us on LinkedIn, X, Facebook, Instagram, and YouTube." That's about Per Scholas but maybe considered boilerplate? It's promotional but still substantive? Might be considered navigation/footer. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That line is not exactly those but could be considered promotional. Might be okay to keep? It's not required. Safer to remove it as it's like a call to action. Also the states list: "Per Scholas candidates must reside in one of the following states..." That's substantive eligibility requirement. Should we include? It's about location eligibility. Could be placed under About the role or Qualifications. It's substantive. We'll include as a paragraph under About the role maybe. Also "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 policy Travel: 25%" We already captured some. We need to avoid repeating the job title as heading. We'll not. Now construct HTML. We'll start with
About the role
thencontaining the description. Then
Responsibilities
then- with
- items.
Then
Qualifications
then- with
- items (maybe nested? but we can just list each bullet as
- with internal for subheadings).
Then
Benefits
then- .
Then
Pay
then. We must not include Schedule. Let's extract details. About the role content: - 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. - Reports to Sr. Director, Product Management. - Full Time, Remote, must be in compliance with Per Scholas office policy. - Travel: 25%. - Per Scholas candidates must reside in one of the following states, provided the position does not carry a specific office location requirement: AZ, CA, CO, FL, GA, IL, IN, KS, MD, MA, MI, MO, NC, NJ, NY, OH, PA, TX, WA. We can combine into paragraph(s). Use
for prose; we can have multiple
under the section. Now Responsibilities items: From WHAT YOU'LL DO: - Roadmap Ownership & Strategic Alignment: * Own and maintain the multi-year curriculum product roadmap for Infrastructure Technology, with clear prioritization criteria, explicit tradeoffs, and documented decisions across market-driven, customized, and alumni offerings. * Establish and maintain a disciplined Operating Rhythm, including discovery-to-delivery planning, milestone tracking, and monthly portfolio reviews tied to outcomes and capacity. * Lead end-to-end product lifecycle management, including opportunity intake, discovery, evaluation, build decisions, implementation, adoption, performance improvement, and strategic sunsetting. * Define and uphold curriculum product standards (quality, consistency, accessibility, safety alignment, assessment rigor, credential alignment) and ensure adoption across the portfolio. - Curriculum Discovery, Requirements Translation, and Design Leadership: * Serve as the primary curriculum strategy lead in partner and funder discovery-translating infrastructure technology requirements into learning objectives, assessments, hands-on labs, and curriculum design intent. * Assume accountability for the analysis and design phase of new and existing curricula by setting clear design requirements, acceptance criteria, and readiness-to-build decisions for infrastructure technology products. * Ensure curriculum alignment to occupational roles, industry standards, and certification requirements, including CompTIA A+, Server+, CDCP, OSHA, EPA 608, NFPA-related safety practices, and relevant infrastructure technology expectations. * Establish durable "definition of done" criteria for curriculum releases (learning objectives, assessments, instructional assets, lab requirements, delivery readiness, and measurement plan). - Stakeholder Advisory & External Enablement: * Act as a lead consultant for internal and external stakeholders-including donors, executive leadership, government partners, and employer partners-to shape infrastructure technology curriculum strategy and delivery commitments. * Spearhead the narrative and content development for client/funder-facing curriculum materials (e.g., solution decks, portfolio overviews, proposals), ensuring accuracy, clarity, and alignment to outcomes, while partnering with Product Operations for packaging, version control, and distribution. * Support grant and contract requirements by translating compliance, credential, safety, reporting, and employer-alignment needs into product requirements, measurement plans, and deliverable timelines. - Product Owner Enablement & Cross-Functional Leadership: * Lead through influence across Product, Design, Delivery, Instructor Development, Evaluation, and Operations to ensure high-quality instructional output and consistent use of product discovery practices. * Coach cross-functional partners and subject-matter experts on discovery, scoping, learning experience intent, assessment strategy, and tradeoff decisions-protecting focus on the highest-impact work. * Serve as the primary intake and prioritization lead for new infrastructure technology product requests, optimizing departmental capacity and protecting the team from scope creep. - Operational Excellence, Measurement, and Governance: * Own, define, and actively track curriculum product KPIs, using them to drive roadmap decisions, accountability, and continuous improvement across infrastructure technology offerings. * Partner with Product Operations to maintain curriculum documentation standards, decision logs, and a reliable system of record for portfolio artifacts (course catalog, product briefs
- items.
Then
- . That's okay. Similarly qualifications: Professional Qualifications (list of items), Preferred Qualifications (list), Personal Characteristics (list). We'll make
- for any list of duties/requirements/benefits. So we need to identify lists. The responsibilities section includes multiple bullet-like items: Roadmap Ownership & Strategic Alignment, Curriculum Discovery..., Stakeholder Advisory..., Product Owner Enablement..., Operational Excellence..., Systems, Process... Each is a heading with description. We can treat each as a list item with heading maybe inside