Jobs · Pennsylvania

Director, Oracle HCM

KPMG US · Harrisburg, PA · 4 wk ago
HybridFull-time
We need to produce HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting mentions benefits: "comprehensive, competitive benefits package", details about medical, dental, vision, disability, life insurance, 401(k), personal well-being benefits, PTO, holidays, breaks. So Benefits section is present. Pay: posting mentions salary ranges but says "KPMG LLP and its affiliates ... complies with all local/state regulations regarding displaying salary ranges. If required, the ranges displayed below or via the URL below are specifically for those potential hires who will work in the location(s) listed. Any offered salary is determined based on relevant factors..." It also provides a link to salary ranges by city outside of CA. So there is some pay info (salary ranges) though not explicit numbers. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that salary ranges are displayed via link, and that they comply with regulations. So we can include a Pay section with that info (maybe summarizing that salary ranges are available via link). However we must not invent or summarize away detail. We can include a

that says salary ranges are available via the provided link and are determined based on factors. That's preserving info. Schedule: posting does not mention schedule specifics (like full-time, part-time, remote). It mentions travel up to 80-100%, but not schedule. So we should not create Schedule section. Skills: posting includes qualifications and responsibilities; we could have a Skills section if there is explicit skills list. The posting includes "Strong client services orientation", "Excellent team building, mentoring, and leadership abilities", "Ability to formulate and express ideas clearly and effectively in verbal and written presentations". Those could be skills. But we already have Qualifications and Requirements sections. The instruction: "Prefer a few substantive sections over many thin ones." We could combine skills into Qualifications or Requirements. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have About the role: The initial paragraph about KPMG Advisory practice, opportunities, etc. That's about the role/firm. Could be About the role. Responsibilities: clearly listed after "Responsibilities :". So include. Requirements: The posting has "Qualifications :" but also includes some requirements like experience, degree, etc. Could treat as Requirements. But we also have Qualifications heading separate. Might be redundant. The instruction says use headings for those specific labels if content exists. We have both "Qualifications :" and also maybe "Requirements" not explicitly labeled but we can infer from the bullet list after Qualifications. However the posting uses "Qualifications :" heading. It does not have a separate "Requirements :" heading. So we should include a Qualifications section with the content under that heading. Should we also include a Requirements section? The posting does not have a separate Requirements heading; but we could treat the content under Qualifications as requirements. To avoid thin sections, we could just have Qualifications and not Requirements. However the instruction list includes Requirements as a possible heading; we can omit if no specific content labeled as Requirements. The posting does not have a separate "Requirements" label; but the content after "Qualifications :" includes experience, degree, etc. That's effectively requirements. So we could put that under Qualifications. We'll not create a separate Requirements section. Skills: The posting includes skills like "Strong client services orientation", "Excellent team building, mentoring, and leadership abilities", "Ability to formulate and express ideas clearly and effectively". Those could be under Skills. But they are also part of Qualifications. To avoid duplication, we could put them under Skills and keep Qualifications more about experience/education. However the posting lumps them together under Qualifications. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we split, we need to ensure we don't lose any info. We could keep Qualifications as is (including experience, degree, etc.) and also have Skills for the soft skills. That would duplicate some content? Not exactly; we would be moving some sentences to Skills. That's okay as long as we preserve all info. But we must not invent or summarize away detail. Moving sentences is fine as long as we keep them verbatim. Better approach: Use sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly Skills if we want to separate soft skills. But we can also keep Qualifications inclusive. Let's examine the posting text for each piece: - About the role: first paragraph(s) up to "consider a career in Advisory." That's descriptive. - Responsibilities: after "Responsibilities :" list. - Qualifications: after "Qualifications :" list includes: * A minimum of eight years of Oracle HCM ERP experience with leading Oracle HCM implementations and upgrades * A minimum of one year of experience leading Oracle Human Capital Management (HCM) implementations and upgrades * Bachelor's degree in Accounting, Business, Computer Science or a related field from an accredited college/university * Experience in managing large projects and team members with the ability to formulate and express ideas clearly and effectively in verbal and written presentations * Strong client services orientation and accustomed to taking an active role in executing projects * Excellent team building, mentoring, and leadership abilities * Travel may be up to 80-100% * Must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future. KPMG LLP will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa) - Benefits: after "In addition, KPMG is proud to offer a comprehensive, competitive benefits package..." includes medical, dental, vision, disability, life insurance, 401(k), personal well-being benefits, PTO, holidays, breaks. - Pay: after "KPMG LLP and its affiliates and subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges. If required, the ranges displayed below or via the URL below are specifically for those potential hires who will work in the location(s) listed. Any offered salary is determined based on relevant factors such as applicant's skills, job responsibilities, prior relevant experience, certain degrees and certifications and market considerations." plus link. - Schedule: none. Thus we will output sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We must not include empty sections. We need to use

