Managing Director, Ignition
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real, specific content for it. 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 core content: description of KPMG, the role, responsibilities, qualifications, maybe skills, benefits, pay, schedule.
We need to decide which sections to include.
We have:
- Intro: "Known for being a great place to work and build a career, KPMG provides audit, tax and advisory services..." This is about the company, could be "About the role"? Actually "About the role" is about the job, not company. But we could use "About the role" to include description of role and maybe company context. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role (maybe a brief overview). The posting includes a paragraph about KPMG and then "If you're as passionate about your future as we are, join our team. KPMG is currently seeking a Managing Director to join our Tax Ignition practice." That's about the role. So we can put that in About the role.
Then Responsibilities: we have a long block after "Responsibilities:" with many bullet-like sentences but not bullet list. We need to convert to - . We need to preserve all substantive info. So we need to split each responsibility into separate
- . The responsibilities block includes multiple sentences separated by semicolons? Let's parse:
"Play a key role in developing our Tax Ignition practice by working with clients to understand enterprise operational requirements for tax processes including documenting tax processes and organization, analyzing tax data/calculations/reports and understanding technology environment and interfacesWork with clients to review, assess and redesign internal tax function operations to develop a new operating model; candidates must demonstrate a high-level understanding of: Tax function strategy and design, Service delivery model options and tradeoffs, Organizational design methodologies,Tax technology challenges and available market solutions for a wide variety of scenariosApply financial reporting standards and tax technical guidance to processes and technologyPossess high-level written communication skills and demonstrate an ability to develop effective artifacts that articulate complex problems and solutions in straight forward waysBuild, manage, direct and monitor multiple client engagements teams while maintaining active communication with clients in an effort to manage expectations and help ensure client satisfactionLead, participate in and contribute to market and business development activities external to the firm; including identifying and pursuing new potential client service opportunities by collaborating with KPMGs Audit and Advisory practicesContribute to the growth, experience and institutional knowledge of the Tax Transformation practice staff level team members"
We need to split into separate responsibilities. Likely each sentence separated by a period or semicolon. Let's break:
1. Play a key role in developing our Tax Ignition practice by working with clients to understand enterprise operational requirements for tax processes including documenting tax processes and organization, analyzing tax data/calculations/reports and understanding technology environment and interfaces
2. Work with clients to review, assess and redesign internal tax function operations to develop a new operating model; candidates must demonstrate a high-level understanding of: Tax function strategy and design, Service delivery model options and tradeoffs, Organizational design methodologies, Tax technology challenges and available market solutions for a wide variety of scenarios
3. Apply financial reporting standards and tax technical guidance to processes and technology
4. Possess high-level written communication skills and demonstrate an ability to develop effective artifacts that articulate complex problems and solutions in straight forward ways
5. Build, manage, direct and monitor multiple client engagements teams while maintaining active communication with clients in an effort to manage expectations and help ensure client satisfaction
6. Lead, participate in and contribute to market and business development activities external to the firm; including identifying and pursuing new potential client service opportunities by collaborating with KPMGs Audit and Advisory practices
7. Contribute to the growth, experience and institutional knowledge of the Tax Transformation practice staff level team members
We'll output each as
- .
Next Qualifications: after "Qualifications:" we have list:
- Minimum ten years of recent experience in a combination of corporate tax and tax technology in an audit, tax, or advisory services firm, corporation, or law firm
- Bachelors degree from an accredited college/university and licensed CPA, J.D./LL.M required
- Knowledge of a broad range of corporate tax matters including tax reporting and compliance experience; possess both tax and technology skills
- Demonstrated track record of business development with the ability to develop and maintain existing internal and external client relationships and help build new relationships with key targets
- Demonstrated experience leading multiple engagements and client service teams as well as developing and mentoring staff within a collaborative team environment
- Excellent written and verbal communication skills with the ability to evaluate and articulate complex information
We need to decide if we put these under Qualifications or Requirements or Skills. The headings list includes Requirements, Qualifications, Skills. We need to include sections only when posting has real specific content. We have qualifications list. Could map to Qualifications. Could also separate Requirements (maybe experience and education) and Skills (communication etc). But we have limited time; better to put all under Qualifications as they are qualifications. Or we could split: Requirements (experience, degree) and Skills (communication, business development, etc). But we need to avoid thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into Qualifications (which includes experience, education, skills). That's fine.
Next Benefits: posting mentions benefits: "In addition, 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. 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."
We have specific benefits: medical/dental plans, vision, disability, life insurance, 401(k), personal well-being benefits, PTO, holidays, two breaks. So we can include Benefits section.
Pay: posting includes salary range: "California Salary Range: $257355 - $665735". Also earlier: "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." That's boilerplate but includes salary range info. We need to include Pay section only if posting actually states them. It does state California Salary Range. So we can include Pay with that range. Also there is a link for salary ranges by city outside of CA. But we should not include application instructions or links? The instruction: remove application instructions. The link for salary ranges might be considered metadata but not application instruction. However it's a link to external site for pay transparency. Might be considered part of Pay section? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The link is minor metadata; we could fold into a short
under Pay or drop it. Probably better to include the salary range and maybe note that ranges vary by location and see link. But we should not invent or summarize away detail. We can include the salary range and mention that additional location-based ranges are available via the provided link. That's preserving detail.
Schedule: posting mentions "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year." Also mentions breaks. That's more about benefits than schedule. There's no explicit schedule like full-time, hours per week. So we may not have specific schedule info. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Schedule, we don't have explicit schedule like "standard work hours" but it's mentioned as part of benefits. Might be considered schedule info? It says "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year." That implies standard work hours but not given. Could we create a Schedule section with that? It's vague. Better to omit Schedule section because not specific.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
We need to output HTML fragment only, no /. Use
for each section heading. Use - for lists. Use
for prose.
We need to preserve all substantive info; not remove needed details. Remove boilerplate: EEO, equal opportunity, legal, navigation, cookie, application instructions (like "No phone calls or agencies please", "KPMG recruits on a rolling basis", etc). Also remove duplicated lines.
We need to keep the intro about KPMG and the role. Let's craft About the role paragraph: combine the intro sentences about KPMG being great place to work, providing audit tax advisory, growth driven by delivering results, culture encourages development, inclusive environment, rewards innovative excellence, supports communities, ranked among best companies to work for, and then "If you're as passionate about your future as we are, join our team. KPMG is currently seeking a Managing Director to join our Tax Ignition practice."
We should not include fluff like "Known for being a great place to work and build a career" - that's substantive? It's about company culture; we can keep.
Now Responsibilities: list as above.
Qualifications: list as above.
Benefits: list benefits: 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 (depending on job classification, standard work hours, years of service), calendar of holidays, two breaks each year (year end and around July 4th) where employees will not be required to use PTO.
We could also mention that benefits are based on eligibility.
Pay: include California Salary Range: $257355 - $665735. Also note that salary ranges vary by location and can be viewed via link: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=M322U_0_26 . But we need to decide if we include the link. It's minor metadata; we could fold into a short
under Pay. The instruction: "fold minor metadata into a short
or drop it." So we can include a short
with the link.
We must not include application instructions like "No phone calls or agencies please", "KPMG recruits on a rolling basis", etc. Also remove EEO boilerplate.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
- . We need to preserve all substantive info. So we need to split each responsibility into separate
- . The responsibilities block includes multiple sentences separated by semicolons? Let's parse: "Play a key role in developing our Tax Ignition practice by working with clients to understand enterprise operational requirements for tax processes including documenting tax processes and organization, analyzing tax data/calculations/reports and understanding technology environment and interfacesWork with clients to review, assess and redesign internal tax function operations to develop a new operating model; candidates must demonstrate a high-level understanding of: Tax function strategy and design, Service delivery model options and tradeoffs, Organizational design methodologies,Tax technology challenges and available market solutions for a wide variety of scenariosApply financial reporting standards and tax technical guidance to processes and technologyPossess high-level written communication skills and demonstrate an ability to develop effective artifacts that articulate complex problems and solutions in straight forward waysBuild, manage, direct and monitor multiple client engagements teams while maintaining active communication with clients in an effort to manage expectations and help ensure client satisfactionLead, participate in and contribute to market and business development activities external to the firm; including identifying and pursuing new potential client service opportunities by collaborating with KPMGs Audit and Advisory practicesContribute to the growth, experience and institutional knowledge of the Tax Transformation practice staff level team members" We need to split into separate responsibilities. Likely each sentence separated by a period or semicolon. Let's break: 1. Play a key role in developing our Tax Ignition practice by working with clients to understand enterprise operational requirements for tax processes including documenting tax processes and organization, analyzing tax data/calculations/reports and understanding technology environment and interfaces 2. Work with clients to review, assess and redesign internal tax function operations to develop a new operating model; candidates must demonstrate a high-level understanding of: Tax function strategy and design, Service delivery model options and tradeoffs, Organizational design methodologies, Tax technology challenges and available market solutions for a wide variety of scenarios 3. Apply financial reporting standards and tax technical guidance to processes and technology 4. Possess high-level written communication skills and demonstrate an ability to develop effective artifacts that articulate complex problems and solutions in straight forward ways 5. Build, manage, direct and monitor multiple client engagements teams while maintaining active communication with clients in an effort to manage expectations and help ensure client satisfaction 6. Lead, participate in and contribute to market and business development activities external to the firm; including identifying and pursuing new potential client service opportunities by collaborating with KPMGs Audit and Advisory practices 7. Contribute to the growth, experience and institutional knowledge of the Tax Transformation practice staff level team members We'll output each as
- .
Next Qualifications: after "Qualifications:" we have list:
- Minimum ten years of recent experience in a combination of corporate tax and tax technology in an audit, tax, or advisory services firm, corporation, or law firm
- Bachelors degree from an accredited college/university and licensed CPA, J.D./LL.M required
- Knowledge of a broad range of corporate tax matters including tax reporting and compliance experience; possess both tax and technology skills
- Demonstrated track record of business development with the ability to develop and maintain existing internal and external client relationships and help build new relationships with key targets
- Demonstrated experience leading multiple engagements and client service teams as well as developing and mentoring staff within a collaborative team environment
- Excellent written and verbal communication skills with the ability to evaluate and articulate complex information
We need to decide if we put these under Qualifications or Requirements or Skills. The headings list includes Requirements, Qualifications, Skills. We need to include sections only when posting has real specific content. We have qualifications list. Could map to Qualifications. Could also separate Requirements (maybe experience and education) and Skills (communication etc). But we have limited time; better to put all under Qualifications as they are qualifications. Or we could split: Requirements (experience, degree) and Skills (communication, business development, etc). But we need to avoid thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into Qualifications (which includes experience, education, skills). That's fine.
Next Benefits: posting mentions benefits: "In addition, 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. 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."
We have specific benefits: medical/dental plans, vision, disability, life insurance, 401(k), personal well-being benefits, PTO, holidays, two breaks. So we can include Benefits section.
Pay: posting includes salary range: "California Salary Range: $257355 - $665735". Also earlier: "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." That's boilerplate but includes salary range info. We need to include Pay section only if posting actually states them. It does state California Salary Range. So we can include Pay with that range. Also there is a link for salary ranges by city outside of CA. But we should not include application instructions or links? The instruction: remove application instructions. The link for salary ranges might be considered metadata but not application instruction. However it's a link to external site for pay transparency. Might be considered part of Pay section? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The link is minor metadata; we could fold into a short
under Pay or drop it. Probably better to include the salary range and maybe note that ranges vary by location and see link. But we should not invent or summarize away detail. We can include the salary range and mention that additional location-based ranges are available via the provided link. That's preserving detail. Schedule: posting mentions "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year." Also mentions breaks. That's more about benefits than schedule. There's no explicit schedule like full-time, hours per week. So we may not have specific schedule info. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Schedule, we don't have explicit schedule like "standard work hours" but it's mentioned as part of benefits. Might be considered schedule info? It says "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year." That implies standard work hours but not given. Could we create a Schedule section with that? It's vague. Better to omit Schedule section because not specific. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to output HTML fragment only, no /. Use
for each section heading. Use
- for lists. Use
for prose. We need to preserve all substantive info; not remove needed details. Remove boilerplate: EEO, equal opportunity, legal, navigation, cookie, application instructions (like "No phone calls or agencies please", "KPMG recruits on a rolling basis", etc). Also remove duplicated lines. We need to keep the intro about KPMG and the role. Let's craft About the role paragraph: combine the intro sentences about KPMG being great place to work, providing audit tax advisory, growth driven by delivering results, culture encourages development, inclusive environment, rewards innovative excellence, supports communities, ranked among best companies to work for, and then "If you're as passionate about your future as we are, join our team. KPMG is currently seeking a Managing Director to join our Tax Ignition practice." We should not include fluff like "Known for being a great place to work and build a career" - that's substantive? It's about company culture; we can keep. Now Responsibilities: list as above. Qualifications: list as above. Benefits: list benefits: 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 (depending on job classification, standard work hours, years of service), calendar of holidays, two breaks each year (year end and around July 4th) where employees will not be required to use PTO. We could also mention that benefits are based on eligibility. Pay: include California Salary Range: $257355 - $665735. Also note that salary ranges vary by location and can be viewed via link: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=M322U_0_26 . But we need to decide if we include the link. It's minor metadata; we could fold into a short
under Pay. The instruction: "fold minor metadata into a short
or drop it." So we can include a short
with the link. We must not include application instructions like "No phone calls or agencies please", "KPMG recruits on a rolling basis", etc. Also remove EEO boilerplate. Now produce HTML. Structure:
About the role
...
Responsibilities
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
- for lists. Use