Intern - President's Office Operations

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting. Primary Work Location: 50 Washington Street, Westborough. On-site schedule. Normal Work Schedule Up to 20 hours per week M-F Job Summary: The University of Massachusetts President's Office, located in Westborough, MA is offering a part time internship for the Fall 2026 semester at $17.00 an hour. Candidates must be a degree seeking UMass student from the five campus system. The Operations Intern supports day-to-day building operations and administrative functions to ensure a safe, clean, and efficient office environment. This is a hands-on role that assists with facilities maintenance, event support, vendor coordination, and basic procurement tasks. Essential Functions (list): Building Access & Facilities Coordination: support access control and visitor check-ins, coordinate maintenance with property management and third party vendors, and ensure common areas and workspaces are clean, safe, and operational. Event support: set up and break down rooms and furniture for meetings and events; manage meeting‑room requests. Mail Room & Office Supply Operations: lead mailroom and shipping activities and manage inventory and procurement of essential supplies. Assist in developing and implementing operational procedures to improve office workflows. Perform other operational tasks and errands as assigned. Minimum Qualifications (Knowledge, Skills, Abilities, Education, Experience): Current UMass student who is enrolled in an undergraduate or graduate program of study; GPA 3.0 or higher; Ability to work independently and as part of a team; Good communication skills, both written and verbal; Detail-oriented and highly organized; Strong problem-solving abilities and proactive approach to addressing challenges; Must be proficient in Microsoft Office (including Excel, Word, PowerPoint); Able to lift 25 lbs; Must be able to work on-site in Westborough, MA Working Conditions: Typical office setting Additional Details: Any offers of an internship within the President's Office is specifically conditioned upon the potential candidate consenting to and successfully completing a background review. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to produce sections: About the role (maybe job summary), Responsibilities (essential functions), Requirements (minimum qualifications?), Qualifications (maybe same?), Skills (maybe Microsoft Office proficiency?), Benefits (none), Pay (hourly rate $17.00), Schedule (Up to 20 hours per week M-F, on-site). Also location maybe part of About the role. We must not repeat job title as heading. Not needed. We must not put Job ID etc. We must include sections only when posting has real specific content. So we have content for About the role (job summary), Responsibilities (essential functions), Requirements (minimum qualifications), Skills (Microsoft Office proficiency maybe part of qualifications but we can separate), Pay ($17.00 an hour), Schedule (Up to 20 hours per week M-F, on-site). Benefits: none specific, so omit. Qualifications: maybe we can combine with Requirements? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include both Requirements and Qualifications if distinct. But we have Minimum Qualifications (Knowledge, Skills, Abilities, Education, Experience). That could be Requirements. Qualifications maybe same? Could treat Requirements as the list of qualifications. But we need to avoid duplication. Perhaps we can put Requirements as the list (student status, GPA, etc.) and Qualifications as maybe "Ability to lift 25 lbs, proficient in Microsoft Office". But that seems arbitrary. Better to follow typical pattern: Requirements = mandatory qualifications; Skills = specific skills (Microsoft Office). Qualifications maybe education/experience? But we have both education (student) and experience (none). Might be okay to have Requirements and Qualifications both with content. Let's decide: - About the role: job summary paragraph. - Responsibilities: essential functions list (ul). - Requirements: minimum qualifications list (student status, GPA, teamwork, communication, detail-oriented, problem-solving, ability to lift 25 lbs, on-site). Could also include ability to work independently/team. - Qualifications: maybe "Current UMass student enrolled in undergraduate or graduate program" (education) and "GPA 3.0 or higher". But that overlaps. Hmm. Alternatively, we could combine Requirements and Qualifications into one section, but we need to follow instruction: use headings for those sections if we have content. If we don't have distinct content for Qualifications, we should not include it. So we should only include sections where we have real specific content. Let's see if we can separate: - Requirements: "Must be able to work on-site in Westborough, MA", "Able to lift 25 lbs", "Ability to work independently and as part of a team", "Good communication skills, both written and verbal", "Detail-oriented and highly organized", "Strong problem-solving abilities and proactive approach to addressing challenges". These are more like abilities/soft skills. - Qualifications: "Current UMass student who is enrolled in an undergraduate or graduate program of study", "GPA 3.0 or higher", "Must be proficient in Microsoft Office (including Excel, Word, PowerPoint)". Those are more like qualifications. - Skills: maybe "Proficient in Microsoft Office (including Excel, Word, PowerPoint)" could be Skills. But we already used that in Qualifications. Could shift. Better: Requirements = eligibility and core abilities (student status, GPA, ability to lift, on-site). Qualifications = skills like Microsoft Office, communication, teamwork, problem-solving, detail-oriented. Skills = maybe Microsoft Office proficiency. But overlapping. Given the instruction to prefer a few substantive sections over many thin ones, we should avoid splitting too thinly. Perhaps we combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we need to decide which heading to use. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't say we must use all; we can pick those that have content. Thus we can have: - About the role (job summary) - Responsibilities (essential functions) - Requirements (minimum qualifications list) - Pay ($17.00 an hour) - Schedule (Up to 20 hours per week M-F, on-site) We could also add Skills (Microsoft Office proficiency) as a separate section if we want, but that would be thin. Better to include Microsoft Office within Requirements or Qualifications. Since we have Requirements already, we can include Microsoft Office there. Thus we will output:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Pay

