HRIS Project Manager

We need to output HTML fragment with sections: Overview (maybe "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real content. The posting includes Overview (description), Duties & Responsibilities, Requirements, Education, Compensation, Benefits. Also maybe "Company Profile" but that's not a heading we need; we can incorporate into Overview? The instruction: do NOT repeat the job title as a heading. Use

for section headings. So we need headings like "Overview", "Responsibilities", "Requirements", "Education", "Compensation", "Benefits"? Actually "Compensation" and "Benefits". Also maybe "Qualifications" but we have Requirements and Education separate. Could combine Education under Requirements? But we have separate Education section; we can make a heading "Education". Also "Skills" not explicitly listed; we could omit. "Pay" same as Compensation. "Schedule" not given (they mention 6+ month remote role, mostly MST/CST, may require light travel). That's schedule info; we could include a Schedule section. The instruction: include a section ONLY when posting has real, specific content for it. So we can add Schedule with details: 6+ month remote role, mostly MST and CST time zones, may require some light travel. That's specific. Also Pay: they gave salary range $70,000-$100,000. So we can include Pay section. Benefits: they gave a paragraph about benefits. So include Benefits. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities we should list each duty as
• . For Requirements list each requirement as
• . For Benefits list each benefit as
• maybe? The benefits paragraph is prose; we could keep as

  but instruction says use

  • for any list of duties/requirements/benefits. Benefits is not a list but we could still use

    . However we could split into bullet points? The paragraph is not a list; better to keep as

    . For Education we could list as

    • . For Pay we could just

      . For Schedule we could

      . For Overview we could

      . We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting. Let's extract content: Company Profile: At Sand Cherry Associates, we excel in the design and delivery of strategic customer-centric initiatives through digitally native, data-empowered solutions. Our client's confidence in us is centered on exceptionally skilled, high-energy talent working with the support of the full Sand Cherry team. Finding the right match for this role is a critical aspect of continuing that success. Overview: We are seeking an experienced Project Manager to lead and support an HR technology transformation initiative. This individual will be responsible for managing the implementation of Workday and coordinating the transition of HR processes and systems into a new HRIS environment. The ideal candidate is a proven project manager with experience leading HRIS implementations, particularly Workday, and the ability to manage complex, cross-functional initiatives involving HR, Payroll, IT, Finance, and other key stakeholders. This is a hands-on project management role requiring strong organizational skills, stakeholder management, communication, and the ability to drive projects from planning through successful implementation. This is a 6+ month remote role working mostly in MST and CST time zones and may require some light travel. All candidates must be authorized to work in the United States without current or future visa sponsorship or transfers. We are unable to work with C2C arrangements for this opportunity. Duties & Responsibilities: list each bullet. Let's list them: - Lead the end-to-end project management of the Workday HRIS implementation, including planning, execution, testing, deployment, and post-implementation activities. - Develop and maintain comprehensive project plans, timelines, milestones, dependencies, and deliverables. - Establish project governance, meeting cadence, status reporting, and escalation processes. - Partner with HR, Payroll, IT, Finance, and business stakeholders to define requirements, priorities, and project objectives. - Coordinate activities across internal teams, Workday implementation partners, vendors, and other project stakeholders. - Manage project scope, schedule, budget, risks, issues, assumptions, and dependencies. - Facilitate project meetings and working sessions, ensuring clear action items, owners, and deadlines. - Track project progress and provide regular updates to leadership and key stakeholders. - Identify potential risks and roadblocks and develop mitigation and contingency plans. - Support business process design and alignment with the capabilities of the Workday platform. - Coordinate data migration, integrations, configuration, testing, and other implementation workstreams. - Lead or coordinate User Acceptance Testing (UAT), including test planning, execution, issue tracking, and resolution. - Support organizational readiness, communications, training, and change management activities associated with the new HRIS. - Ensure appropriate documentation is developed and maintained throughout the project lifecycle. - Coordinate cutover and go-live readiness activities and support post-go-live stabilization. - Drive accountability across workstreams to ensure deliverables are completed on time and meet quality expectations. - Identify opportunities to improve HR processes and maximize the value of the new HRIS environment. Requirements: list each bullet. - 5+ years of project management experience, with a proven track record leading complex, cross-functional initiatives. - Demonstrated experience managing HRIS implementations, with specific Workday implementation experience required. - Experience managing projects through the full implementation lifecycle, including planning, requirements gathering, design, testing, deployment, go-live, and post-implementation stabilization. - Strong understanding of HR processes and HR technology environments. - Experience working cross-functionally with HR, Payroll, IT, Finance, and business stakeholders. - Experience coordinating data migration, system integrations, configuration, testing, and User Acceptance Testing (UAT). - Experience managing vendors, implementation partners, and third-party resources. - Strong project planning, organization, prioritization, problem-solving, and risk management skills. - Excellent written and verbal communication skills, with the ability to effectively communicate with both technical and executive audiences. - Proven ability to manage multiple workstreams, competing priorities, dependencies, and deadlines. - Experience supporting organizational change management, communications, training, and organizational readiness activities. - Proficiency with Microsoft Office/Office 365 and project management tools. - Experience with multiple Workday modules, such as HCM, Payroll, Benefits, Recruiting, Time Tracking, or Absence, preferred. - Experience with HR technology integrations and complex data migration initiatives preferred. Education: list each bullet. - Bachelor's degree in Business, Human Resources, Information Systems, Project Management, or a related field preferred. - PMP, Prosci, Workday, or other relevant project/change management certification preferred. Compensation: paragraph: "Sand Cherry Associates is required by Colorado law to include a reasonable estimate of the compensation range for this role. This compensation range considers a wide range of factors considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and delivery model. This is a long-term consulting opportunity with a salary range of $70,000-$100,000. Years of experience, level of education, geographic location, unique skills/qualifications for the specific role and potential certifications can be key factors in the final compensation for this role." We need to keep all that. Could be a

      . Benefits: paragraph: "Our team is unique — we are passionate about what we do. At Sand Cherry, our Consultants know they are impacting and shaping our clients' industries. We recognize our employees for their contributions. Our culture is one of the most friendly and communicative in the consulting industry. Sand Cherry is not a top-heavy organization. We offer the opportunity to be part of a digital workforce. Discover the experience that only comes with self-responsibility in the workplace. Our team members manage their own workloads and are expected to deliver exceptional work for our clients. Professional career growth is one of our main priorities, as we affirm that investing in our Consultants and empowering our people will also deliver the best results and value for our clients." We'll keep as

      . Schedule: we have info: "This is a 6+ month remote role working mostly in MST and CST time zones and may require some light travel." Also maybe mention remote. We'll put in Schedule section. We also need to include authorization to work in US etc. That's part of Overview maybe; we already included in Overview paragraph. Should we separate? It's part of Overview; we can keep there. Now produce HTML fragment with

      headings and appropriate

      or

      • . We must not include or . Just the fragment. Let's structure:

        Overview

        ... (company profile + overview details)

        But we have company profile separate; we could combine into Overview paragraph. We need to ensure we don't repeat job title; fine. We'll include:

        Overview

        At Sand Cherry Associates, we excel in the design and delivery of strategic customer-centric initiatives through digitally native, data-empowered solutions. Our client's confidence in us is centered on exceptionally skilled, high-energy talent working with the support of the full Sand Cherry team. Finding the right match for this role is a critical aspect of continuing that success. We are seeking an experienced Project Manager to lead and support an HR technology transformation initiative. This individual will be responsible for managing the implementation of Workday and coordinating the transition of HR processes and systems into a new HRIS environment. The ideal candidate is a proven project manager with experience leading HRIS implementations, particularly Workday, and the ability to manage complex, cross-functional initiatives involving HR, Payroll, IT, Finance, and other key stakeholders. This is a hands-on project management role requiring strong organizational skills, stakeholder management, communication, and the ability to drive projects from planning through successful implementation. This is a 6+ month remote role working mostly in MST and CST time zones and may require some light travel. All candidates must be authorized to work in the United States without current or future visa sponsorship or transfers. We are unable to work with C2C arrangements for this opportunity.

        Then Responsibilities:

        Responsibilities

        • ...
        ...
        Requirements:

        Requirements

        • ...
        ...
        Education:

        Education

        • ...
        • ...
        Compensation:

        Compensation

        ...

        Benefits:

        Benefits

        ...

        Schedule:

        Schedule

        This is a 6+ month remote role working mostly in MST and CST time zones and may require some light travel.

        But note we already mentioned schedule in Overview; but we can still have Schedule section with that detail. However we must not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplicating is okay as long as we preserve. But maybe better to keep schedule only in Schedule section and remove from Overview to avoid duplication. However Overview already includes that sentence; we could keep it there and not have Schedule section. But we need to include Schedule section only if posting has real specific content for it. It does; we could keep it there and not duplicate. But we already have that sentence in Overview; we could keep it there and not create Schedule section. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe better to not create Schedule section if we already covered it in Overview. But the Overview already includes that sentence; we could keep it there. However the instruction about sections: Use headings for section headings (e.g. About the role, Responsibilities,