Senior Project Manager – ERP / Benefits Operations
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can use other headings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should use those exact headings? Probably we should map content to those headings where appropriate. For job summary we could use "About the role". Responsibilities -> "Responsibilities". Required Qualifications -> "Requirements" or "Qualifications"? They said Requirements, Qualifications as possible headings. We have both Required and Preferred qualifications. Could combine into "Qualifications". Or separate "Required Qualifications" and "Preferred Qualifications" as subheadings? But instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings, not variations. So we need to decide which sections to include: About the role (job summary), Responsibilities, Qualifications (maybe combine required and preferred), Skills? There's no explicit skills section but we could embed skills in qualifications. Could also include "Requirements" for required qualifications and "Qualifications" for preferred? But they said we can use those headings; we can choose to include both Requirements and Qualifications if we have content. However they said prefer a few substantive sections over many thin ones. So maybe combine required and preferred into one Qualifications section.
We also have "Ideal Candidate" which could be part of About the role or Qualifications. Could incorporate into About the role.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information. So we need to include all details from job summary, responsibilities, required qualifications, preferred qualifications, ideal candidate, recruiter screening keywords? Keywords maybe not substantive? It's metadata but could be considered part of qualifications? Probably we can drop recruiter screening keywords as it's just keywords for screening, not substantive content. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Keywords not listed but could be considered metadata; but it's not boilerplate. However it's not a section heading; we could embed as a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings, not variations. So we need to decide which sections to include: About the role (job summary), Responsibilities, Qualifications (maybe combine required and preferred), Skills? There's no explicit skills section but we could embed skills in qualifications. Could also include "Requirements" for required qualifications and "Qualifications" for preferred? But they said we can use those headings; we can choose to include both Requirements and Qualifications if we have content. However they said prefer a few substantive sections over many thin ones. So maybe combine required and preferred into one Qualifications section. We also have "Ideal Candidate" which could be part of About the role or Qualifications. Could incorporate into About the role. We must not repeat job title as heading. No Job ID. We must preserve all substantive information. So we need to include all details from job summary, responsibilities, required qualifications, preferred qualifications, ideal candidate, recruiter screening keywords? Keywords maybe not substantive? It's metadata but could be considered part of qualifications? Probably we can drop recruiter screening keywords as it's just keywords for screening, not substantive content. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Keywords not listed but could be considered metadata; but it's not boilerplate. However it's not a section heading; we could embed as a
maybe. But better to drop as it's not essential? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Keywords are substantive? They list relevant terms; could be considered part of qualifications. Might be safe to include as a
under Qualifications or as a separate "Keywords" but not a heading. Since they didn't give a heading for keywords, we could just include as a paragraph. We must not include Pay/Schedule/Benefits unless posting states them. Not present. Thus output:
About the role
Job Summary ...
Responsibilities
- ... ...
Qualifications
Required Qualifications: ...
Preferred Qualifications: ...
Ideal Candidate: ...
Recruiter Screening Keywords: ...
But we need to avoid repeating headings like "Required Qualifications:" inside a paragraph; that's okay. We must use- for any list of duties/requirements/benefits. So responsibilities list as ul. Also maybe list of qualifications? Could also list as ul but not required; but we can keep as p.
We need to preserve all details. Let's extract.
Job Summary paragraph:
"We are seeking an experienced Senior Project Manager to lead complex projects and issue-resolution initiatives involving ERP/Workday configuration, employee and payroll data, integrations, benefits administration, transaction processing, vendor systems, and business processes. The ideal candidate will coordinate cross-functional teams across functional and technical areas, payroll, finance, business analysis, and third-party vendors. This role will drive issues from identification and prioritization through root-cause analysis, corrective action, testing, production deployment, reconciliation, employee remediation, and final closure."
Key Responsibilities list:
- Establish and manage a centralized project/issue backlog, including business impact, severity, affected population, owners, dependencies, target dates, and closure criteria.
- Lead cross-functional teams responsible for resolving complex business and technical issues.
- Establish clear action items, owners, deadlines, and accountability across project teams.
- Track commitments, address roadblocks, follow up on overdue actions, and escalate risks when necessary.
- Maintain detailed meeting notes, decisions, action items, open issues, and completion dates.
- Develop and maintain integrated project schedules across functional, technical, payroll, finance, and vendor workstreams.
- Define project roles, responsibilities, dependencies, and ownership.
- Lead issue-triage, working sessions, decision meetings, and executive status meetings.
- Coordinate root-cause analysis involving Workday configuration, source data, integration logic, vendor processing, transaction timing, and business processes.
- Manage dependencies across integrations and ensure teams do not implement conflicting solutions.
- Coordinate test planning, test data, expected results, regression testing, vendor validation, and business acceptance.
- Manage change control and release readiness from non-production environments through production deployment.
- Validate that corrected integrations reconcile with Workday payroll and benefits results.
- Ensure affected employee records and financial transactions are properly addressed.
- Track risks, decisions, overdue actions, resource constraints, and unresolved ownership.
- Provide concise executive reporting covering issue aging, affected populations, financial exposure, testing status, blocked decisions, and resolution trends.
Required Qualifications:
- Bachelor's degree in a related field from an accredited college or university.
- Minimum 3 years of recent, relevant project management experience with increasing levels of responsibility.
- Eligibility to sit for the Project Management Professional (PMP) certification.
- Strong project management, communication, organization, problem-solving, and stakeholder-management skills.
- Experience coordinating cross-functional business and technical teams.
Preferred Qualifications:
- Experience with ERP implementations, particularly Workday/HCM.
- Experience implementing or supporting HR, payroll, benefits, or HCM business processes.
- Experience working with government organizations or public-sector environments.
- 6+ years of project management experience supporting business processes.
- Experience with Software Development Life Cycle (SDLC) methodologies.
- Experience implementing structured project/program management processes.
- Hands-on experience with project management tools such as: Jira, MS Project, Asana.
- PMP or CAPM certification preferred.
- Experience working with integrations, data reconciliation, testing, release management, and vendor coordination is highly desirable.
Ideal Candidate:
"The ideal candidate is a Senior Project Manager / Program Manager who can bridge business and technical teams and take complex issues from discovery to verified resolution. Strong candidates will have experience with Workday/ERP, HCM, payroll, benefits, integrations, SDLC, project governance, testing, and executive reporting."
Recruiter Screening Keywords:
"Senior Project Manager, Project Manager, Program Manager, Workday, HCM, ERP, Benefits, Payroll, Integrations, SDLC, Jira, MS Project, Asana, PMP, CAPM, Data Reconciliation, Release Management, Change Management, UAT, Government, Public Sector"
Note: This is a long-term opportunity in Atlanta, GA. Candidates should be local to the Atlanta area and available to report to the office occasionally.
We could include location/duration in About the role paragraph or as a separate note. Since it's substantive, we should preserve. Could add a paragraph after About the role: "Location: Atlanta, GA. Duration: Long-Term. Work Arrangement: Local candidates preferred; must be able to come into the office occasionally."
We must not create headings for location/duration unless we have a heading like "About the role" already covers.
Thus final HTML:
About the role
We are seeking an experienced Senior Project Manager to lead complex projects and issue-resolution initiatives involving ERP/Workday configuration, employee and payroll data, integrations, benefits administration, transaction processing, vendor systems, and business processes. The ideal candidate will coordinate cross-functional teams across functional and technical areas, payroll, finance, business analysis, and third-party vendors. This role will drive issues from identification and prioritization through root-cause analysis, corrective action, testing, production deployment, reconciliation, employee remediation, and final closure. Location: Atlanta, GA. Duration: Long-Term. Work Arrangement: Local candidates preferred; must be able to come into the office occasionally.
Responsibilities
- Establish and manage a centralized project/issue backlog, including business impact, severity, affected population, owners, dependencies, target dates, and closure criteria.
- Lead cross-functional teams responsible for resolving complex business and technical issues.
- Establish clear action items, owners, deadlines, and accountability across project teams.
- Track commitments, address roadblocks, follow up on overdue actions, and escalate risks when necessary.
- Maintain detailed meeting notes, decisions, action items, open issues, and completion dates.
- Develop and maintain integrated project schedules across functional, technical, payroll, finance, and vendor workstreams.
- Define project roles, responsibilities, dependencies, and ownership.
- Lead issue-triage, working sessions, decision meetings, and executive status meetings.
- Coordinate root-cause analysis involving Workday configuration, source data, integration logic, vendor processing, transaction timing, and business processes.
- Manage dependencies across integrations and ensure teams do not implement conflicting solutions.
- Coordinate test planning, test data, expected results, regression testing, vendor validation, and business acceptance.
- Manage change control and release readiness from non-production environments through production deployment.
- Validate that corrected integrations reconcile with Workday payroll and benefits results.
- Ensure affected employee records and financial transactions are properly addressed.
- Track risks, decisions, overdue actions, resource constraints, and unresolved ownership.
- Provide concise executive reporting covering issue aging, affected populations, financial exposure, testing status, blocked decisions, and resolution trends.
Qualifications
Required Qualifications:
- Bachelor's degree in a related field from an accredited college or university.
- Minimum 3 years of recent, relevant project management experience with increasing levels of responsibility.
- Eligibility to sit for the Project Management Professional (PMP) certification.
- Strong project management, communication, organization, problem-solving, and stakeholder-management skills.
- Experience coordinating cross-functional business and technical teams.
Preferred Qualifications:
- Experience with ERP implementations, particularly Workday/HCM.
- Experience implementing or supporting HR, payroll, benefits, or HCM business processes.
- Experience working with government organizations or public-sector environments.
- 6+ years of project management experience supporting business processes.
- Experience with Software Development Life Cycle (SDLC) methodologies.
- Experience implementing structured project/program management processes.
- Hands-on experience with project management tools such as: Jira, MS Project, Asana.
- PMP or CAPM certification preferred.
- Experience working with integrations, data reconciliation, testing, release management, and vendor coordination is highly desirable.
Ideal Candidate: The ideal