HR Operations Specialist
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. We have: - About EOTSS (company description) -> could be "About the role"? Actually "About the role" is a heading suggestion but we have "About EOTSS" which is about the organization. Could use "About the role" but content is about the organization. Might be okay to use "About EOTSS" as heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict list; we can use other headings if appropriate? Probably we should stick to those examples; but we can also use "About EOTSS" as a heading if it's substantive. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That suggests we should use those headings when applicable. For company overview, maybe "About the role" is not correct. Could we omit that section? The instruction: include a section ONLY when the posting has real, specific content for it. We have content about EOTSS; we could put it under a heading like "About EOTSS". But they didn't list that as example; but they didn't forbid other headings. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." implies those are examples, not exclusive. So we can use other headings like "About EOTSS". Probably fine.
We also have "Role Overview" which could be a heading like "Role Overview". Could also be under "About the role". But we have separate sections: Role Overview, Major Responsibilities, Preferred Qualifications, Minimum Entrance Requirements (with substitutions), Comprehensive Benefits, etc.
We need to decide which sections to output: we should include sections for:
- About EOTSS (company description)
- Role Overview (maybe combine with About the role? but we have both)
- Responsibilities (Major Responsibilities)
- Qualifications (Preferred Qualifications + Minimum Entrance Requirements? Could combine but better separate: Qualifications (Preferred) and Requirements (Minimum). However they said prefer a few substantive sections over many thin ones. So we could combine Preferred Qualifications and Minimum Entrance Requirements into a "Qualifications" section, but we need to preserve all detail. Could list both.
- Benefits: we have "Comprehensive Benefits" but only says "Explore our Employee Benefits and Rewards!" No specific benefits listed. That's placeholder; we should not create a Benefits section unless posting actually states them. It does not list specific benefits, just a link. So we should omit Benefits section.
- Pay: we have Salary: 73,615.88 (presumably per year). That's specific. So we should include a Pay section with that salary.
- Schedule: we have regular work schedule Monday through Friday, 9:00 AM to 5:00 PM ET. Also mention limited ad hoc telework may be available. That's specific. So we can include a Schedule section.
- Also we have location info: primary work location One Ashburton Place, Boston, MA 02108; also expected to work onsite at MITC, 200 Arlington Street, Chelsea, MA 02150 as operationally needed. Could be part of Role Overview or a separate "Location" section but not in examples. Could fold into Role Overview paragraph.
- Also we have "First consideration will be given to those applicants that apply within the first 14 days." That's minor metadata; could be a short p.
- Also we have "Official Title Program Coordinator II", "Primary Location United States-Massachusetts-Boston-1 Ashburton Place", "Job Administrative Services Agency Exec Office of Technology Services and Security", "Schedule Full-time", "Job Posting Sep 21, 2026, 1:40:05 PM", "Bargaining Unit 06-NAGE - Professional Admin.", "Potentially Eligible for a Hybrid Work Schedule Yes". Many of these are metadata; we can fold into short p or drop if not substantive. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." implies those are examples, not exclusive. So we can use other headings like "About EOTSS". Probably fine. We also have "Role Overview" which could be a heading like "Role Overview". Could also be under "About the role". But we have separate sections: Role Overview, Major Responsibilities, Preferred Qualifications, Minimum Entrance Requirements (with substitutions), Comprehensive Benefits, etc. We need to decide which sections to output: we should include sections for: - About EOTSS (company description) - Role Overview (maybe combine with About the role? but we have both) - Responsibilities (Major Responsibilities) - Qualifications (Preferred Qualifications + Minimum Entrance Requirements? Could combine but better separate: Qualifications (Preferred) and Requirements (Minimum). However they said prefer a few substantive sections over many thin ones. So we could combine Preferred Qualifications and Minimum Entrance Requirements into a "Qualifications" section, but we need to preserve all detail. Could list both. - Benefits: we have "Comprehensive Benefits" but only says "Explore our Employee Benefits and Rewards!" No specific benefits listed. That's placeholder; we should not create a Benefits section unless posting actually states them. It does not list specific benefits, just a link. So we should omit Benefits section. - Pay: we have Salary: 73,615.88 (presumably per year). That's specific. So we should include a Pay section with that salary. - Schedule: we have regular work schedule Monday through Friday, 9:00 AM to 5:00 PM ET. Also mention limited ad hoc telework may be available. That's specific. So we can include a Schedule section. - Also we have location info: primary work location One Ashburton Place, Boston, MA 02108; also expected to work onsite at MITC, 200 Arlington Street, Chelsea, MA 02150 as operationally needed. Could be part of Role Overview or a separate "Location" section but not in examples. Could fold into Role Overview paragraph. - Also we have "First consideration will be given to those applicants that apply within the first 14 days." That's minor metadata; could be a short p. - Also we have "Official Title Program Coordinator II", "Primary Location United States-Massachusetts-Boston-1 Ashburton Place", "Job Administrative Services Agency Exec Office of Technology Services and Security", "Schedule Full-time", "Job Posting Sep 21, 2026, 1:40:05 PM", "Bargaining Unit 06-NAGE - Professional Admin.", "Potentially Eligible for a Hybrid Work Schedule Yes". Many of these are metadata; we can fold into short p or drop if not substantive. 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 paragraph with metadata like "Official Title: Program Coordinator II. Primary Location: One Ashburton Place, Boston, MA. Schedule: Full-time. Posted: Sep 21, 2026." etc. We need to remove boilerplate: EEO statements, equal opportunity, etc. Also remove "An Equal Opportunity / Affirmative Action Employer..." etc. Also remove "Research suggests that qualified women..." etc. Also remove "If you have Diversity, Affirmative Action or Equal Employment Opportunity questions..." etc. Also remove "Want the specifics? Explore our Employee Benefits and Rewards!" (that's part of Benefits but we are omitting Benefits section). Also remove "First consideration will be given to those applicants that apply within the first 14 days." maybe keep as minor metadata. We need to preserve all substantive information: company description, role overview, responsibilities, qualifications (preferred and minimum), pay, schedule, location details, maybe work schedule note about telework. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must output only HTML fragment, no /, no markdown.
Let's structure:
About EOTSS
... description ...
Role Overview
... role overview text ...
Responsibilities
- ... each duty ... Actually each duty as
- .
Qualifications
We could split into Preferred Qualifications and Minimum Entrance Requirements as subheadings? But we only allowed for section headings; we could use for subheadings? Not specified. Safer to keep as one Qualifications section with two subparts using
headings? Could use within . But maybe better to have two sections: Preferred Qualifications and Minimum Entrance Requirements, each as
. That would be more sections but still substantive. The instruction: prefer a few substantive sections over many thin ones. Having two qualification sections may be okay if each has substantive content. We'll do:
Preferred Qualifications
... bullet list? Actually it's a list of bullet points. We'll use
- for each.
Minimum Entrance Requirements
... description of requirements and substitutions.
Could also use for the substitution list.
Then:
Pay
Salary: $73,615.88 per year.
Schedule
Regular work schedule: Monday through Friday, 9:00 AM to 5:00 PM ET. Limited ad hoc telework may be available subject to operational needs and manager approval.
We also need to include location info maybe within Role Overview or a separate section. Could add a after Role Overview about locations.
Also include metadata short paragraph maybe after schedule.
Let's extract the substantive content.
About EOTSS paragraph:
"The Executive Office of Technology Services and Security (EOTSS) is the lead enterprise technology organization for the Commonwealth of Massachusetts. Charged with driving the ongoing alignment of business and technology across the Commonwealth’s Executive Branch, EOTSS oversees and manages the enterprise technology, digital infrastructure and services, as well as the Commonwealth Security Operations Center and an enterprise Standard Operating Environment that includes an information security and risk management framework for over 125 state agencies and over 43,000 state employees. We directly serve our constituents by providing digital services and tools that enable taxpayers, drivers, businesses, visitors, families and other citizens to do business with the Commonwealth in a way that makes every interaction with government easier, faster, and more secure. Our Mission: We provide technology leadership across the Commonwealth to enhance the quality of public service and foster positive community outcomes."
We'll keep that.
Role Overview paragraph:
"EOTSS is seeking an HR Operations Specialist to provide day-to-day operational and administrative support to the EOTSS Human Resources team. The position supports key HR functions, including recruitment and hiring, employee onboarding, payroll and personnel transactions, compliance activities, and employee records management. The HR Operations Specialist works closely with HR staff, recruiters, hiring managers, and business partners to coordinate and complete HR processes accurately and on time. The position plays an important role in maintaining accurate HR information, tracking required documentation and approvals, responding to routine HR inquiries, and ensuring processes are completed in accordance with Commonwealth policies, procedures, and applicable requirements. The position’s primary work location is One Ashburton Place, Boston, MA 02108. The employee will also be expected to work onsite at MITC, 200 Arlington Street, Chelsea, MA 02150, as operationally needed. The regular work schedule is Monday through Friday, 9:00 AM to 5:00 PM ET. The specific reporting location may vary based on operational needs and will be determined in coordination with the manager. Limited ad hoc telework may be available in the future, subject to operational needs and manager approval."
We might move schedule details to Schedule section, but we can keep location and note about schedule in Role Overview, but we will also have Schedule section. To avoid duplication, we could keep Role Overview without schedule details, but we need to preserve all info. We could keep location and note about reporting location variation, and mention that schedule details are in Schedule section. But we must not lose the schedule info; we can mention that schedule details are provided in the Schedule section. However the instruction says preserve ALL substantive information; we can keep it in both places? Duplication is okay? They said remove duplicated lines. So we should avoid duplicating the same sentence. So we should not repeat schedule info in Role Overview if we have a Schedule section. So we will edit Role Overview to exclude the schedule sentence, but keep location and reporting location variation.
Thus Role Overview paragraph:
"EOTSS is seeking an HR Operations Specialist to provide day-to-day operational and administrative support to the EOTSS Human Resources team. The position supports key HR functions, including recruitment and hiring, employee onboarding, payroll and personnel transactions, compliance activities, and employee records management. The HR Operations Specialist works closely with HR staff, recruiters, hiring managers, and business partners to coordinate and complete HR processes accurately and on time. The position plays an important role in maintaining accurate HR information, tracking required documentation and approvals, responding to routine HR inquiries, and ensuring processes are completed in accordance with Commonwealth
for prose. We must output only HTML fragment, no /, no markdown. Let's structure:
About EOTSS
... description ...
Role Overview
... role overview text ...
Responsibilities
- ... each duty ... Actually each duty as
- .
Qualifications
We could split into Preferred Qualifications and Minimum Entrance Requirements as subheadings? But we only allowed for section headings; we could use for subheadings? Not specified. Safer to keep as one Qualifications section with two subparts using
headings? Could use within . But maybe better to have two sections: Preferred Qualifications and Minimum Entrance Requirements, each as ... bullet list? Actually it's a list of bullet points. We'll use . That would be more sections but still substantive. The instruction: prefer a few substantive sections over many thin ones. Having two qualification sections may be okay if each has substantive content. We'll do:
Preferred Qualifications
Minimum Entrance Requirements
... description of requirements and substitutions.
Could also use- for the substitution list.
Then:
Pay
Salary: $73,615.88 per year.
Schedule
Regular work schedule: Monday through Friday, 9:00 AM to 5:00 PM ET. Limited ad hoc telework may be available subject to operational needs and manager approval.
We also need to include location info maybe within Role Overview or a separate section. Could add aafter Role Overview about locations. Also include metadata short paragraph maybe after schedule. Let's extract the substantive content. About EOTSS paragraph: "The Executive Office of Technology Services and Security (EOTSS) is the lead enterprise technology organization for the Commonwealth of Massachusetts. Charged with driving the ongoing alignment of business and technology across the Commonwealth’s Executive Branch, EOTSS oversees and manages the enterprise technology, digital infrastructure and services, as well as the Commonwealth Security Operations Center and an enterprise Standard Operating Environment that includes an information security and risk management framework for over 125 state agencies and over 43,000 state employees. We directly serve our constituents by providing digital services and tools that enable taxpayers, drivers, businesses, visitors, families and other citizens to do business with the Commonwealth in a way that makes every interaction with government easier, faster, and more secure. Our Mission: We provide technology leadership across the Commonwealth to enhance the quality of public service and foster positive community outcomes." We'll keep that. Role Overview paragraph: "EOTSS is seeking an HR Operations Specialist to provide day-to-day operational and administrative support to the EOTSS Human Resources team. The position supports key HR functions, including recruitment and hiring, employee onboarding, payroll and personnel transactions, compliance activities, and employee records management. The HR Operations Specialist works closely with HR staff, recruiters, hiring managers, and business partners to coordinate and complete HR processes accurately and on time. The position plays an important role in maintaining accurate HR information, tracking required documentation and approvals, responding to routine HR inquiries, and ensuring processes are completed in accordance with Commonwealth policies, procedures, and applicable requirements. The position’s primary work location is One Ashburton Place, Boston, MA 02108. The employee will also be expected to work onsite at MITC, 200 Arlington Street, Chelsea, MA 02150, as operationally needed. The regular work schedule is Monday through Friday, 9:00 AM to 5:00 PM ET. The specific reporting location may vary based on operational needs and will be determined in coordination with the manager. Limited ad hoc telework may be available in the future, subject to operational needs and manager approval." We might move schedule details to Schedule section, but we can keep location and note about schedule in Role Overview, but we will also have Schedule section. To avoid duplication, we could keep Role Overview without schedule details, but we need to preserve all info. We could keep location and note about reporting location variation, and mention that schedule details are in Schedule section. But we must not lose the schedule info; we can mention that schedule details are provided in the Schedule section. However the instruction says preserve ALL substantive information; we can keep it in both places? Duplication is okay? They said remove duplicated lines. So we should avoid duplicating the same sentence. So we should not repeat schedule info in Role Overview if we have a Schedule section. So we will edit Role Overview to exclude the schedule sentence, but keep location and reporting location variation. Thus Role Overview paragraph: "EOTSS is seeking an HR Operations Specialist to provide day-to-day operational and administrative support to the EOTSS Human Resources team. The position supports key HR functions, including recruitment and hiring, employee onboarding, payroll and personnel transactions, compliance activities, and employee records management. The HR Operations Specialist works closely with HR staff, recruiters, hiring managers, and business partners to coordinate and complete HR processes accurately and on time. The position plays an important role in maintaining accurate HR information, tracking required documentation and approvals, responding to routine HR inquiries, and ensuring processes are completed in accordance with Commonwealth