Director, Supply Chain Manufacturing

We need to output HTML fragment with sections: About the role? The posting includes introductory paragraphs about KPMG Advisory practice, then "KPMG is currently seeking a Director in Supply Chain for our Consulting practice." That's the role description. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real, specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. We need to keep the content: responsibilities list, qualifications list, benefits description, maybe pay? There's a mention of salary ranges: "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." This is generic but does not give actual numbers. It says they comply with displaying salary ranges, but no actual range given. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, they do state benefits: "In addition, KPMG is proud to offer a comprehensive, competitive benefits package... Available benefits are based on eligibility. 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. 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. Additional details about our benefits can be found towards the bottom of our KPMG US Careers site at Benefits & How We Work." That's substantive benefits content. So we should include Benefits section. Pay: they mention salary ranges but not actual numbers; they say they comply with displaying salary ranges, provide a link. The instruction: never emit a 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 the posting actually states them. The posting does not state an actual salary range; it just says they comply and provide a link. That might be considered filler? It's not a specific range. 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." No actual ranges displayed. So we should not create a Pay section. Schedule: they mention standard work hours, personal time off, holidays, breaks. That's schedule-related info. They say "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." That's schedule info (time off, holidays). So we could include a Schedule section with that content. However, the instruction: "Prefer a few substantive sections over many thin ones." We could combine Benefits and Schedule? But they are separate headings allowed. We could include both if they have substantive content. The schedule info is about PTO, holidays, breaks. That's substantive. So include Schedule. We also need About the role section: we have introductory paragraphs describing the role and the practice. That's substantive. We'll put that in About the role. Responsibilities: we have a list after "Responsibilities:" with multiple items separated by line breaks. We'll turn each into

. Qualifications: after "Qualifications:" we have bullet-like sentences. We'll turn each into

. Skills: The posting does not have a separate Skills section; qualifications include skills. We could either not include Skills section (since no explicit Skills heading). The instruction: include a section ONLY when the posting has real, specific content for it. There's no explicit Skills section, but we could infer skills from qualifications. However, better to not create a Skills section unless there is explicit content. So we omit Skills. We need to remove boilerplate: EEO, equal opportunity, legal, visa sponsorship details? The visa sponsorship info is part of qualifications? It says "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 qualification (work authorization). Should we keep it? It's substantive info about eligibility. It's part of qualifications. We'll keep as a qualification item. We must remove duplicated lines, application instructions, etc. Also remove the line about "KPMG offers a comprehensive compensation and benefits package." That's duplicate of benefits. We'll keep benefits content but not duplicate. We must remove the EEO boilerplate at the end, the "No phone calls or agencies please", "KPMG recruits on a rolling basis", etc. Also remove the Los Angeles County Fair Chance Act details (that's legal). Also remove the link to salary ranges (maybe keep as part of benefits? It's about pay transparency; but we are not including Pay section. Could we include a link in Benefits? Probably not needed. We'll remove. We must preserve all substantive information: responsibilities, qualifications, benefits, schedule (PTO, holidays, breaks), about the role. Now craft HTML. Structure:

About the role

... (intro paragraphs)

Responsibilities

• Drive engagement delivery and lead key business development activities for our supply chain advisory services including targeting key C- level clients, proposing our services and closing opportunities
• Lead/co-lead highly skilled client and KPMG work teams throughout the project lifecycle by leveraging our supply chain approaches/frameworks and ensuring timely execution of project deliverables
• Manage and execute end to end supply chain planning related to manufacturing at multiple US and International sites
• Lead on-site project teams in the execution of complex material movement and flow
• Assist Partners with practice administration including resource allocation, career development of staff and other people management decisions

Qualifications

• Minimum eight years of recent experience in leading complex Supply Chain projects and teams with a particular focus on Manufacturing including Tier 1 Suppliers and local OEM
• Bachelor's degree from an accredited college/university in finance, engineering, operations research, or a related field; MBA/MS from an accredited college/university preferred
• Previously responsible for the complex management and movement of materials
• Have deep experience with industrial materials management in the supply chain eco system
• Prior industry experience in industrial or automotive manufacturing
• Ability to travel up to 80%
• 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

• Comprehensive, competitive benefits package with options designed to help you make the best decisions for yourself, your family, and your lifestyle
• 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
• Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year
• 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
• Additional details about our benefits can be found towards the bottom of our KPMG US Careers site at Benefits & How We Work

But note that some of the benefits items overlap with schedule (PTO, holidays, breaks). We could keep them in Benefits, and maybe not have a separate Schedule section. However, the instruction says we can include Schedule section if posting actually states them. The posting does state schedule-related info (standard work hours, PTO, holidays, breaks). That is substantive. We could either put them under Benefits or Schedule. Since we already have Benefits section with those items, we could keep them there and not create a separate Schedule section to avoid duplication. But we need to ensure we don't lose any info. The benefits section currently includes PTO, holidays, breaks. That's fine. We should also include the line about "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year." That's already in benefits. Thus we may not need a separate Schedule section. We need to ensure we didn't include any boilerplate like "KPMG is an equal opportunity employer." We removed that. Check for any leftover boilerplate: The paragraph about "KPMG LLP and its affiliates and subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges..." we removed because it's not specific salary range. Good. We also removed the link to salary ranges. We removed the "KPMG offers a comprehensive compensation and benefits package." duplicate. We removed the EEO paragraph. We removed the "No phone calls or agencies please." etc. We removed the Los Angeles County Fair Chance Act details. We removed the "KPMG recruits on a rolling basis." etc. We removed the "Follow this link to obtain salary ranges by city outside of CA:" etc. Now ensure we didn't miss any substantive info: The intro paragraphs about KPMG Advisory practice, transformation, etc. That's about the role. We'll include that. Check if any other responsibilities: The responsibilities list we captured exactly as in text. Ensure we didn't miss any punctuation. The original: "Drive engagement delivery and lead key business development activities for our supply chain advisory services including targeting key C- level clients, proposing our services and closing opportunities Lead/co-lead highly skilled client and KPMG work teams throughout the project lifecycle by leveraging our supply chain approaches/frameworks and ensuring timely execution of project deliverablesManage and execute end to end supply chain planning related to manufacturing at multiple US and International sitesLead on-site project teams in the execution of complex material movement and flowAssist Partners with practice administration including resource allocation, career development of staff and other people management decisions". There are missing spaces after periods. We'll keep as is but maybe add spaces for readability? We must preserve ALL substantive information; we can fix formatting? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Changing punctuation might be considered altering detail? Probably okay to add spaces for readability as it doesn't change meaning. But safer to keep exactly as given? The original had no spaces after periods; we could keep that but it's ugly. However,