Director of Accounting

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Job Description (title). There's an "Opportunity" paragraph describing role. Then "What You Will Own" with subsections: Close, Reporting & Controllership; Technical Accounting & Policy; Audit, Controls & Compliance; Process Automation & Systems Modernization; Global Team Leadership. Then "What You Bring" with Required and Strongly Preferred. Then Salary line. We need to map to headings: About the role (maybe the opportunity paragraph). Responsibilities (what you will own). Requirements (required). Qualifications (maybe strongly preferred? but they said Qualifications separate from Skills? Usually Qualifications = required? But we have both Required and Strongly Preferred. Could treat Required as Requirements, Strongly Preferred as Qualifications or Skills? They said Skills separate. We could put Required under Requirements, Strongly Preferred under Qualifications, and maybe Skills under Skills (like technical skills). But we have many skill-like items: ERP ownership, written communication, etc. Could put those under Skills. However we must not invent sections with filler. We need to see if we have content for each. We have: - About the role: The Opportunity paragraph (Reporting directly to CFO...). That's substantive. - Responsibilities: The "What You Will Own" sections (Close, Reporting & Controllership; Technical Accounting & Policy; Audit, Controls & Compliance; Process Automation & Systems Modernization; Global Team Leadership). That's substantive. - Requirements: The "What You Bring" Required bullet list (Active CPA license, 10+ years, etc). That's substantive. - Qualifications: Could be the Strongly Preferred list (Professional fluency in Mandarin, experience at high-growth, etc). That's substantive. - Skills: Could be specific technical skills like ERP ownership experience, written communication, ability to work on-site hybrid, etc. But many of those are already in Required/Preferred. However we could still create a Skills section for items like "Excellent written communication", "Ability to work on-site...", "ERP ownership experience", "Experience with close-management platforms", etc. But we need to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep all info. If we split into sections, we must ensure we don't lose any info. We can categorize but must keep all details. It's okay to have overlapping? Better to keep each piece in one section only. So we need to decide a logical grouping that covers all info without duplication. We have sections: About the role (Opportunity). Responsibilities (What You Will Own). Requirements (Required). Qualifications (Strongly Preferred). Skills (maybe we can include things like "Excellent written communication", "Ability to work on-site...", "ERP ownership experience", "Experience with close-management, reconciliation, or automation platforms", "Experience with reporting or BI tooling", "Comfort working with data directly — SQL, Power Query, Alteryx, or scripting", "Experience in AI, data services, technology-enabled services, or a global professional-services delivery model", "Experience with international statutory reporting, transfer pricing, and cross-border intercompany structures", "Experience integrating acquisitions or standing up new legal entities". Many of those are already in Strongly Preferred list. Actually the Strongly Preferred list includes: Professional fluency in Mandarin; Experience at a high-growth, venture- or private-equity-backed company, and experience preparing an accounting function for audit readiness, IPO, or SOX compliance; Hands-on experience with close-management, reconciliation, or automation platforms (e.g., BlackLine, FloQast, Numeric, Trintech) and with reporting or BI tooling (e.g., Power BI, Tableau); Comfort working with data directly — SQL, Power Query, Alteryx, or scripting — enough to prototype and to speak credibly with engineers; Experience in AI, data services, technology-enabled services, or a global professional-services delivery model; Experience with international statutory reporting, transfer pricing, and cross-border intercompany structures; Experience integrating acquisitions or standing up new legal entities. Thus the Strongly Preferred list already covers many skill-like items. So we could treat Strongly Preferred as Qualifications, and maybe we don't need a separate Skills section. The Required list includes: Active CPA license; 10+ years experience; prior in-house experience at tech companies as Senior Manager or Director; Demonstrated controllership experience; Direct experience leading a Big 4 financial statement audit as company-side owner; Track record of accounting process automation; Proven experience partnering with IT and Engineering to scope, prioritize, and deliver internal tools, system integrations, and data automation; Deep technical U.S. GAAP expertise; Proven experience working with international teams in a multi-entity, multi-currency environment; ERP ownership experience; Excellent written communication; Ability to work on-site in the San Francisco Bay Area or Redmond, WA on a hybrid schedule. Thus Required includes many skill-like items as well. So we could treat Required as Requirements, and maybe we don't need separate Skills. The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. We have About the role, Responsibilities, Requirements, Qualifications (Strongly Preferred). Pay is present: Salary line. Benefits? Not mentioned. Schedule? Not mentioned besides hybrid schedule ability to work on-site (that's more location/hybrid). Not a schedule like full-time/part-time. So we should not create Benefits or Schedule sections because no specific content. Pay we have salary range. Thus output sections: About the role, Responsibilities, Requirements, Qualifications, Pay. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Not include Job ID etc. We need to preserve all substantive information. So we need to include all paragraphs and bullet points. Let's extract content. About the role: The Opportunity paragraph: "Reporting directly to the Chief Financial Officer, the Director of Accounting owns the accounting organization end to end: the global close, technical accounting and U.S. GAAP policy, internal controls, and audit. You will act as the company's de facto Controller — the final word on how transactions are recorded and how the numbers are defended.This role suits a candidate who trained at a large public accounting firm, then moved in-house and grew through Senior Manager or Director of Accounting roles at technology companies. You have carried a close, survived audits, written the memos, and built the processes that let a finance team close faster with fewer surprises. You are comfortable being both the technical expert and the operator, and you have done it across time zones.Immediate priority: lead the 2026 audit, conducted to PCAOB standards with a Big 4 audit firm, to a clean and on-time opinion. This is the defining deliverable of the role's first year and the primary lens through which candidates will be evaluated." We need to keep that as prose (

  ). Possibly split into multiple paragraphs but we can keep as one. Responsibilities: "What You Will Own" with subheadings. We need to turn each bullet? Actually it's paragraphs with bold headings. We'll need to represent as

  • for any list of duties/requirements/benefits. The content includes multiple sections each with multiple sentences. We could treat each major bullet as a list item. Eg: - Close, Reporting & Controllership: Own the global month-, quarter-, and year-end close across all entities, driving cycle-time reduction without sacrificing accuracy. Own the consolidated financial statements, intercompany accounting, foreign currency translation, and the supporting reporting package delivered to the CFO, executive team, board, and investors. Own the general ledger, chart of accounts, and accounting systems roadmap, including ERP process design and automation of manual work. Own accounting operations — revenue, AR/collections, AP, payroll accounting, equity, leases, fixed assets, and treasury accounting. - Technical Accounting & Policy: Serve as the internal authority on U.S. GAAP. Research complex transactions, write the technical position memos, and defend those positions with auditors. Own the accounting treatment for revenue recognition (ASC 606) across multi-element, milestone, and usage-based arrangements; leases (ASC 842); stock-based compensation (ASC 718); business combinations (ASC 805); and capitalized software (ASC 350-40). Maintain the global accounting policy manual and drive consistent application across all entities and regions. Assess and implement new accounting standards, and advise the CFO on the accounting implications of new commercial structures, financings, and M&A activity. - Audit, Controls & Compliance: Lead the 2026 audit to a clean, on-time opinion — conducted to PCAOB standards with a Big 4 audit firm. Own the audit plan, the PBC calendar, sampling and evidence requests, and every technical position put in front of the engagement team. Own the Big 4 auditor relationship end to end, including the engagement partner and manager cadence, scoping and materiality discussions, component and international audit coordination, and timely resolution of open items. Drive the company to a PCAOB-grade documentation standard: control descriptions, evidence retention, review sign-offs, and audit trails that withstand inspection-level scrutiny. Design, document, and operate the internal control environment, building toward SOX-grade controls as the company matures — with no material adjustments or significant deficiencies. Partner with Tax, Legal, and external advisors on direct and indirect tax provisions, transfer pricing support, statutory filings, and local regulatory compliance across international jurisdictions. - Process Automation & Systems Modernization: Own the accounting automation agenda: identify manual, spreadsheet-dependent, and error-prone processes and systematically engineer them out. Modernize the close using current tooling — close management and task orchestration, automated account reconciliation and transaction matching, AP/expense automation, revenue and billing systems, and reporting and analytics layers. Partner directly with Engineering and IT to specify, prioritize, and implement internal tools and integrations that serve Accounting — data pipelines between operational systems and the ERP, automated journal entry feeds, custom reporting, and workflow and approval automation. Write clear functional requirements, act as business owner on internal tooling projects, and manage them through UAT, cutover, and adoption. Evaluate where AI and intelligent automation can responsibly reduce cycle time and manual review — and apply the control and auditability standards that make those tools defensible to auditors. Track and report efficiency outcomes: close-cycle days, manual journal entry volume, reconciliation automation rate, and cost per transaction. - Global Team Leadership: Build, lead, and develop a distributed accounting team spanning U.S. and international locations, including offshore shared-service and outsourced resources. Set clear close calendars, ownership, and quality standards across regions and time zones, and hold the organization to them. Partner cross-functionally with FP&A, Legal, Sales, Operations, and Delivery leadership — translating accounting requirements into terms the business can act on. Serve as a trusted deputy to the CFO on special projects: systems implementations, financing and diligence support, entity setup, and integration work. We need to preserve all that. Use
    • for each major bullet? Could also nest lists but spec says use
      • for any list of duties/requirements/benefits. So we can make each major responsibility a
      • containing the sentences (maybe as

        inside?). But spec says use

        for prose. So inside

      • we can have

        for prose. That's acceptable. Thus:

        Responsibilities

        • Close, Reporting & Controllership: Own the global month-, quarter-, and year-end close across all entities, driving cycle-time reduction without sacrificing accuracy. Own the consolidated financial statements, intercompany accounting, foreign currency translation, and the supporting reporting package delivered to the CFO, executive team, board, and investors.