FAS Divisional Technology Partner: Science Division

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to parse the job posting. We have company description, job description, responsibilities, qualifications, additional info, benefits, etc. We need to decide which sections to include. - About the role: Could be derived from job description summary: "The FAS Divisional Technology Partner: Science Division will partner with divisional leadership to align technology investments with priorities, leads demand planning and prioritization within governance frameworks, and represents divisional needs in enterprise decision-making while coordinating solutions, managing escalations, and supporting effective issue resolution." That's a description of the role. So we can include About the role section with that paragraph. - Responsibilities: The "Job-Specific Responsibilities: Duties and Responsibilities:" list many bullet-like sentences. We need to put them in

• . So Responsibilities section with list items. - Requirements: The posting has "Basic Qualifications" and "Additional Qualifications and Skills". Could combine into Requirements? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. Possibly we can have Requirements for basic qualifications, Qualifications for additional qualifications, Skills for skills? But we need to avoid thin sections. Better to combine into maybe Requirements and Qualifications? However we must follow instruction: Use those headings only when there is real specific content. We can include Requirements (basic qualifications) and Qualifications (additional qualifications and skills). Skills maybe not needed separately if covered. But we could also put skills under Qualifications. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But we have headings list; we can choose to include only those we have content for. Could do: About the role, Responsibilities, Requirements (basic qualifications), Qualifications (additional qualifications and skills), Benefits. Pay: we have salary grade level 058 and reference to Harvard's Salary Ranges but not actual numbers. That's not specific; we should not create Pay section unless posting actually states them. It says "Please visit Harvard's Salary Ranges to view the corresponding salary range and related information." That's not a specific figure, so we should not include Pay section. Schedule: we have hybrid 3-4 days in person, work schedule and location set by department, etc. That's schedule info. So we can include Schedule section with that detail. Benefits: we have benefits list. So include Benefits. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. We need to ensure we don't repeat job title as heading. Not include Job ID etc. We need to strip boilerplate: EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions (cover letter and resume as one document). Also remove pre-employment screening, visa sponsorship info? Visa sponsorship info is maybe relevant but it's not a heading; we could fold into a short p under Additional Information? But we are not including Additional Information heading. We could include that info in a paragraph under maybe Requirements? But better to keep only substantive sections; we could include a short paragraph under Additional Information? Not a heading. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a short p for things like visa sponsorship, work format details, etc. But we need to decide where to place them. Perhaps after Qualifications we can add a

  with that metadata. However we must not create extra headings. So we can just add a

  after Qualifications (or before Benefits) containing that info. But we must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all substantive info from the posting, but we can omit boilerplate. We need to ensure we don't lose any substantive info like: "Working Conditions: Onsite work is performed in an office setting. Hybrid 3-4 days in personVisa Sponsorship Information: Harvard University is unable to provide visa sponsorship for this position. Pre-Employment Screening: IdentityOther Information: Please provide a cover letter and resume as one document with your application. This position has an 180-day orientation and review period." Also "Harvard University's Central Administration (CADM) is a 5,000+ employee organization..." That's more about CADM, maybe not directly relevant to the role but it's substantive? It's describing the organization; could be considered part of company description but we already have company description. Might be redundant but still substantive. However we might drop it as it's not directly about the role? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should keep all substantive info from the posting, not just about the role. But we also need to remove boilerplate like EEO, legal, scam-warning, duplicated lines. The CADM paragraph is not boilerplate; it's substantive about the organization. Should we keep it? It appears under "Additional Information". It might be considered part of company description. We could incorporate it into About the role or a separate paragraph. Since we already have About the role from job description, we could add a paragraph about the organization (CADM) maybe under About the role or as a separate

  . But we don't have a heading for "Company Description". We could fold it into About the role or a preceding

  before sections. The instruction says we can fold minor metadata into a short

  or drop it. The CADM paragraph is not minor metadata; it's substantive about the organization. Might be okay to include as a

  before sections. Similarly, the IT Academy description is substantive about benefits/training. Could be included under Benefits or as a separate paragraph. We need to decide what to keep. Let's extract all substantive content blocks: - Company Description (first paragraph): "By working at Harvard University, you join a vibrant community that advances Harvard's world-changing mission in meaningful ways, inspires innovation and collaboration, and builds skills and expertise. We are dedicated to creating a diverse and welcoming environment where everyone can thrive." - Why join the Harvard Faculty of Arts and Sciences / Harvard University Information Technology (HUIT)? Then description of FAS and HUIT. That's also substantive. - Job Description: The FAS Divisional Technology Partner: Science Division will partner with divisional leadership to align technology investments with priorities, leads demand planning and prioritization within governance frameworks, and represents divisional needs in enterprise decision-making while coordinating solutions, managing escalations, and supporting effective issue resolution. - Job-Specific Responsibilities: Duties and Responsibilities: list of duties (many sentences). We'll turn into list. - Qualifications: Basic Qualifications: Bachelor's degree or equivalent work experience required. Minimum of five years’ post-secondary education or relevant work experience - Additional Qualifications and Skills: list: Ability to navigate stakeholders at all levels of the organization. Strategic initiative and portfolio management. Executive communication and stakeholder engagement. Stakeholder negotiation and influence. Experience working in the FAS, Harvard, or a complex higher education settingFinancial stewardship and resource allocation. Facility with technological tools, platforms, and concepts. Organizational change leadership. - Additional Information: Working Conditions: Onsite work is performed in an office setting. Hybrid 3-4 days in person Visa Sponsorship Information: Harvard University is unable to provide visa sponsorship for this position. Pre-Employment Screening: Identity Other Information: Please provide a cover letter and resume as one document with your application. This position has an 180-day orientation and review period. Harvard University's Central Administration (CADM) is a 5,000+ employee organization that supports the university's overall excellence by understanding and serving the needs of its schools, students, faculty, staff, alumni, and surrounding communities. Through dynamic and collaborative partnerships, CADM provides high-quality and efficient services to the schools to help them achieve their goals. IT Academy (designed for IT Staff): HUIT’s IT Academy aims to enable each IT staff person to grow professionally and become a trusted partner to her or his team. The IT Academy is built on the belief that every IT staff member across the University (including technology employees at each school and campus) can grow in her or his area of expertise as well as building strong people and project management skills. Learn more here: https://itacademy.harvard.edu/. Work Format Details This position has been determined by school or unit leaders that some of the duties and responsibilities can be effectively performed at a non-Harvard location. The work schedule and location will be set by the department at its discretion and based upon operational needs. When not working at a Harvard or Harvard-designated location, employees in hybrid positions must work in a Harvard registered state in compliance with the University’s Policy on Employment Outside of Massachusetts. Additional details will be discussed during the interview process. Certain visa types and funding sources may limit work location. Individuals must meet work location sponsorship requirements prior to employment. Salary Grade and Ranges This position is salary grade level 058. Please visit Harvard's Salary Ranges to view the corresponding salary range and related information. Benefits Harvard offers a comprehensive benefits package that is designed to support a healthy work-life balance and your physical, mental and financial wellbeing. Because here, you are what matters. Our benefits include, but are not limited to: Generous paid time off including parental leave Medical, dental, and vision health insurance coverage starting on day one Retirement plans with university contributions Wellbeing and mental health resources Support for families and caregivers Professional development opportunities including tuition assistance and reimbursement Commuter benefits, discounts and campus perks Learn more about these and additional benefits on our Benefits & Wellbeing Page. We need to remove EEO/Non-Discrimination Commitment Statement (boilerplate). Also remove duplicated lines (maybe none). Also remove application instructions? The instruction says remove application instructions. That includes "Please provide a cover letter and resume as one document with your application." That's an application instruction, so we should remove it. Also "Learn more here: https://itacademy.harvard.edu." maybe not application instruction but it's a link; could be considered reference; but it's not boilerplate. Might keep. We also need to remove "Pre-Employment Screening: Identity" maybe that's boilerplate? It's minor metadata; could fold into short p or drop. Probably drop as it's not substantive. We need to keep "This position has an 180-day orientation and review period." That's substantive. We need to keep "Harvard University's Central Administration (CADM) is a 5,000+ employee organization..." That's substantive. We need to keep IT Academy description. We need to keep Work Format Details. We need to keep Salary Grade and Ranges (but we cannot create Pay section unless specific numbers; we can include that info in a short p maybe under a heading? Not Pay. Could fold into a

  under maybe Benefits? But it's about salary. Could create a short p after Benefits? But we shouldn't create Pay heading. So we can include a

  with that info. We need to keep Benefits list. Now we need to output HTML fragment with sections. We'll structure:

  Company Description paragraph(s).

  Maybe combine the "Why join..." into same

  or separate. We'll have:

  About the role

  The FAS Divisional Technology Partner: Science Division will partner with divisional leadership to align technology investments with priorities, leads demand planning and prioritization within governance frameworks, and represents divisional needs in enterprise decision-making while coordinating solutions, managing escalations, and supporting effective issue resolution.

  Responsibilities

  • Document local FAS technology needs and gather feedback on IT systems and services.
  • Manage IT investment request intake.
  • Partner with FAS divisional leadership to align technology investments with academic and operational priorities, ensuring IT initiatives are prioritized and/or funded within defined governance guardrails and