Senior Manager, Sales & Use Tax
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info.
Let's parse the posting.
First paragraph: "At KPMG, you can become an integral part of a dynamic team at one of the worlds top tax firms. Enjoy a collaborative, future-forward culture that empowers your success. Work with KPMGs extensive network of specialists; enjoy access to our Ignition Centers, where deep industry knowledge merges with cutting-edge technologies to create innovative tax solutions. Join a diverse team helping high-profile clients understand, analyze, and respond to complex business opportunities and challenges. Develop your career through a range of multifaceted engagements, formal training, and informal mentoring. At KPMG, we believe nothing is more important than investing in our culture because it is an investment in our people, our future, and what we stand for as a firm."
That's about the role/company. Could be "About the role" or "About KPMG". We'll use "About the role". It's substantive.
Then: "KPMG is currently seeking a Senior Manager to join our State and Local Tax (SALT) practice." That's also part of about.
Then "Responsibilities:" list.
Responsibilities bullet points:
- Provide excellent client service to multi-state companies with state and local sales/use tax issues including reverse audits, compliance, tax planning, automation technology, research and writing, multi-jurisdictional reporting, and controversies/audit defense
- Partner with multi-state companies in analyzing state tax considerations/impacts related to business restructuring projects and intercompany transactions
- Work with multi-state companies in state and local tax (SALT) controversies, which includes preparing clients for discussions with auditors, representing the client at hearings and at appeal meetings, and preparing protests
- Supervise, mentor and develop staff members
- Participate in the business development, management and delivery of SALT services
These are duties; we should put under Responsibilities
with - .
Then "Qualifications:" heading.
Qualifications bullet points (actually they list multiple items):
- Minimum eight years of recent experience in providing tax research and technical advice on multi-state issues
- Bachelor's degree from an accredited college/university or twenty years of work experience at a professional services firm or similar industry providing tax compliance, research, and/or technical or regulatory advice on multi-state issues to include sales and use, excise, severance or other types of indirect taxes for a corporate, public accounting, consulting or government entity; licensed CPA, EA, JD/LLM, MST (Master's in Taxation) or a certified member of the Institute for Professionals in Taxation (CMI) designation for non-CPA eligible candidates, in addition to others on KPMG's approved credential listing; any individual who does not possess at least one of the approved designations/credentials when their employment commences, has one year from their date of hire to obtain at least one of the approved designations/credentials; should you like to see the complete list of currently approved designations/credentials for the hiring practice/service line, your recruiter can provide you with that list
- Strong knowledge of the development, planning and execution of sales and transactions tax refund claims
- Experience with various other corporate taxes and their impact on sales tax
We need to decide sections: "Qualifications" and maybe "Requirements". The posting uses "Qualifications:" heading. There's no separate "Requirements". We could treat "Qualifications" as the requirements. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only if there is real specific content. We have qualifications content. Could also split into "Requirements" (experience, education) and "Qualifications" (certifications). But better to follow the posting: use "Qualifications". Could also add "Skills" if there are skill-specific items like "Strong knowledge..." and "Experience with various other corporate taxes...". Those could be considered skills. But we can keep them under Qualifications.
Benefits: The 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."
That's substantive benefits info. So we should include a Benefits section.
Pay: The posting mentions 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." Then a link. It does not give actual numbers, just says they comply and provide a link. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that they comply and provide a link, but does not give actual salary 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." There's no actual range displayed in the text. It mentions a link. Is that enough to consider Pay section? The instruction says: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The text does not give a range; it's basically saying they will display ranges if required, and provides a link. That's somewhat placeholder. I'd argue we should not create a Pay section because there is no specific salary range. The instruction says only create Pay section if posting actually states them. It does not state a specific range; it's a generic statement. So we should omit Pay.
Schedule: The posting mentions standard work hours, Personal Time Off, holidays, breaks. That is schedule-related info. It says: "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 can include a Schedule section.
We also have "About the role" section.
We need to avoid boilerplate: EEO, equal opportunity, scam warning, navigation, cookie, legal, etc. Remove those paragraphs.
We must preserve all substantive information. So we need to keep the benefits details, schedule details, qualifications, responsibilities, about.
We must not repeat job title as heading. The job title is Senior Manager; we should not add a heading for it.
We must not put Job ID/requisition numbers as headings; none present.
We must output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
About the role
... (the about paragraph(s) combined)
Responsibilities
- ...
...
Qualifications
- ...
...
Benefits
... (benefits paragraph)
Schedule
... (schedule paragraph)
Check if any other sections like Skills: we could embed skills within Qualifications. Not needed.
Now we need to ensure we preserve all substantive info from the posting, but we removed boilerplate like EEO, etc. Let's extract substantive pieces.
About the role paragraph: The first big paragraph up to "KPMG is currently seeking a Senior Manager to join our State and Local Tax (SALT) practice." That's all substantive.
We could split into two paragraphs but one is fine.
Responsibilities: list as above.
Qualifications: we need to capture each bullet.
Let's extract qualifications bullet points exactly as in text:
- Minimum eight years of recent experience in providing tax research and technical advice on multi-state issues
- Bachelor's degree from an accredited college/university or twenty years of work experience at a professional services firm or similar industry providing tax compliance, research, and/or technical or regulatory advice on multi-state issues to include sales and use, excise, severance or other types of indirect taxes for a corporate, public accounting, consulting or government entity; licensed CPA, EA, JD/LLM, MST (Master's in Taxation) or a certified member of the Institute for Professionals in Taxation (CMI) designation for non-CPA eligible candidates, in addition to others on KPMG's approved credential listing; any individual who does not possess at least one of the approved designations/credentials when their employment commences, has one year from their date of hire to obtain at least one of the approved designations/credentials; should you like to see the complete list of currently approved designations/credentials for the hiring practice/service line, your recruiter can provide you with that list
- Strong knowledge of the development, planning and execution of sales and transactions tax refund claims
- Experience with various other corporate taxes and their impact on sales tax
We should keep them as
- items.
Benefits: The paragraph: "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 could split into two paragraphs but one
is fine.
Schedule: Actually the benefits paragraph already includes schedule info (Personal Time Off, holidays, breaks). The instruction says to create Schedule section only if posting actually states them. The schedule info is present within benefits paragraph. But we could still create a Schedule section with that info. However we risk duplicating content. The instruction says preserve ALL substantive information; do not invent or summarize away detail. If we put schedule info only in Benefits section, that's fine; we don't need a separate Schedule section unless we want to separate. But we could create a Schedule section with the same info; that would be duplication but not invented. However the instruction says "Prefer a few substantive sections over many thin ones." So better to keep schedule info within Benefits, not create a separate Schedule section unless there is distinct schedule info beyond benefits. The benefits paragraph already includes schedule info; we could keep it there and not create a Schedule section. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule info (Personal Time Off, holidays,
About the role
... (the about paragraph(s) combined)
Responsibilities
- ... ...
Qualifications
- ... ...
Benefits
... (benefits paragraph)
Schedule
... (schedule paragraph)
Check if any other sections like Skills: we could embed skills within Qualifications. Not needed. Now we need to ensure we preserve all substantive info from the posting, but we removed boilerplate like EEO, etc. Let's extract substantive pieces. About the role paragraph: The first big paragraph up to "KPMG is currently seeking a Senior Manager to join our State and Local Tax (SALT) practice." That's all substantive. We could split into two paragraphs but oneis fine. Responsibilities: list as above. Qualifications: we need to capture each bullet. Let's extract qualifications bullet points exactly as in text: - Minimum eight years of recent experience in providing tax research and technical advice on multi-state issues - Bachelor's degree from an accredited college/university or twenty years of work experience at a professional services firm or similar industry providing tax compliance, research, and/or technical or regulatory advice on multi-state issues to include sales and use, excise, severance or other types of indirect taxes for a corporate, public accounting, consulting or government entity; licensed CPA, EA, JD/LLM, MST (Master's in Taxation) or a certified member of the Institute for Professionals in Taxation (CMI) designation for non-CPA eligible candidates, in addition to others on KPMG's approved credential listing; any individual who does not possess at least one of the approved designations/credentials when their employment commences, has one year from their date of hire to obtain at least one of the approved designations/credentials; should you like to see the complete list of currently approved designations/credentials for the hiring practice/service line, your recruiter can provide you with that list - Strong knowledge of the development, planning and execution of sales and transactions tax refund claims - Experience with various other corporate taxes and their impact on sales tax We should keep them as
is fine. Schedule: Actually the benefits paragraph already includes schedule info (Personal Time Off, holidays, breaks). The instruction says to create Schedule section only if posting actually states them. The schedule info is present within benefits paragraph. But we could still create a Schedule section with that info. However we risk duplicating content. The instruction says preserve ALL substantive information; do not invent or summarize away detail. If we put schedule info only in Benefits section, that's fine; we don't need a separate Schedule section unless we want to separate. But we could create a Schedule section with the same info; that would be duplication but not invented. However the instruction says "Prefer a few substantive sections over many thin ones." So better to keep schedule info within Benefits, not create a separate Schedule section unless there is distinct schedule info beyond benefits. The benefits paragraph already includes schedule info; we could keep it there and not create a Schedule section. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule info (Personal Time Off, holidays,