$17.00 per hour

Schedule

Up to 20 hours per week, Monday–Friday; on‑site at 50 Washington Street, Westborough, MA.

We need to preserve all substantive information: location, on-site schedule, job summary, essential functions list, minimum qualifications list, working conditions (typical office setting) maybe we can include in About the role or Responsibilities? Could add a sentence about working conditions in About the role. Additional details about background review maybe we can include in About the role or Requirements? It's a condition of offer; could be included in About the role as a note. We must not invent or summarize away detail. So we need to keep all details. Let's extract exact phrasing: Job Summary: "The University of Massachusetts President's Office, located in Westborough, MA is offering a part time internship for the Fall 2026 semester at $17.00 an hour. Candidates must be a degree seeking UMass student from the five campus system. The Operations Intern supports day-to-day building operations and administrative functions to ensure a safe, clean, and efficient office environment. This is a hands-on role that assists with facilities maintenance, event support, vendor coordination, and basic procurement tasks." We can keep that as paragraph. Essential Functions: list items: - Building Access & Facilities Coordination: support access control and visitor check-ins, coordinate maintenance with property management and third party vendors, and ensure common areas and workspaces are clean, safe, and operational. - Event support: set up and break down rooms and furniture for meetings and events; manage meeting‑room requests. - Mail Room & Office Supply Operations: lead mailroom and shipping activities and manage inventory and procurement of essential supplies. - Assist in developing and implementing operational procedures to improve office workflows - Perform other operational tasks and errands as assigned. We need to preserve punctuation. Minimum Qualifications list: - Current UMass student who is enrolled in an undergraduate or graduate program of study - GPA 3.0 or higher - Ability to work independently and as part of a team - Good communication skills, both written and verbal - Detail-oriented and highly organized - Strong problem-solving abilities and proactive approach to addressing challenges - Must be proficient in Microsoft Office (including Excel, Word, PowerPoint) - Able to lift 25 lbs - Must be able to work on-site in Westborough, MA Working Conditions: Typical office setting (maybe we can add as a sentence in About the role or Responsibilities). We'll include a short paragraph after Responsibilities maybe. Additional Details: Any offers of an internship within the President's Office is specifically conditioned upon the potential candidate consenting to and successfully completing a background review. We can include that as a note in About the role or Requirements. Probably after Requirements. We must not include boilerplate like EEO etc. Not present. Now produce HTML. Make sure to use

for each section heading. Use

• for lists. Use

  for prose. We must not include or tags. Let's craft. About the role paragraph: include job summary plus maybe location and schedule? But schedule is separate section. We'll keep location maybe in About the role? The posting includes Primary Work Location: 50 Washington Street, Westborough. On-site schedule. Normal Work Schedule Up to 20 hours per week M-F. We'll put schedule in its own section, but location could be in About the role. Thus About the role paragraph: "The University of Massachusetts President's Office, located in Westborough, MA is offering a part time internship for the Fall 2026 semester at $17.00 an hour. Candidates must be a degree seeking UMass student from the five campus system. The Operations Intern supports day-to-day building operations and administrative functions to ensure a safe, clean, and efficient office environment. This is a hands-on role that assists with facilities maintenance, event support, vendor coordination, and basic procurement tasks. Primary work location: 50 Washington Street, Westborough. On-site schedule." But we might duplicate location later in Schedule section. Could keep location in About the role and schedule in Schedule section. That's fine. Now Responsibilities ul. Requirements ul. Pay:

  $17.00 per hour

  Schedule:

  Up to 20 hours per week, Monday–Friday; on‑site.

  We might also include "Normal Work Schedule Up to 20 hours per week M-F" exactly. Now ensure we preserve all details: background review condition. Add a paragraph after Requirements maybe as part of Additional Details. Could be its own section? Not a standard heading; we could add a

  after Requirements without heading. But instruction says use headings for sections; we can just include a paragraph without heading? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that pattern. However we can include a

  for the background review note