Business Systems Analyst - Harvard Integrated Life Sciences

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title heading. No Job ID etc. Remove boilerplate like EEO, navigation, legal, etc. Also remove application instructions, duplicated lines. We need to parse the posting. Company Description: includes description of Harvard University and Harvard Medical School. That could be "About the role"? Actually "About the role" is generic; but we have company description. Could map to "About the role" or maybe "About the team". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections have content. We have: - Job Description: description of role, duties, responsibilities. That maps to Responsibilities (maybe also About the role). The "Job Description" paragraph includes: "Harvard Medical School Information Systems seeks a Business Systems Analyst professional skilled in leading requirements elicitation, journey mapping, business process redesign, and user-centered design. This position will support the Harvard Integrated Life Sciences (HILS) Administration and will design, develop, and implement solutions to streamline HILS operations and data collection processes. The position will collaborate regularly with the HILS Director of Academic Administration and Education Staff to translate business needs into technology strategies and systems requirements. The position will participate in the full software development lifecycle (SDLC) from project inception through ongoing production support, including data analysis, testing, and training. The position will require experience with desktop, mobile, or web-based software applications and relational databases with a service delivery approach. Familiarity with Peoplesoft Campus Solutions and/or Oracle Business Intelligence Enterprise Suite and/or Oracle Analytics will be a plus. The ideal candidate will be energized by solving problems in new and innovative ways. You are comfortable working in an ever-changing environment and have the ability to engage with stakeholders to identify minimal viable product for frequent delivery of new technology solutions." That's responsibilities. Then "Core Duties:" list bullet points. That's also responsibilities/duties. Then "Qualifications" section with Basic Qualifications and Additional Qualifications and Skills. Then "Certificates and Licenses:" line. Then "Additional Information": includes Standard Hours/Schedule: 35 hours per week. Work is primarily carried out remotely with monthly in-office anchor days for local employees. Visa Sponsorship Information: Harvard University is unable to provide visa sponsorship for this position. Pre-Employment Screening: Identity, Criminal... (cut off). Then "Staying Informed About Your Application:" etc. Then "Work Format Details": remote etc. Then "Salary Grade and Ranges": salary grade level 057, refer to Harvard's Salary Ranges. Then "Benefits": list. We need to include sections only if real specific content. We have: - About the role: maybe we can use company description as "About the role". The company description includes Harvard University and Harvard Medical School mission. That's specific content. So we can have

About the role

with paragraphs. - Responsibilities: we have Job Description paragraph and Core Duties list. So we can have

Responsibilities

with

for the prose and

