Tax Manager - Corporate Taxes
for section headings
- Use - for lists
- Use
for prose
- Don't repeat job title as heading
- Don't put Job ID/requisition as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions)
- Include section ONLY when real specific content exists
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment, no html/body, no markdown fences
Let me parse the content:
Job Summary: There's a paragraph describing the role.
Job Duties: List of bullet points (though they're not formatted as bullets in the text, they're separate lines). I'll make them a list.
Supervisory Responsibilities: One line about supervising Senior Tax Accountants.
Qualifications: Has subsections:
- Education: Bachelor's required, Master's preferred
- Experience: 6+ years, specific experience required/preferred
- License/Certification: CPA or EA preferred
- Software: Expert in MS Office, OneSource/CorpTax required, Oracle/OneStream preferred
- Language: N/A (should I include? It says N/A, so maybe skip or mention not required)
- Other Knowledge, Skills & Abilities: List of abilities
Pay: National Range and specific ranges for Maryland and NYC/Long Island/Westchester. This is real pay info, so include Pay section.
About Us: Describes BDO, mentions ESOP, Total Rewards benefits, but the benefits details are behind a link. The posting says "Learn more about our benefits: BDO Total Rewards encompass more than traditional benefits. Click here to find out more!" and "Benefits may be subject to eligibility requirements." This is somewhat boilerplate but does mention ESOP and Total Rewards. However, the rule says "never create Benefits sections unless the posting actually states them." It does state benefits in a general way, but not specific benefits. I think I should include an "About Us" section with the company description, and maybe a "Benefits" section if there's substantive content. The posting mentions ESOP and Total Rewards, but no specifics. The rule says "never emit a heading followed by filler/placeholder text". Since it's just a reference to a link, maybe I should include the About Us as a section but not a separate Benefits section. Or include Benefits with the ESOP mention. Let me see: "We are proud to be an ESOP company, offering participants a stake in the firm's success through beneficial ownership and a unique opportunity to enhance their financial well-being. As a qualified retirement plan, the ESOP is a meaningful addition to our comprehensive compensation and Total Rewards benefits* offerings." That's substantive about ESOP. But the rest is boilerplate. I'll include an "About Us" section with the company description and ESOP mention. I'll not create a separate Benefits section because the details are not listed.
Also need to remove EEO boilerplate at the end.
Now structure:
About the role
Job Summary paragraph
Responsibilities
- each duty
Supervisory responsibilities
Supervises a team of Senior Tax Accountants
Qualifications
Then subsections? The rule says use for section headings. Should I use for each qualification subsection? The example headings include "Qualifications" as a heading. I think I should have a main Qualifications heading, then maybe use ? But the rule says use for section headings. It doesn't mention subheadings. I could make each qualification category an ? That might be too many. Better to have one Qualifications section with sub-lists. But the content has distinct categories. I'll use for each category: Education, Experience, Licenses & certifications, Software, Other knowledge, skills & abilities. However, the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So Qualifications is a section heading. I'll make Qualifications an and then within it, use ? But the output is HTML fragment, and they didn't forbid h4. But they said use for section headings. I think it's okay to use for each major section, and for subsections maybe use or just bold text. However, to keep it simple and semantic, I'll make each qualification category an ? That would be many h3s. Let's see the example: they list "Qualifications" as a heading. I'll treat the whole qualifications block as one section with subsections using or just
with strong. But the rule says "use
for section headings". It doesn't say you can't use h4. I'll use h3 for main sections, and for subsections I'll use (since it's still a heading). But the instruction says "Output ONLY the HTML fragment". I'll assume standard HTML is fine.
Alternatively, I can make a single Qualifications section with a list of categories, each category as a sublist. But the content is detailed. I'll do:
Qualifications
Education
- ...
Experience
- ...
etc.
But the rule didn't mention h4. However, it's semantic HTML. I think it's acceptable.
Now Pay section: include the ranges.
About Us section: include the company description.
Now, ensure no boilerplate: remove EEO, equal opportunity, scam warnings, application instructions (none here), duplicated lines.
Let's write the HTML.
First, About the role:
About the role
As part of Corporate Finance, the Tax Manager, Provision & Federal Taxes joins an expanding team focused on providing tax compliance and tax planning for the organization. Specifically, this individual is responsible for coordinating the annual tax provision process and leading the preparation of BDO USA, P.C. and its affiliates federal tax returns. The Tax Manager, Provision & Federal Taxes is also responsible for reviewing tax workpapers and returns prepared by the tax staff. The role includes facilitating tax projections for federal, state, and local income tax estimated payments, extensions, and budgets. Working through periodic federal income tax audits with a view towards obtaining no change results is another aspect of this role.
Responsibilities: list each duty. The duties are listed as separate lines. I'll make them list items.
Responsibilities
- Acts as the lead over the company's tax provision process and coordinating the plan to prepare for and execute various tax projects within the tax department from beginning to end
- Oversees the process of gathering the necessary data and information to prepare the corporate federal tax return
- Leads the federal tax return preparation process using OneSource OIT or CorpTax
- Coordinates the quarterly tax projections for federal, state, and local income tax estimated payments and tax extensions processes
- Demonstrates the ability to research complex tax questions, communicate findings effectively, and implement results on various income tax returns
- Assists in setting up and computing the US income tax provision and drafts the financial tax footnote disclosures, while assisting in the correspondence and support with external auditors
- Acts as the primary contact for federal tax audits
- Oversees and approves the reconciliation of various tax accounts within the general ledger and coordinates the associated JEs within the month end close process with the Senior Tax Accountants
- Drives the process in getting the associated tax expense for budget purposes
- Demonstrates the understanding and ability to execute the "BDO" Tax Manager Competencies
- Other duties as required
Supervisory responsibilities:
Supervisory responsibilities
Supervises a team of Senior Tax Accountants.
Qualifications:
Qualifications
Education
- Bachelor's degree required; focus in Accounting, Taxation, or Finance preferred
- Master's degree in Accounting or Taxation preferred
Experience
- Six (6) or more years of experience in public accounting tax team or a corporate tax department required
- Experience preparing Federal and State tax yearly tax provisions required
- Experience preparing Federal and State corporate income tax returns required
- Exposure to multi-state and international tax preparation preferred
Licenses & certifications
- CPA or Enrolled Agent (EA) preferred
Software
- Expert in the use of Microsoft Office Suite, specifically Excel and Word required
- Experience utilizing OneSource (OIT & OPT) or other CorpTax income tax software required
- Experience utilizing Oracle and OneStream or similar general ledger and consolidation tools preferred
Other knowledge, skills & abilities
- Ability to lead the execution of tax projects with limited supervision
- Superior customer service skills
- Ability to maintain the highly confidential nature of BDO USA's activities as they relate to associated taxes positions
- Capable of working and communicating effectively with professionals at all levels within BDO USA
- Ability to work in a deadline-driven environment, and handle multiple projects/tasks with an attention to detail
- Ability to successfully multi-task while leading and overseeing within a group environment
- Deep knowledge of federal and state income taxation and the management of fixed assets
- Strong verbal and written communication skills
- Excellent organizational and time management skills
Pay:
Pay
Individual salaries are determined after consideration of numerous factors including but not limited to the candidate's qualifications, experience, skills, and geography.
- National Range: $125,000 - $145,000
- Maryland Range: $125,000 - $145,000
- NYC/Long Island/Westchester Range: $125,000 - $145,000
About Us:
About us
At BDO, how we show up matters. We build strong relationships by supporting one another, our clients, and our communities with care, curiosity, and a commitment to helping one another grow and succeed. Here, you'll find meaningful work, leaders invested in your success, and opportunities to build a career around what matters most to you. Our purpose is to be the people our
for prose - Don't repeat job title as heading - Don't put Job ID/requisition as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no html/body, no markdown fences Let me parse the content: Job Summary: There's a paragraph describing the role. Job Duties: List of bullet points (though they're not formatted as bullets in the text, they're separate lines). I'll make them a list. Supervisory Responsibilities: One line about supervising Senior Tax Accountants. Qualifications: Has subsections: - Education: Bachelor's required, Master's preferred - Experience: 6+ years, specific experience required/preferred - License/Certification: CPA or EA preferred - Software: Expert in MS Office, OneSource/CorpTax required, Oracle/OneStream preferred - Language: N/A (should I include? It says N/A, so maybe skip or mention not required) - Other Knowledge, Skills & Abilities: List of abilities Pay: National Range and specific ranges for Maryland and NYC/Long Island/Westchester. This is real pay info, so include Pay section. About Us: Describes BDO, mentions ESOP, Total Rewards benefits, but the benefits details are behind a link. The posting says "Learn more about our benefits: BDO Total Rewards encompass more than traditional benefits. Click here to find out more!" and "Benefits may be subject to eligibility requirements." This is somewhat boilerplate but does mention ESOP and Total Rewards. However, the rule says "never create Benefits sections unless the posting actually states them." It does state benefits in a general way, but not specific benefits. I think I should include an "About Us" section with the company description, and maybe a "Benefits" section if there's substantive content. The posting mentions ESOP and Total Rewards, but no specifics. The rule says "never emit a heading followed by filler/placeholder text". Since it's just a reference to a link, maybe I should include the About Us as a section but not a separate Benefits section. Or include Benefits with the ESOP mention. Let me see: "We are proud to be an ESOP company, offering participants a stake in the firm's success through beneficial ownership and a unique opportunity to enhance their financial well-being. As a qualified retirement plan, the ESOP is a meaningful addition to our comprehensive compensation and Total Rewards benefits* offerings." That's substantive about ESOP. But the rest is boilerplate. I'll include an "About Us" section with the company description and ESOP mention. I'll not create a separate Benefits section because the details are not listed. Also need to remove EEO boilerplate at the end. Now structure:
About the role
Job Summary paragraph
Responsibilities
- each duty
Supervisory responsibilities
Supervises a team of Senior Tax Accountants
Qualifications
Then subsections? The rule says use for section headings. Should I use for each qualification subsection? The example headings include "Qualifications" as a heading. I think I should have a main Qualifications heading, then maybe use ? But the rule says use for section headings. It doesn't mention subheadings. I could make each qualification category an ? That might be too many. Better to have one Qualifications section with sub-lists. But the content has distinct categories. I'll use for each category: Education, Experience, Licenses & certifications, Software, Other knowledge, skills & abilities. However, the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So Qualifications is a section heading. I'll make Qualifications an and then within it, use ? But the output is HTML fragment, and they didn't forbid h4. But they said use for section headings. I think it's okay to use for each major section, and for subsections maybe use or just bold text. However, to keep it simple and semantic, I'll make each qualification category an ? That would be many h3s. Let's see the example: they list "Qualifications" as a heading. I'll treat the whole qualifications block as one section with subsections using or just
? But the rule says use for section headings. It doesn't mention subheadings. I could make each qualification category an ? That might be too many. Better to have one Qualifications section with sub-lists. But the content has distinct categories. I'll use for each category: Education, Experience, Licenses & certifications, Software, Other knowledge, skills & abilities. However, the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So Qualifications is a section heading. I'll make Qualifications an and then within it, use ? But the output is HTML fragment, and they didn't forbid h4. But they said use for section headings. I think it's okay to use for each major section, and for subsections maybe use or just bold text. However, to keep it simple and semantic, I'll make each qualification category an ? That would be many h3s. Let's see the example: they list "Qualifications" as a heading. I'll treat the whole qualifications block as one section with subsections using or just
? That might be too many. Better to have one Qualifications section with sub-lists. But the content has distinct categories. I'll use for each category: Education, Experience, Licenses & certifications, Software, Other knowledge, skills & abilities. However, the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So Qualifications is a section heading. I'll make Qualifications an and then within it, use ? But the output is HTML fragment, and they didn't forbid h4. But they said use for section headings. I think it's okay to use for each major section, and for subsections maybe use or just bold text. However, to keep it simple and semantic, I'll make each qualification category an ? That would be many h3s. Let's see the example: they list "Qualifications" as a heading. I'll treat the whole qualifications block as one section with subsections using or just
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So Qualifications is a section heading. I'll make Qualifications an and then within it, use ? But the output is HTML fragment, and they didn't forbid h4. But they said use for section headings. I think it's okay to use for each major section, and for subsections maybe use or just bold text. However, to keep it simple and semantic, I'll make each qualification category an ? That would be many h3s. Let's see the example: they list "Qualifications" as a heading. I'll treat the whole qualifications block as one section with subsections using or just
? But the output is HTML fragment, and they didn't forbid h4. But they said use for section headings. I think it's okay to use for each major section, and for subsections maybe use or just bold text. However, to keep it simple and semantic, I'll make each qualification category an ? That would be many h3s. Let's see the example: they list "Qualifications" as a heading. I'll treat the whole qualifications block as one section with subsections using or just
for each major section, and for subsections maybe use or just bold text. However, to keep it simple and semantic, I'll make each qualification category an ? That would be many h3s. Let's see the example: they list "Qualifications" as a heading. I'll treat the whole qualifications block as one section with subsections using or just
? That would be many h3s. Let's see the example: they list "Qualifications" as a heading. I'll treat the whole qualifications block as one section with subsections using or just
with strong. But the rule says "use
for section headings". It doesn't say you can't use h4. I'll use h3 for main sections, and for subsections I'll use (since it's still a heading). But the instruction says "Output ONLY the HTML fragment". I'll assume standard HTML is fine.
Alternatively, I can make a single Qualifications section with a list of categories, each category as a sublist. But the content is detailed. I'll do:
Qualifications
Education
- ...
Experience
- ...
etc.
But the rule didn't mention h4. However, it's semantic HTML. I think it's acceptable.
Now Pay section: include the ranges.
About Us section: include the company description.
Now, ensure no boilerplate: remove EEO, equal opportunity, scam warnings, application instructions (none here), duplicated lines.
Let's write the HTML.
First, About the role:
About the role
Qualifications
Education
- ...
Experience
- ...
About the role
As part of Corporate Finance, the Tax Manager, Provision & Federal Taxes joins an expanding team focused on providing tax compliance and tax planning for the organization. Specifically, this individual is responsible for coordinating the annual tax provision process and leading the preparation of BDO USA, P.C. and its affiliates federal tax returns. The Tax Manager, Provision & Federal Taxes is also responsible for reviewing tax workpapers and returns prepared by the tax staff. The role includes facilitating tax projections for federal, state, and local income tax estimated payments, extensions, and budgets. Working through periodic federal income tax audits with a view towards obtaining no change results is another aspect of this role.
Responsibilities: list each duty. The duties are listed as separate lines. I'll make them list items.Responsibilities
- Acts as the lead over the company's tax provision process and coordinating the plan to prepare for and execute various tax projects within the tax department from beginning to end
- Oversees the process of gathering the necessary data and information to prepare the corporate federal tax return
- Leads the federal tax return preparation process using OneSource OIT or CorpTax
- Coordinates the quarterly tax projections for federal, state, and local income tax estimated payments and tax extensions processes
- Demonstrates the ability to research complex tax questions, communicate findings effectively, and implement results on various income tax returns
- Assists in setting up and computing the US income tax provision and drafts the financial tax footnote disclosures, while assisting in the correspondence and support with external auditors
- Acts as the primary contact for federal tax audits
- Oversees and approves the reconciliation of various tax accounts within the general ledger and coordinates the associated JEs within the month end close process with the Senior Tax Accountants
- Drives the process in getting the associated tax expense for budget purposes
- Demonstrates the understanding and ability to execute the "BDO" Tax Manager Competencies
- Other duties as required
Supervisory responsibilities
Supervises a team of Senior Tax Accountants.
Qualifications:Qualifications
Education
- Bachelor's degree required; focus in Accounting, Taxation, or Finance preferred
- Master's degree in Accounting or Taxation preferred
Experience
- Six (6) or more years of experience in public accounting tax team or a corporate tax department required
- Experience preparing Federal and State tax yearly tax provisions required
- Experience preparing Federal and State corporate income tax returns required
- Exposure to multi-state and international tax preparation preferred
Licenses & certifications
- CPA or Enrolled Agent (EA) preferred
Software
- Expert in the use of Microsoft Office Suite, specifically Excel and Word required
- Experience utilizing OneSource (OIT & OPT) or other CorpTax income tax software required
- Experience utilizing Oracle and OneStream or similar general ledger and consolidation tools preferred
Other knowledge, skills & abilities
- Ability to lead the execution of tax projects with limited supervision
- Superior customer service skills
- Ability to maintain the highly confidential nature of BDO USA's activities as they relate to associated taxes positions
- Capable of working and communicating effectively with professionals at all levels within BDO USA
- Ability to work in a deadline-driven environment, and handle multiple projects/tasks with an attention to detail
- Ability to successfully multi-task while leading and overseeing within a group environment
- Deep knowledge of federal and state income taxation and the management of fixed assets
- Strong verbal and written communication skills
- Excellent organizational and time management skills
Pay
Individual salaries are determined after consideration of numerous factors including but not limited to the candidate's qualifications, experience, skills, and geography.
- National Range: $125,000 - $145,000
- Maryland Range: $125,000 - $145,000
- NYC/Long Island/Westchester Range: $125,000 - $145,000
About us
At BDO, how we show up matters. We build strong relationships by supporting one another, our clients, and our communities with care, curiosity, and a commitment to helping one another grow and succeed. Here, you'll find meaningful work, leaders invested in your success, and opportunities to build a career around what matters most to you. Our purpose is to be the people our