HUMAN RESOURCES SPECIALIST I #00025372

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 as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes "Anticipated Hiring Range ... $17.40-$20.00 hourly." That's pay info, so we can include Pay section. Benefits: there is a "Benefit Eligibility" paragraph describing benefits, so we can include Benefits section. Schedule: not mentioned, so omit. About the role: we have a description: "Provides administrative support for human resources operations and recruitment by processing transactions, coordinating activities, and maintaining accurate records. Works closely with HR staff and Human Resource Business Partners (HRBPs) to ensure processes are completed efficiently and in alignment with established procedures. Serves as the first point of contact for phone and office visits." That's about the role. Could also include "Hiring Department Human Resources ..." but that's more about department; we could incorporate into About the role or maybe a separate "About the department". But only allowed headings list; we can use About the role. Responsibilities: list of key responsibilities bullet points. Requirements: Minimum Qualifications and Preferred Qualifications maybe combined? Could separate Requirements (minimum) and Qualifications (preferred) but we have both headings allowed: Requirements, Qualifications. We'll put Minimum Qualifications under Requirements, Preferred Qualifications under Qualifications. Skills: maybe we can extract from preferred qualifications: strong written and oral communication skills, proficiency in multiple computer applications including databases, spreadsheets, word processing. That's skills. Could also include other skills from responsibilities? But we can put under Skills. We need to preserve all substantive info; not invent or summarize away detail. Must not omit details like "Process personnel actions and maintain HR records", etc. Must keep them as list items. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Application Deadline Applications will be accepted until this position is filled." That's application instruction; remove. Also remove "Sponsorship Information Visa Sponsorship Information Applicants must be authorized to work in the United States. The University will not sponsor applicants for this position for employment visas." That's sponsorship info; maybe considered boilerplate? It's not EEO but it's about visa sponsorship; not sure if we should keep. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Sponsorship info is not explicitly listed, but it's similar to legal? Might be considered boilerplate; but it's substantive info about visa sponsorship. However, the instruction says to remove EEO/equal-opportunity/scam-warning boilerplate. Sponsorship info is not exactly those. Might keep? But it's about visa sponsorship; could be considered relevant. However, the instruction says "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Sponsorship info is not exactly those categories, but could be considered legal. Safer to remove? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Visa sponsorship info is substantive. But it's also a condition of employment. I'd keep it maybe under a section like "Work Authorization". But we don't have a heading for that; we could fold into a paragraph under About the role or Requirements? Not ideal. However, we could create a short

for minor metadata. The instruction says: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Visa sponsorship could be considered minor metadata? Might be okay to fold into a short

. But we have no place for misc metadata; maybe we can add a

after the sections. But the instruction says output ONLY the HTML fragment; we can include a

for minor metadata not fitting headings. We also have "Grade: GGS 7 University Title: HUMAN RESOURCES SPEICALIST I". That's minor metadata; we can fold into a short

. Also "To review the University of Missouri’s Staff Compensation Structure you can view the Job Code detail page. Internal applicants can determine their university title by accessing the Talent Profile tile in myHR." That's application instruction/boilerplate; remove. Also "Community Information University Information ..." that's a lot of descriptive text about the university and location. Is that substantive? It's about the institution and location; could be considered relevant but maybe not required. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That is substantive info about the university and location. However, it's quite lengthy and maybe considered boilerplate? It's not navigation/legal/EEO. It's describing the university and location; could be considered relevant to job posting. But the instruction says prefer a few substantive sections over many thin ones. We could include an "About the department" or "About the university" section? Not in allowed headings list. Allowed headings are only those specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add extra headings. We could fold that info into a

under About the role? But About the role is supposed to be about the role, not the university. However, we could include a short paragraph about the university as part of About the role? Might be stretching. But we could also drop it if considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The community information is not those; it's descriptive. So we should keep it. But we lack a heading for it; we could incorporate into a

