Manager, Supply Chain

We need to output HTML fragment with sections only if there is real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must not include Job ID etc. Remove boilerplate, navigation, EEO, etc. Keep substantive info. Let's parse the posting. First paragraph: intro about KPMG Advisory practice, opportunities, etc. That's generic but maybe "About the role" content? The posting says "KPMG Advisory practice is at the forefront...". That's more about the firm, not specific role. Could be considered "About the role" but it's generic. However we need to include only if real specific content. The posting includes a description of the role: "KPMG is currently seeking a Manager in Customer & Operations for our Consulting practice." Then responsibilities list. Thus we can have sections: About the role (maybe a short paragraph summarizing the role), Responsibilities (list), Qualifications (list), Benefits (maybe mention benefits package), Pay (maybe mention salary ranges link?), Schedule (maybe mention travel up to 80-100%? That's not schedule but travel). Schedule maybe not given. Pay: they mention salary ranges link and that they comply with local regulations, but no specific numbers. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. They do mention benefits package (comprehensive, competitive benefits package, list of medical, dental, vision, disability, life insurance, 401(k), personal well-being benefits, PTO, holidays). That's substantive. So Benefits section is okay. Pay: they mention salary ranges link and that they comply with regulations, but no actual range. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Since they didn't give a specific number, but they gave a link to salary ranges. Is that considered specific? It says "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." They gave a URL. That's still not a specific number but a reference. Might be considered placeholder? Probably better to omit Pay section because no explicit range. Schedule: they mention travel may be up to 80-100% depending on project requirements. That's not schedule but travel. No standard work hours mentioned. So omit Schedule. Skills: maybe we can extract from qualifications: deep knowledge, demonstrated experience, etc. Could be a Skills section but we already have Qualifications. The instruction says use headings for those categories if content exists. We have Qualifications (list). Could also have Skills but maybe redundant. Prefer few substantive sections over many thin ones. So we can combine qualifications and skills into Qualifications section. About the role: we have a paragraph describing the role: "KPMG is currently seeking a Manager in Customer & Operations for our Consulting practice." plus earlier intro about advisory practice. Could be considered About the role. We'll include a short paragraph summarizing. Responsibilities: list bullet points. Qualifications: list bullet points. Benefits: list bullet points. We must not include boilerplate like EEO, visa sponsorship details? The visa sponsorship statement is substantive: "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)". That's a requirement. Should we include that in Qualifications? Yes, it's a qualification/requirement. So include in Qualifications list. Also mention "KPMG LLP and its affiliates and subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges." That's more about pay transparency, but we omitted Pay. Also mention "Additional details about our benefits can be found towards the bottom of our KPMG US Careers site at Benefits & How We Work." That's a link; we could include in Benefits as a note. We must not include navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove EEO paragraph, "No phone calls or agencies please", "KPMG recruits on a rolling basis", etc. Also remove Los Angeles County specifics? That's a legal requirement; might be considered boilerplate? It's specific to location but still legal. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The Los Angeles County Fair Chance Act is a legal requirement; might be considered EEO-related. Safer to remove that paragraph. 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=M135ADV_3_26". That's pay-related but we omitted Pay section; maybe we could keep as part of Benefits? No, it's pay. Since we omitted Pay, we should not include that link. However the instruction says: never create Pay/Schedule/Benefits sections unless posting actually states them. They did state salary ranges link, but not actual range. It's ambiguous. To be safe, we could include a Pay section with just the link? But that might be considered placeholder? The link is specific. However the rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The link is not filler; it's a URL to salary ranges. So maybe we should include Pay section with that link and a brief note: "See link for salary ranges by city (outside CA)". That is substantive. But we also have a statement: "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." That's also pay-related. Thus we can include Pay section with that sentence and the link. Benefits: we have details. Schedule: we have travel up to 80-100% maybe could be considered Schedule? Not exactly. But we could include Schedule section with travel expectation. However the instruction says use Schedule heading for schedule info. Travel % is not schedule but could be considered work schedule expectation. Might be okay to include Schedule with travel expectation. But we need to avoid filler. Travel up to 80-100% is specific. So we can include Schedule section with that bullet. But we must prefer few substantive sections over many thin ones. We already have About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. That's six sections. Could we combine Pay and Benefits? No, they are distinct headings. Could we drop Schedule and put travel in Qualifications? Travel requirement is more about job demands; could be under Qualifications as a requirement. But the instruction says use headings for those categories if content exists. Travel is not a qualification but a job demand. Could be under Responsibilities? Not really. Might be better to have Schedule. Let's decide: Include About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Now we need to format. Use

for each heading. Use

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

  for prose. We must not repeat job title as heading. We must not include Job ID etc. We must preserve all substantive information. Let's extract substantive content. About the role: The paragraph: "The KPMG Advisory practice is at the forefront of transformation, offering excellent opportunities for individuals to advance their careers and expertise with KPMG. Looking ahead, we anticipate continued evolution and success within the practice, fostering both personal and professional development, thereby creating new pathways for growth. In this ever-changing market environment, our professionals must be adaptable and thrive in a collaborative, team-driven culture. At KPMG, our people are our number one priority. With a wealth of learning and career development opportunities, a world-class training facility, and leading market tools, we help our people continue to grow both professionally and personally. If you're looking for a firm with a strong team connection where you can be your whole self, have an impact, advance your skills, deepen your experiences, and have the flexibility and access to constantly find new areas of inspiration and expand your capabilities, then consider a career in Advisory. KPMG is currently seeking a Manager in Customer & Operations for our Consulting practice." We can condense but must preserve all substantive information; we cannot invent or summarize away detail. However we can keep the prose as is; it's okay to keep it long. It's not boilerplate; it's substantive about the firm and role. So we can put that entire paragraph in

  . Responsibilities: list: - Lead client engagements and work streams related to supply chain strategy and operational improvement projects - Provide oversight of day-to-day project work with highly skilled client and KPMG work teams throughout the project lifecycle - Help ensure timely execution of project deliverables, client work sessions and executive reviews - Lead project teams through strategy definition, operating model design, organization design, network strategy for the supply chain function - Establish client value propositions that tie financial metrics and CFO focus areas directly to operations business improvement - Assist with proposal and business development activities by leveraging existing relationships with C-level executives Qualifications: list: - Minimum five years of recent management consulting experience providing advisory services related to supply chain, cost reduction and operational restructuring with the ability to assess, improve and reconstruct the information, physical and financial flows across the clients supply chain - Bachelor's degree in finance, engineering, operations analysis or a related field from an accredited college/university - Deep knowledge of supply chain strategy, operational excellence, operating model, global network design, supply chain finance - Demonstrated experience developing relationships with senior clients; ability to manage competing priorities and ambiguity - Demonstrated ability to structure compelling analysis - Travel may be up to 80-100% depending on project requirements (maybe move to Schedule) - 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) We could keep travel in Qualifications or Schedule. Let's keep travel in Qualifications for now; we can still have Schedule maybe empty? Better to move travel to Schedule to keep Qualifications focused. But we need to ensure we don't lose info. Let's create Schedule section with travel expectation. Thus Qualifications list excludes travel. Benefits: list: - Comprehensive, competitive benefits package - Medical and dental plans - Vision coverage - Disability and life insurance - 401(k) plans - Robust suite of personal well-being benefits to support mental health - Personal Time Off per fiscal year (based on job classification, standard work hours, and years of service) - Calendar of holidays observed each year - Two breaks each year where employees will not be required to use Personal Time Off (year-end and around July 4th) - Additional details available at Benefits & How We Work on KPMG US Careers site Pay: include: - KPMG complies with local/state regulations regarding displaying salary ranges. - If required, ranges displayed below or via the URL below are for potential hires who will work in the location(s) listed. - See link for salary ranges by city outside of CA: https://kpmg.com/us/en/how-we