Head of Internal Audit

We need to output HTML fragment with sections: About the role? The posting includes description of company and role. We need headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Only include sections where there is real specific content. We have content for About the role (intro paragraph about role). Responsibilities (list). Requirements (list). Preferred (maybe part of Requirements? Could be separate but we can include under Requirements or separate "Preferred Qualifications". The instruction says use headings like Qualifications, Skills, Benefits, Pay, Schedule. We have Benefits and Pay. No Schedule info. So we should not include Schedule heading. Also we have "Why Join BitGo?" which is like benefits/culture; but we already have Benefits section. Could treat "Why Join BitGo?" as part of Benefits or maybe as a separate section like "About the company". But instruction says use headings for those specific ones; we can include About the role (intro). Then Responsibilities, Requirements, Benefits, Pay. Possibly also Qualifications (but we have Requirements covering qualifications). Could combine. But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role, Responsibilities, Requirements, Benefits, Pay. Not include Qualifications, Skills, Schedule if no content. Ensure we don't repeat job title as heading. No Job ID etc. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. So we need to extract the substantive paragraphs. Let's parse: Company description: "BitGo (NYSE: BTGO) is the digital asset infrastructure company delivering custody, wallets, staking, trading, financing, stablecoins, and settlement services from regulated cold storage. Since 2013, BitGo has focused on accelerating the transition of the financial system to a digital asset economy. BitGo maintains a global presence and multiple regulated entities, including BitGo Bank & Trust, National Association, the first federally chartered digital asset trust bank owned by a publicly traded company. Today, BitGo serves thousands of institutions, including many of the industry's top brands, financial institutions, exchanges, and platforms, and millions of investors worldwide. For more information, visit www.bitgo.com. This role will require being full-time onsite at either our Palo Alto or San Francisco offices to support collaborative team dynamics and innovative problem-solving." Then role description: "BitGo is looking for a Head of Internal Audit to lead and scale the company’s third line of defense during a pivotal period of growth. Reporting to the Audit Committee functionality and the Chief Operating Officer administratively, this individual will own the design and execution of a risk-based audit program across BitGo’s global operations, drive Sarbanes-Oxley compliance, and serve as a trusted advisor to the business on matters of internal control, regulatory compliance, and operational risk. The ideal candidate is a seasoned audit leader who thrives in dynamic, fast-moving environments and brings deep expertise in financial services or technology." That's About the role. Responsibilities list: bullet points each starting with a verb. Need to preserve each as

. Responsibilities: - Own and continuously mature the company’s Sarbanes-Oxley (SOX) compliance framework, including designing, executing, and overseeing the annual Internal Controls over Financial Reporting (ICFR) testing plan in coordination with management and external auditors - Serve as the primary internal owner for SOC 1, SOC 2, and CCSS audits, coordinating across engineering, security, operations, and finance to facilitate timely and successful completion of each examination - Oversee and direct co-sourced audit resources engaged in the planning and execution of operational and compliance audits across BitGo’s regulated entities globally, ensuring consistent audit quality, methodology, and timely delivery of findings - Build and maintain strong working relationships with external auditors, managing day-to-day interactions, coordinating audit requests, and aligning on scope, timing, and control reliance strategies to support an efficient and effective external audit process - Prepare and deliver regular, high-quality reporting on audit results, open findings, remediation status, and emerging risk themes to BitGo’s Board of Directors, Audit Committees, and senior management across its regulated entities - Develop and maintain a risk-based annual internal audit plan that reflects the company’s strategic priorities, regulatory obligations, and evolving risk landscape, and update the plan dynamically in response to business changes - Partner cross-functionally with Legal, Compliance, Finance, and Technology teams to identify control gaps, support remediation efforts, and promote a culture of accountability and continuous improvement Requirements list: - 10+ years of progressive experience in internal audit, public accounting, or a combination thereof, including demonstrated leadership of audit teams or functions - Deep expertise in SOX / ICFR compliance, including scoping, control design evaluation, testing, and deficiency assessment in complex organizational environments - Hands-on experience managing SOC 1 and SOC 2 readiness and examination processes, including coordinating with service auditors and internal stakeholders - Experience operating in or auditing regulated financial services entities, with a strong understanding of the regulatory and compliance landscape applicable to such organizations - Proven ability to manage and direct co-source or third-party audit providers, including scoping engagements, reviewing work product, and ensuring quality and timeliness - Strong executive presence and communication skills, with the ability to present complex audit findings and risk themes clearly and credibly to Boards, Audit Committees, and C-suite stakeholders - Bachelor’s degree in Accounting, Finance, Business, or a related field; advanced degree a plus Preferred: - One or more relevant professional certifications, including Certified Public Accountant (CPA), Certified Internal Auditor (CIA), and/or Certified Information Systems Auditor (CISA) - Prior experience in the digital assets industry, including familiarity with digital asset custody, trading, staking, or settlement operations and the associated risk and control environment - Knowledge of the rules, regulations, and supervisory expectations applicable to federally chartered trust banks, including OCC guidance, fiduciary standards, and related compliance obligations We could include Preferred under Requirements or as separate "Preferred Qualifications". The instruction only lists certain headings; we could put Preferred under Requirements as part of same list or separate section "Requirements" and include both required and preferred. But better to separate: maybe "Requirements" for required, and "Preferred Qualifications" for preferred. However the instruction didn't list "Preferred Qualifications" as a heading option, but we could still use it? It says use headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could still use other headings but better to stick to those. We could incorporate Preferred into Requirements section, maybe as a sub-list with note "Preferred". But we need to preserve all info; we can include a note inside the list item like "(Preferred)". That's okay. Benefits: list from "Here are some of the benefits* of working at BitGo:" then bullet list. Benefits items: - Competitive base salary, bonus and stock options - 100% company paid health insurance for employee, partner and dependents - Up to 4% 401k company match - Paid parental leave, Paid vacation - Free commuter/parking pass; near BART - Free custom lunches, dinners and snacks - Computer equipment and workplace furniture to suit your needs - Great colleagues and inspiring startup environment - Benefits may vary based on location Also there is a line: "Pay Transparency Notice: Depending upon your leveling and location, the compensation for this role averages between $190,000 - $275,000 USD base salary. Equity, an annual performance bonus and the benefits outlined below are also a part of this role's package." So Pay section: we need to include that sentence. Also note equity and annual performance bonus mentioned but those are part of compensation; we can include in Pay. We should not include "Why Join BitGo?" as separate; but we could incorporate its content into Benefits or maybe as a short paragraph about culture. However the instruction says include a section ONLY when posting has real, specific content for it. The "Why Join BitGo?" is a paragraph about culture; we could treat it as part of Benefits or maybe as a separate "About the company" but not required. Safer to incorporate into Benefits section as a paragraph after list? But we must not invent headings. Could add a

under Benefits after the list describing culture. That's okay. We must not include boilerplate like cookie/navigation/legal/EEO etc. There's none. Now construct HTML:

About the role

... (the paragraph(s) describing role and company). We need to include company description and role specifics. Probably combine into one

or multiple

. We'll keep as one

containing all that info. Then

Responsibilities

with each responsibility as
• . Then

  Requirements

  with required items; then maybe a note for preferred items: we could add a
  • with "Preferred: ..." but better to separate: maybe add a

    before list: "Preferred qualifications:" then

    . But that adds a heading? Not needed. We'll just include preferred items as
    • with "(Preferred)" at end. Then

      Benefits

      with benefits list; after list maybe a

      for the "Why Join BitGo?" paragraph. Then

      Pay

      with pay transparency notice. We should not include Schedule. Make sure to preserve all info: include the line about full-time onsite at Palo Alto or San Francisco offices. Include the bit about reporting to Audit Committee functionality and COO administratively. Include the bit about ideal candidate. Let's craft the About the role paragraph: "BitGo (NYSE: BTGO) is the digital asset infrastructure company delivering custody, wallets, staking, trading, financing, stablecoins, and settlement services from regulated cold storage. Since 2013, BitGo has focused on accelerating the transition of the financial system to a digital asset economy. BitGo maintains a global presence and multiple regulated entities, including BitGo Bank & Trust, National Association, the first federally chartered digital asset trust bank owned by a publicly traded company. Today, BitGo serves thousands of institutions, including many of the industry's top brands, financial institutions, exchanges, and platforms, and millions of investors worldwide. For more information, visit www.bitgo.com. This role will require being full-time onsite at either our Palo Alto or San Francisco offices to support collaborative team dynamics and innovative problem-solving. BitGo is looking for a Head of Internal Audit to lead and scale the company’s third line of defense during a pivotal period of growth. Reporting to the Audit Committee functionality and the Chief Operating Officer administratively, this individual will own the design and execution of a risk-based audit program across BitGo’s global operations, drive Sarbanes-Oxley compliance, and serve as a trusted advisor to the business on matters of internal control, regulatory compliance, and operational risk. The ideal candidate is a seasoned audit leader who thrives in dynamic, fast-moving environments and brings deep expertise in financial services or technology." That seems comprehensive. Now Responsibilities list as above. Requirements list: include the 7 required items. Preferred items: we can add as separate list under Requirements with a note "Preferred qualifications:" then

      . But that adds a heading? Not a heading, just a

      . That's okay. Let's do:

      Requirements

      Required:

      ... required items ...

      Preferred qualifications:

      ...