after the sections as minor metadata? It's not minor; it's fairly long. However, we could treat it as part of "About the role" maybe as a description of the work environment? Might be okay. Given the constraints, I'll produce sections: About the role (including the description and maybe university/community info as a paragraph), Responsibilities (ul), Requirements (ul for minimum qualifications), Qualifications (ul for preferred qualifications), Skills (ul for skills), Benefits (ul for benefits), Pay (p with salary range). Omit Schedule. We must not repeat job title as heading. Good. Now extract details: About the role: The job description paragraph: "Provides administrative support for human resources operations and recruitment by processing transactions, coordinating activities, and maintaining accurate records. Works closely with HR staff and Human Resource Business Partners (HRBPs) to ensure processes are completed efficiently and in alignment with established procedures. Serves as the first point of contact for phone and office visits." Also the hiring department description: "The Human Resources Department provides support in areas such as benefits, recruitment, employee relations, and training. The department administers HR processes and services that contribute to campus operations. Positions in HR focus on service delivery, employment processes, and policy related guidance." Could be considered about the department; we could include as part of About the role? Might be okay. Also university/community info: large block. Might be too much; but we can include as a paragraph after About the role? Might be considered minor metadata? I'd rather include it as a

after About the role but before Responsibilities? Not sure. Given the instruction to prefer few substantive sections over many thin ones, maybe we should keep only the core sections and drop the lengthy community info as it's not directly about the role. However, the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we drop it, we are summarizing away detail (removing). That would violate. So we must keep it somewhere. We could include it as a

under About the role? But About the role heading is for role description; adding unrelated info might be odd but still preserves info. Alternatively, we could add a

after the sections as a "Additional Information" but we don't have heading for that; we could just put a

without heading, which is allowed? The instruction says output ONLY the HTML fragment; we can include

elements anywhere. It didn't say we must wrap everything under headings. So we can have a

for the community info after the sections. Thus structure:

About the role

Provides administrative support for human resources operations and recruitment by processing transactions, coordinating activities, and maintaining accurate records. Works closely with HR staff and Human Resource Business Partners (HRBPs) to ensure processes are completed efficiently and in alignment with established procedures. Serves as the first point of contact for phone and office visits.

The Human Resources Department provides support in areas such as benefits, recruitment, employee relations, and training. The department administers HR processes and services that contribute to campus operations. Positions in HR focus on service delivery, employment processes, and policy related guidance.

Grade: GGS 7 | University Title: HUMAN RESOURCES SPECIALIST I

Then Responsibilities:

Responsibilities

• Process personnel actions and maintain HR records
• Manage walk-in and phone traffic providing high level customer service
• Assist with onboarding processes, including document verification
• Run standard reports and track items requiring follow-up
• Coordinate HR processes such as unpaid appointments and data requests
• Support basic HR transactions
• Support recruitment activities, including posting jobs, routing applicants, and assisting with background checks and reference checks
• Perform other duties as assigned

Requirements (minimum qualifications):

Requirements

• High school diploma or equivalent and at least 2 years of experience from which comparable knowledge and skills can be acquired

Qualifications (preferred):

Qualifications

• Strong written and oral communication skills
• Proficiency in multiple computer applications, including databases, spreadsheets, and word processing

Skills: maybe we can combine with Qualifications? But we already have Qualifications for preferred qualifications. Skills could be separate but might duplicate. However, we could treat the preferred qualifications as Skills. But we already used Qualifications heading for preferred qualifications. The instruction allows Skills heading; we could put the same items under Skills. But that would duplicate info. Better to keep Qualifications for preferred qualifications and maybe Skills for something else? There's no other explicit skills list. Could omit Skills section if no distinct content beyond what's already covered. The instruction: Prefer a few substantive sections over many thin ones. So we could omit Skills if it would be thin. However, we have the preferred qualifications which are skills; we could put them under Skills and not have Qualifications. But we also have Minimum Qualifications (requirements). So we could have Requirements (minimum) and Skills (preferred). That would be two sections. That seems reasonable: Requirements = minimum qualifications; Skills = preferred qualifications (skills). Then we don't need a Qualifications heading. Let's do that. Thus:

Requirements

• High school diploma or equivalent and at least 2 years of experience from which comparable knowledge and skills can be acquired

Skills

• Strong written and oral communication skills
• Proficiency in multiple computer applications, including databases, spreadsheets, and word processing

Benefits: we have a paragraph describing benefits. We'll make a

• for each benefit. Benefit Eligibility paragraph: "This position is eligible for University benefits. As part of your total compensation, the University offers a comprehensive benefits package, including medical, dental and vision plans, retirement