Tax Manager

We need to output HTML fragment with sections: About the role (but note the page already shows job title; we should not repeat job title as heading). The posting includes sections: About Tradeify (company description), About the role, What you will do, What we are looking for, Preferred qualifications, How success will be measured, Why join Tradeify, A Note on Our Hiring Process (but we need to remove boilerplate like AI-assisted tools? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The note about AI-assisted tools is maybe considered part of hiring process but not boilerplate? It's not EEO, but it's about hiring process. Might be considered relevant? The instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The note about AI-assisted tools is not exactly those, but it's part of hiring process. It might be considered relevant info. However we might keep it as a short paragraph under a section? There's no specific heading for that. Could incorporate into a paragraph under "Why join Tradeify" or separate? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine some. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. The posting includes: About the role (description), What you will do (responsibilities), What we are looking for (requirements/qualifications), Preferred qualifications (maybe qualifications), How success will be measured (maybe metrics), Why join Tradeify (benefits/culture). No explicit Pay, Schedule, Benefits. Benefits maybe implied in Why join Tradeify (but not explicit benefits like health etc). We should not create Benefits section unless posting actually states them. It does not list benefits like health insurance, 401k, etc. So we should not create Benefits, Pay, Schedule sections. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate duplicated lines. We need to output only HTML fragment. Let's extract content: Company description: "About TradeifyTradeify is a growing futures trading fintech focused on creating a reliable, transparent, and technology-enabled experience for traders. As the business scales, we are strengthening the systems, controls, and financial processes that support confident decisions and sustainable growth." We could include that as a paragraph maybe under a heading? There's no heading for company overview but we could include as a

  before sections. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that pattern. Could we add a heading "About Tradeify"? Not in list but could be okay? The instruction says use

  for section headings (e.g. About the role, Responsibilities...). It implies those are examples; we could still use other headings but better to stick to those. However we have company description; we could just put it as a

  before the first heading. Now sections: - About the role: we have a paragraph: "We are hiring a Tax Manager to own and strengthen Tradeify's tax function across a growing, multi-entity organization. This role will manage tax compliance, provision support, planning, and risk while coordinating effectively with external advisors and internal stakeholders. The ideal candidate combines strong technical tax knowledge with a practical, hands-on approach and can build scalable processes in a fast-moving environment." We can put that under

  About the role

  as

  . - Responsibilities: "What you will do" bullet list (actually sentences separated by periods). We need to convert to

  • . Let's list each duty: 1. Own the calendar, preparation, review, and timely filing of federal, state, local, and other applicable tax returns across Tradeify entities. 2. Coordinate tax provision and related accounting activities, including current and deferred tax calculations, reconciliations, journal entries, and financial statement disclosures. 3. Manage indirect tax obligations and evaluate nexus, registration, filing, and compliance requirements as the business expands. 4. Partner with external tax advisors while maintaining internal ownership of deliverables, data quality, deadlines, and conclusions. 5. Research and document tax positions, monitor regulatory developments, and translate changes into clear business actions. 6. Support entity structuring, new products, geographic expansion, and other business initiatives with practical tax analysis. 7. Lead responses to tax notices, inquiries, and audits and maintain organized supporting documentation. 8. Build and improve tax controls, policies, workpapers, and data flows to reduce risk and shorten recurring cycles. 9. Partner with Accounting, Legal, Payroll, Finance, and Operations on tax-sensitive transactions and reporting requirements. We'll put under

    Responsibilities

    with
    • each. - Requirements / Qualifications: "What we are looking for" list: - Bachelor's degree in Accounting, Finance, Taxation, or a related field. - Five or more years of progressive tax experience in public accounting, industry, or a combination of both. - Strong knowledge of U.S. federal and multi-state corporate tax compliance and tax accounting concepts. - Experience managing multiple entities, deadlines, advisors, and complex source data with a high degree of accuracy. - Ability to research technical issues, document conclusions, and communicate recommendations to non-tax stakeholders. - Strong project management skills and comfort building structure in an evolving organization. We can put under

      Requirements

      (or Qualifications). The instruction includes both Requirements and Qualifications as possible headings. We could combine into one section "Requirements". Or we could split: Requirements (the must-haves) and Qualifications (preferred). Let's follow: Requirements for the must-haves, Qualifications for preferred. Thus:

      Requirements

      with
      • for the six items. - Preferred qualifications: list: - CPA, active CPA candidacy, or advanced degree in taxation. - Experience in fintech, financial services, technology, or another high-growth, regulated environment. - Experience with NetSuite and tax provision or compliance software. - Exposure to international tax, transfer pricing, or cross-border operations. We'll put under

        Qualifications

        with
        • . - How success will be measured: bullet list: - Tax filings, payments, provisions, and supporting schedules are accurate and completed on time. - Tax risks and planning opportunities are identified early and communicated clearly. - Processes, documentation, and controls become more scalable and less dependent on outside providers. - Business partners receive timely, practical guidance for new initiatives and transactions. We'll put under

          Success Metrics

          ? But allowed headings include maybe not exactly; we could use "How success will be measured" as heading but not in list. The instruction says use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those examples. However we could rename to "Success Metrics" which is similar to maybe not listed. Safer to use one of the allowed headings that matches content: maybe "Requirements" already used; "Qualifications" used; "Responsibilities". For success metrics, we could put under "Requirements"? Not appropriate. Could we omit? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The posting has real content for success metrics, so we should include a section. We need a heading; we could use "Skills"? Not appropriate. Could we use "Qualifications"? Already used. Could we use "About the role"? Already used. Could we create a custom heading like "How success will be measured"? The instruction didn't forbid custom headings, just gave examples. I think it's okay to use that heading as

          How success will be measured

          . It's descriptive. - Why join Tradeify: paragraph(s). We'll put under

          Why join Tradeify

          with

          . - A Note on Our Hiring Process: This is about AI-assisted tools. Might be considered relevant but not boilerplate. Could we include under a heading? Not in list. Could we incorporate into a paragraph under "Why join Tradeify"? Might be thin. Better to include as its own section maybe

          Hiring Process

          . But not in examples. However we could treat it as part of "Why join Tradeify"? Not really. The instruction says remove boilerplate like EEO etc. This note is not boilerplate; it's specific to their process. I'd keep it as a short paragraph under its own heading maybe

          Hiring Process

          . But to stay close to examples, maybe we can omit it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that note. So we need a section for it. We could use

          Hiring Process

          . That seems reasonable. Now we need to ensure we don't repeat job title as heading. The job title is "Tax Manager". Not used. We must not include Job ID/requisition numbers. Now produce HTML fragment. Let's craft:

          About TradeifyTradeify is a growing futures trading fintech focused on creating a reliable, transparent, and technology-enabled experience for traders. As the business scales, we are strengthening the systems, controls, and financial processes that support confident decisions and sustainable growth.

          About the role

          We are hiring a Tax Manager to own and strengthen Tradeify's tax function across a growing, multi-entity organization. This role will manage tax compliance, provision support, planning, and risk while coordinating effectively with external advisors and internal stakeholders. The ideal candidate combines strong technical tax knowledge with a practical, hands-on approach and can build scalable processes in a fast-moving environment.

          Responsibilities

          • Own the calendar, preparation, review, and timely filing of federal, state, local, and other applicable tax returns across Tradeify entities.
          • Coordinate tax provision and related accounting activities, including current and deferred tax calculations, reconciliations, journal entries, and financial statement disclosures.
          • Manage indirect tax obligations and evaluate nexus, registration, filing, and compliance requirements as the business expands.
          • Partner with external tax advisors while maintaining internal ownership of deliverables, data quality, deadlines, and conclusions.
          • Research and document tax positions, monitor regulatory developments, and translate changes into clear business actions.
          • Support entity structuring, new products, geographic expansion, and other business initiatives with practical tax analysis.
          • Lead responses to tax notices, inquiries, and audits and maintain organized supporting documentation.
          • Build and improve tax controls, policies, workpapers, and data flows to reduce risk and shorten recurring cycles.
          • Partner with Accounting, Legal, Payroll, Finance, and Operations on tax-sensitive transactions and reporting requirements.

          Requirements

          • Bachelor's degree in Accounting, Finance, Taxation, or a related field.
          • Five or more years of progressive tax experience in public accounting, industry, or a combination of both.
          • Strong knowledge of U.S. federal and multi-state corporate tax compliance and tax accounting concepts.
          • Experience managing multiple entities, deadlines, advisors, and complex source data with a high degree of accuracy.
          • Ability to research technical issues, document conclusions, and communicate recommendations to non-tax stakeholders.
          • Strong project management