for section headings. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must not repeat job title as heading. The job title is "Director, Oracle HCM r our Consulting practice." (typo). We must not put that as heading. We must not put Job ID/requisition numbers as headings. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out lines like "KPMG is an equal opportunity employer..." etc. Also remove "No phone calls or agencies please." etc. Also remove "Los Angeles County applicants: Material job duties..." etc. Also remove "KPMG offers a comprehensive compensation and benefits package." (some duplication). Also remove "KPMG is an equal opportunity employer..." etc. Also remove "The attached link contains further information regarding KPMG's compliance..." etc. Also remove "KPMG recruits on a rolling basis..." etc. Also remove "Follow this link to obtain salary ranges by city outside of CA: ..."? Actually that link is part of Pay info; we should keep it as it's relevant to pay. But the instruction says remove application instructions. That link is not an application instruction; it's pay transparency. So keep. We also need to remove duplicated lines: The posting repeats "KPMG offers a comprehensive compensation and benefits package." and later "In addition, KPMG is proud to offer a comprehensive, competitive benefits package..." We'll keep the latter as benefits; drop the former. Also remove "KPMG LLP and its affiliates and subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges." That's pay info; keep. Also remove "KPMG is proud to offer a comprehensive, competitive benefits package, with options designed to help you make the best decisions for yourself, your family, and your lifestyle." Keep as benefits. Also remove "Available benefits are based on eligibility." Keep. Also remove "Our Total Rewards package includes a variety of medical and dental plans, vision coverage, disability and life insurance, 401(k) plans, and a robust suite of personal well-being benefits to support your mental health." Keep. Also remove "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year. Additionally, each year KPMG publishes a calendar of holidays to be observed during the year and provides eligible employees two breaks each year where employees will not be required to use Personal Time Off; one is at year end and the other is around the July 4th holiday." Keep. Also remove "Additional details about our benefits can be found towards the bottom of our KPMG US Careers site at Benefits & How We Work." Could be considered boilerplate? It's a reference to more details; maybe keep as part of benefits? It's not substantive detail but a pointer. Might be considered boilerplate; but it's not navigation/legal/EEO. It's a reference to more info. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This is not exactly those categories; it's a reference to more details. Could keep but it's not substantive detail. Might be considered navigation? It's a link to benefits page. Might be considered navigation. Safer to remove it. Also remove "Follow this link to obtain salary ranges by city outside of CA: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=M130ADV_2_26". That's a link for pay transparency; it's substantive for pay. Keep. Also remove "KPMG offers a comprehensive compensation and benefits package." (duplicate). Already considered. Also remove "KPMG is an equal opportunity employer..." etc. Also remove "KPMG complies with all applicable federal, state and local laws regarding recruitment and hiring..." etc. Also remove "All qualified applicants are considered for employment without regard to ..." etc. Also remove "The attached link contains further information regarding KPMG's compliance with federal, state and local recruitment and hiring laws." etc. Also remove "No phone calls or agencies please." etc. Also remove "KPMG recruits on a rolling basis..." etc. Also remove "Los Angeles County applicants: Material job duties for this position are listed above. Criminal history may have a direct, adverse, and negative relationship with some of the material job duties of this position..." etc. That's legal/EEO? It's about Fair Chance Act; could be considered legal boilerplate. Remove. Also remove "Pursuant to the California Fair Chance Act..." etc. Remove. Now we need to craft HTML. We'll have:

    About the role

    ... (the about role paragraph)

Similar jobs