HR Operations & HRIS Specialist
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them.
We need to extract substantive content: Summary, Essential Functions (list of duties), Minimum Required Qualifications, Desired Qualifications, Work Environment (maybe not needed), Compensation & Benefits (Pay and Benefits). Also maybe "Supervisory Responsibilities" (no formal supervisory responsibilities) - could be omitted as not needed? Might be considered not a section.
We need to decide sections: About the role (summary), Responsibilities (essential functions), Requirements (minimum required qualifications), Qualifications (desired qualifications?), Skills (maybe combine?), Benefits, Pay. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content.
We have content for About the role (summary). Responsibilities (essential functions). Requirements (minimum required qualifications). Qualifications (desired qualifications). Skills maybe not explicit separate; could be omitted if no specific skills list beyond qualifications. Benefits: posting mentions benefits package: health benefits, retirement contributions, paid time off, bonus eligibility. So we can create Benefits section with list. Pay: posting gives salary range $69,906.75 - $100,000.00 per year, plus note about offers typically bottom half, etc. That's specific content, so we can include Pay section. Schedule: not mentioned (virtual, open to residents, but no schedule like full-time/part-time). Could infer full-time but not explicitly stated; better not to create Schedule section if no explicit schedule info. Work environment maybe not needed.
We must not include boilerplate like "Reasonable accommodations may be made..." duplicates; we can keep maybe one mention but it's boilerplate; better to remove. Also remove duplicated lines like "The above job is not intended to be an all-inclusive list..." repeated twice; we should keep only once? Probably remove as boilerplate. Also remove EEO statement, application instructions, contact for accommodation, etc.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the details from essential functions, qualifications, compensation, benefits.
We need to format as HTML fragment: use
for each section heading, then content: either
for prose or
- for lists.
We need to decide what goes into lists: Essential functions are a list of duties; we can put each bullet as
- . Minimum required qualifications also list; desired qualifications list; benefits list.
We need to ensure we don't repeat headings unnecessarily.
Let's extract:
Summary (About the role):
"The HR Operations Specialist plays a key role in supporting HR initiatives through a combination of project coordination and HRIS partnership. Sitting at the intersection of HR Operations and HRIS, this role helps drive execution of recurring HR programs, system-related work, Workday enhancements, reporting and dashboard development, and process improvement initiatives across the HR organization. This role is ideal for someone who enjoys building and managing project plans, coordinating cross-functional work, understanding how HR processes and systems connect, and partnering closely with HRIS on activities such as requirements gathering, testing coordination, business process documentation, and Workday-related support. Success in this role requires strong organizational and communication skills, attention to detail, and the ability to connect day-to-day work to broader operational goals, system impacts, and business priorities."
That's prose; we can put in
.
Essential Functions (Responsibilities):
List items:
- Lead planning and execution of HR projects, including recurring annual cycles and system-related work, by managing timelines, dependencies, risks, and cross-functional alignment across HR teams and systems
- Manage the Workday enhancement process through sprint planning and backlog management, partnering with cross-functional stakeholders to define priorities, requirements, scope, and delivery timelines
- Partner closely with HRIS to support system-related initiatives, including gathering and validating requirements, facilitating testing activities, and documenting current and future state business processes and workflows in Visio
- Evaluate, prioritize, and facilitate resolution of HR Operations and Workday-related requests through Fresh service, ensuring alignment with operational priorities, system impacts, and business needs
- Lead documentation of current and future states for key HR business processes in Visio
- Drive change management activities, including stakeholder communications, training, and readiness
- Identify and lead opportunities to improve HR processes, operational workflows, and Workday utilization, supporting implementation of those changes across HR Operations and Workday
- Develop and deliver reporting, dashboards, and operational insights through Smartsheet and related tools to provide visibility into project progress, risks, outcomes, and key operational metrics for stakeholders and leadership teams
- Workday operations support including EIB data loads, provide support for internal and external audit requests (system walk through, provide evidence, support Kainos).
Also "Supervisory Responsibilities: This position has no formal supervisory responsibilities." Could be a note; maybe include as a
under Responsibilities or separate? Not required but we can include as a short note.
Minimum Required Qualifications:
- Five (5) + years of experience supporting HR operations, HR systems, or delivery‑focused program or project work within an HR environment
- Hands‑on experience supporting Workday or similar HR platforms
- Strong understanding of how HR functional areas and systems intersect (e.g., Compensation, Payroll, Talent, Compliance, HRIS)
- Demonstrated experience in project management and change management within an HR environment
- Comfort interacting with and supporting senior stakeholders, including preparing materials and communicating updates
- Strong communication, organization, and prioritization skills
- Interest in HR systems, process improvement, and operational design
- Proficient in Office 365 and strong functional experience in Workday
- Ability to clear required background check
- Certificates and Licenses: None required. (maybe we can include as a note)
Desired Qualifications:
- Bachelor's degree in Human Resources, Business or related field
- Project Management Institute (PMI) certification such as Certified Associate in Project Management (CAPM) or Project Management Professional (PMP)
- Workday Pro certification or equivalent Workday functional training
- Prosci Change Management Certification
Work Environment: maybe not needed but we could include as a short paragraph: "This position is virtual and open to residents of the 50 states, D.C." That's substantive; we could put under a heading like "Work Environment" but not in the list of allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Work Environment not in list; but we could incorporate into About the role or Responsibilities? Probably better to omit as not required heading; but we might lose info. However instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings if needed? But they say "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add Work Environment heading. We could incorporate that info into About the role or Responsibilities as a sentence. It's about virtual nature; we could add to About the role paragraph.
Compensation & Benefits: we need separate Pay and Benefits sections if content exists.
Pay: "We anticipate the salary range to be $69,906.75 - $100,000.00 per year. The upper end of this range is not likely to be offered, as an individual’s compensation can vary based on several factors. These factors include, but are not limited to, geographic location, experience, training, education, and local market conditions. Eligible employees may receive a bonus." Also earlier: "Stride, Inc. considers a person’s education, experience, and qualifications, as well as the position’s work location, expected quality and quantity of work, required travel (if any), external market and internal value when determining a new employee’s salary level. Salaries will differ based on these factors, the position’s level and expected contribution, and the employee’s benefits elections. Offers will typically be in the bottom half of the range." That's substantive.
We should include all that in Pay section as prose or list? Probably prose.
Benefits: "Stride offers a robust benefits package for eligible employees that can include health benefits, retirement contributions, and paid time off." Also earlier: "Eligible employees may receive a bonus." Bonus could be part of Pay or Benefits; but we already mentioned bonus in Pay. We'll keep benefits as health benefits, retirement contributions, paid time off.
We must not include boilerplate like "The above job is not intended to be an all-inclusive list..." duplicates; we should remove.
Also remove "Reasonable accommodations may be made..." duplicates; we can keep one maybe but it's boilerplate; better to remove.
Also remove EEO statement, application instructions, contact for accommodation, etc.
Now construct HTML.
We'll have:
About the role
... summary plus maybe virtual note.
Responsibilities
- ...
...
Supervisory Responsibilities: This position has no formal supervisory responsibilities.
(maybe as )
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- Health benefits
- Retirement contributions
- Paid time off
Pay
... compensation details.
We need to ensure we don't include Schedule section.
Check for any placeholder/filler: none.
Now craft the exact text.
About the role paragraph: combine summary and virtual note.
Summary: "The HR Operations Specialist plays a key role in supporting HR initiatives through a combination of project coordination and HRIS partnership. Sitting at the intersection of HR Operations and HRIS, this role helps drive execution of recurring HR programs, system-related work, Workday enhancements, reporting and dashboard development, and process improvement initiatives across the HR organization. This role is ideal for someone who enjoys building and managing project plans, coordinating cross-functional work, understanding how HR processes and systems connect, and partnering closely with HRIS on activities such as requirements gathering, testing coordination, business process documentation, and Workday-related support. Success in this role requires strong organizational and communication skills, attention to detail, and the ability to connect day-to-day work to broader operational goals, system impacts, and business priorities."
Add virtual note: "This position is virtual and open to residents of the 50 states, D.C."
Combine into one paragraph.
Now Responsibilities list: include the 9 items.
Check for any duplication: "Lead documentation of current and future states for key HR business processes in Visio" appears twice? Actually we have "Partner closely with HRIS to support system-related initiatives, including gathering and validating requirements, facilitating testing activities, and documenting current and future state business processes and workflows in Visio" and later "Lead documentation of current and future states for key HR business processes in Visio". They are similar but
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. We need to extract substantive content: Summary, Essential Functions (list of duties), Minimum Required Qualifications, Desired Qualifications, Work Environment (maybe not needed), Compensation & Benefits (Pay and Benefits). Also maybe "Supervisory Responsibilities" (no formal supervisory responsibilities) - could be omitted as not needed? Might be considered not a section. We need to decide sections: About the role (summary), Responsibilities (essential functions), Requirements (minimum required qualifications), Qualifications (desired qualifications?), Skills (maybe combine?), Benefits, Pay. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. We have content for About the role (summary). Responsibilities (essential functions). Requirements (minimum required qualifications). Qualifications (desired qualifications). Skills maybe not explicit separate; could be omitted if no specific skills list beyond qualifications. Benefits: posting mentions benefits package: health benefits, retirement contributions, paid time off, bonus eligibility. So we can create Benefits section with list. Pay: posting gives salary range $69,906.75 - $100,000.00 per year, plus note about offers typically bottom half, etc. That's specific content, so we can include Pay section. Schedule: not mentioned (virtual, open to residents, but no schedule like full-time/part-time). Could infer full-time but not explicitly stated; better not to create Schedule section if no explicit schedule info. Work environment maybe not needed. We must not include boilerplate like "Reasonable accommodations may be made..." duplicates; we can keep maybe one mention but it's boilerplate; better to remove. Also remove duplicated lines like "The above job is not intended to be an all-inclusive list..." repeated twice; we should keep only once? Probably remove as boilerplate. Also remove EEO statement, application instructions, contact for accommodation, etc. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the details from essential functions, qualifications, compensation, benefits. We need to format as HTML fragment: use
for each section heading, then content: either
for prose or
- for lists. We need to decide what goes into lists: Essential functions are a list of duties; we can put each bullet as
- . Minimum required qualifications also list; desired qualifications list; benefits list.
We need to ensure we don't repeat headings unnecessarily.
Let's extract:
Summary (About the role):
"The HR Operations Specialist plays a key role in supporting HR initiatives through a combination of project coordination and HRIS partnership. Sitting at the intersection of HR Operations and HRIS, this role helps drive execution of recurring HR programs, system-related work, Workday enhancements, reporting and dashboard development, and process improvement initiatives across the HR organization. This role is ideal for someone who enjoys building and managing project plans, coordinating cross-functional work, understanding how HR processes and systems connect, and partnering closely with HRIS on activities such as requirements gathering, testing coordination, business process documentation, and Workday-related support. Success in this role requires strong organizational and communication skills, attention to detail, and the ability to connect day-to-day work to broader operational goals, system impacts, and business priorities."
That's prose; we can put in
. Essential Functions (Responsibilities): List items: - Lead planning and execution of HR projects, including recurring annual cycles and system-related work, by managing timelines, dependencies, risks, and cross-functional alignment across HR teams and systems - Manage the Workday enhancement process through sprint planning and backlog management, partnering with cross-functional stakeholders to define priorities, requirements, scope, and delivery timelines - Partner closely with HRIS to support system-related initiatives, including gathering and validating requirements, facilitating testing activities, and documenting current and future state business processes and workflows in Visio - Evaluate, prioritize, and facilitate resolution of HR Operations and Workday-related requests through Fresh service, ensuring alignment with operational priorities, system impacts, and business needs - Lead documentation of current and future states for key HR business processes in Visio - Drive change management activities, including stakeholder communications, training, and readiness - Identify and lead opportunities to improve HR processes, operational workflows, and Workday utilization, supporting implementation of those changes across HR Operations and Workday - Develop and deliver reporting, dashboards, and operational insights through Smartsheet and related tools to provide visibility into project progress, risks, outcomes, and key operational metrics for stakeholders and leadership teams - Workday operations support including EIB data loads, provide support for internal and external audit requests (system walk through, provide evidence, support Kainos). Also "Supervisory Responsibilities: This position has no formal supervisory responsibilities." Could be a note; maybe include as a
under Responsibilities or separate? Not required but we can include as a short note. Minimum Required Qualifications: - Five (5) + years of experience supporting HR operations, HR systems, or delivery‑focused program or project work within an HR environment - Hands‑on experience supporting Workday or similar HR platforms - Strong understanding of how HR functional areas and systems intersect (e.g., Compensation, Payroll, Talent, Compliance, HRIS) - Demonstrated experience in project management and change management within an HR environment - Comfort interacting with and supporting senior stakeholders, including preparing materials and communicating updates - Strong communication, organization, and prioritization skills - Interest in HR systems, process improvement, and operational design - Proficient in Office 365 and strong functional experience in Workday - Ability to clear required background check - Certificates and Licenses: None required. (maybe we can include as a note) Desired Qualifications: - Bachelor's degree in Human Resources, Business or related field - Project Management Institute (PMI) certification such as Certified Associate in Project Management (CAPM) or Project Management Professional (PMP) - Workday Pro certification or equivalent Workday functional training - Prosci Change Management Certification Work Environment: maybe not needed but we could include as a short paragraph: "This position is virtual and open to residents of the 50 states, D.C." That's substantive; we could put under a heading like "Work Environment" but not in the list of allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Work Environment not in list; but we could incorporate into About the role or Responsibilities? Probably better to omit as not required heading; but we might lose info. However instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings if needed? But they say "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add Work Environment heading. We could incorporate that info into About the role or Responsibilities as a sentence. It's about virtual nature; we could add to About the role paragraph. Compensation & Benefits: we need separate Pay and Benefits sections if content exists. Pay: "We anticipate the salary range to be $69,906.75 - $100,000.00 per year. The upper end of this range is not likely to be offered, as an individual’s compensation can vary based on several factors. These factors include, but are not limited to, geographic location, experience, training, education, and local market conditions. Eligible employees may receive a bonus." Also earlier: "Stride, Inc. considers a person’s education, experience, and qualifications, as well as the position’s work location, expected quality and quantity of work, required travel (if any), external market and internal value when determining a new employee’s salary level. Salaries will differ based on these factors, the position’s level and expected contribution, and the employee’s benefits elections. Offers will typically be in the bottom half of the range." That's substantive. We should include all that in Pay section as prose or list? Probably prose. Benefits: "Stride offers a robust benefits package for eligible employees that can include health benefits, retirement contributions, and paid time off." Also earlier: "Eligible employees may receive a bonus." Bonus could be part of Pay or Benefits; but we already mentioned bonus in Pay. We'll keep benefits as health benefits, retirement contributions, paid time off. We must not include boilerplate like "The above job is not intended to be an all-inclusive list..." duplicates; we should remove. Also remove "Reasonable accommodations may be made..." duplicates; we can keep one maybe but it's boilerplate; better to remove. Also remove EEO statement, application instructions, contact for accommodation, etc. Now construct HTML. We'll have:
About the role
... summary plus maybe virtual note.
Responsibilities
- ... ...
Supervisory Responsibilities: This position has no formal supervisory responsibilities.
(maybe as)
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- Health benefits
- Retirement contributions
- Paid time off
Pay
... compensation details.
We need to ensure we don't include Schedule section. Check for any placeholder/filler: none. Now craft the exact text. About the role paragraph: combine summary and virtual note. Summary: "The HR Operations Specialist plays a key role in supporting HR initiatives through a combination of project coordination and HRIS partnership. Sitting at the intersection of HR Operations and HRIS, this role helps drive execution of recurring HR programs, system-related work, Workday enhancements, reporting and dashboard development, and process improvement initiatives across the HR organization. This role is ideal for someone who enjoys building and managing project plans, coordinating cross-functional work, understanding how HR processes and systems connect, and partnering closely with HRIS on activities such as requirements gathering, testing coordination, business process documentation, and Workday-related support. Success in this role requires strong organizational and communication skills, attention to detail, and the ability to connect day-to-day work to broader operational goals, system impacts, and business priorities." Add virtual note: "This position is virtual and open to residents of the 50 states, D.C." Combine into one paragraph. Now Responsibilities list: include the 9 items. Check for any duplication: "Lead documentation of current and future states for key HR business processes in Visio" appears twice? Actually we have "Partner closely with HRIS to support system-related initiatives, including gathering and validating requirements, facilitating testing activities, and documenting current and future state business processes and workflows in Visio" and later "Lead documentation of current and future states for key HR business processes in Visio". They are similar but