• for duties. - Requirements: maybe we can combine Qualifications and Certificates? The instruction says use headings like Requirements, Qualifications, Skills. We have Qualifications section. Could map to "Qualifications". Also we have "Skills" maybe separate? But we can combine. We need to decide which headings to use: The instruction says use headings for those specific labels. It doesn't forbid using other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those labels. So we need to decide which of those we have content for. We have content for: - About the role (company description) - Responsibilities (job description + core duties) - Qualifications (basic and additional qualifications) - Skills (maybe we can extract skills from qualifications? But we have a separate "Skills" heading; we could put skills there if we have explicit skill list. The qualifications include: "Strong analytical and critical thinking skills", "Strong ability to communicate both verbally and in writing", "Ability to prioritize and multitask", "Troubleshooting skills, problem resolution, project management and technology evaluation". Those are skills. Could put them under Skills. - Benefits (list) - Pay (we have salary grade level 057, but not actual salary range; we have reference to Harvard's Salary Ranges. The instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states "Salary Grade and Ranges This position is salary grade level 057. Please visit Harvard's Salary Ranges to view the corresponding salary range and related information." That is not a specific salary range; it's a reference. Is that considered filler? It's not a specific number, but it's stating the salary grade and that you can view range elsewhere. The instruction says do not create Pay section unless posting actually states them. It does state salary grade level, but not actual range. Might be considered not specific enough? The phrase "Please visit Harvard's Salary Ranges to view the corresponding salary range and related information." is basically a referral. I'd argue it's not a concrete salary figure, but it's still some info. However the instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary grade level, which is a form of pay info. I'd include Pay section with that sentence. - Schedule: we have "Standard Hours/Schedule: 35 hours per week. Work is primarily carried out remotely with monthly in-office anchor days for local employees." That's specific schedule info. So we can include Schedule section. Thus we will have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. We must not include Requirements heading if we don't have distinct content separate from Qualifications/Skills. We could omit Requirements. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, except boilerplate. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we must exclude: - EEO/Non-Discrimination Commitment Statement (the long paragraph) - "Staying Informed About Your Application:" etc. - "Pre-Employment Screening: Identity, Criminal" (maybe incomplete but it's boilerplate) - "Visa Sponsorship Information: Harvard University is unable to provide visa sponsorship for this position." This is not EEO but maybe considered relevant? It's about visa sponsorship. It's substantive? It's a condition. Should we keep? It's not boilerplate; it's specific info about visa. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Visa sponsorship is not exactly those; it's a condition. Might keep? However it's under Additional Information. Could be considered relevant. But we have Schedule section already; we could include visa info under Additional Information? But we don't have a heading for that. We could incorporate into Schedule or maybe a note. But the instruction says only use those headings; we could put visa info in a

  under Schedule or Additional Information? Not sure. The instruction says "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." Visa sponsorship is minor metadata; we could fold into a short

  maybe under Schedule or Additional Information? But we don't have Additional Information heading. Could we add a

  after Schedule? The instruction says output ONLY the HTML fragment; we can include

  elements not under headings? It didn't forbid extra

  outside sections. It said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

    for prose. It didn't say we cannot have stray

    not under a heading. But likely they expect sections with headings and content under them. However we could include a

    for visa info under Schedule or maybe under Additional Information but we don't have that heading. Safer to include visa info as a

    under Schedule? But schedule is about hours/remote; visa is different. Could create a separate heading like "Additional Information" but not in allowed list. The instruction says use those headings as examples, not exclusive? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could create other headings if needed, but they gave examples. Safer to stick to those examples. Visa sponsorship could be considered part of "Schedule"? Not really. Could be part of "Pay"? Not really. Could be part of "Benefits"? Not. Could be part of "About the role"? Not. Maybe we can drop visa sponsorship as minor metadata folded into a short

    (maybe under Schedule or after). The instruction says fold minor metadata into a short

    or drop it. So we can add a

    after the sections for visa sponsorship. That seems acceptable. Similarly, "Pre-Employment Screening: Identity, Criminal" is incomplete but likely boilerplate; we can drop. "Staying Informed About Your Application:" etc is application instructions; drop. "Work Format Details" about remote etc: that's similar to schedule/remote; we could incorporate into Schedule section (maybe add details). The schedule section currently has standard hours/remote. The work format details adds: "This position has been determined by school or unit leaders that the duties and responsibilities can effectively be performed fully remotely at a non-Harvard location. Employees in fully remote positions must work all scheduled hours in a Harvard registered state in compliance with the University’s Policy on Employment Outside of Massachusetts. At the discretion of the department, fully remote employees may occasionally be required on site at a Harvard location. Certain visa types and funding sources may limit work location. Individuals must meet work location sponsorship requirements prior to employment." That's more detail about remote work. Could be folded into Schedule section as additional prose. Thus Schedule section will contain: standard hours/week, remote work details, monthly in-office anchor days, etc. Now Benefits: we have list. Now Pay: we have salary grade level 057 and reference to Harvard's Salary Ranges. We'll include that as prose. Now Qualifications: we have Basic Qualifications: Minimum of two years’ post-secondary education or relevant work experience. Additional Qualifications and Skills: Bachelor's degree preferred. 5+ years' experience in defining requirements for desktop, mobile, or web-based software applications and relational databases preferred. Familiarity with desktop, mobile, or web-based software applications and relational databases with a service delivery approach. Familiarity with Peoplesoft Campus Solutions and/or Oracle Business Intelligence Enterprise Suite and/or Oracle Analytics will be a plus. Demonstrated team performance delivering technology solutions with a service mindset approach. Familiarity with the agile methodology and experienced working with agile frameworks and tools. Strong analytical and critical thinking skills to solve complex issues. Strong ability to communicate both verbally and in writing with internal and external teams. Ability to prioritize and multitask, deadline