Director, Business Integration

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow specific rules: 1. Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for lists of duties/requirements/benefits, and

  for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting: 1. Company description/About TAIT - this is "About the role" or company context 2. Position Purpose - this is "About the role" 3. Key Responsibilities - multiple subsections 4. Qualifications - list of requirements 5. TAIT Benefits - list of benefits 6. EEO statement - boilerplate, should be removed I need to structure this properly. Let me identify the sections: - About the role (Position Purpose) - Responsibilities (Key Responsibilities with subsections) - Qualifications (the qualifications list) - Benefits (TAIT Benefits) The posting doesn't have Pay or Schedule sections explicitly, so I won't create those. I'll create: 1.

  About the role

  with the Position Purpose content 2.

  Responsibilities

  with the Key Responsibilities broken into subsections (but as lists under the main Responsibilities heading) 3.

  Qualifications

  with the qualifications list 4.

  Benefits

  with the benefits list For Responsibilities, the posting has several sub-sections: Due Diligence and Integration Planning, Integration Leadership and Governance, Business Continuity and Organizational Alignment, People and Cultural Integration, Value Realization and Continuous Improvement. I should preserve these as sub-headings or as grouped lists. Since the rule says use

  for section headings, and these are sub-sections of Responsibilities, I could use

  but the rule only mentions

  . I think I should keep them as

  headings or group them under Responsibilities with

  • for each bullet point. But the content is quite detailed with multiple bullet points under each sub-section. Looking at the rules: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other heading levels, but says to use

    for those main sections. I think I should use

    for the main sections and perhaps

    for sub-sections, but the instruction says "use

    for section headings" and lists examples. To be safe, I'll use

    for the main sections only, and for the sub-sections under Responsibilities, I'll include them as part of the Responsibilities section with bold text or as list items with the sub-section name as a lead-in. Actually, re-reading: "Use

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

      for prose." The responsibilities have prose descriptions and bullet points. I think the best approach is to have

      Responsibilities

      then for each sub-section, a

      with the sub-section name in bold, followed by

      • for the bullet points. But the sub-sections have both prose and bullet points. For example, "Due Diligence and Integration Planning" has a paragraph then bullet points. I'll structure each sub-section as a

        (since it's a sub-heading) but the rule only mentions

        . However, semantic HTML allows

        . The instruction says "use

        for section headings" but doesn't say "only use

        ". I think using

        for sub-sections is acceptable and more semantic. But to strictly follow: "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This implies those are the only section headings to use

        for. Sub-sections might not need headings. I'll make the sub-section titles bold in

        tags. Let me draft:

        About the role

        TAIT partners with artists, brands, IP holders and place makers to bring culture-defining, never-before-seen experiences to life. With a legacy of innovation spanning over 45 years, TAIT has grown from pioneering in rock ‘n’ roll concert staging to setting the global standard for extraordinary live events and experiences through cutting-edge technology, precision engineering, and creative design. TAIT’s 20 global offices have developed iconic productions and experiences in over 30 countries, all seven continents, and even outer space for renowned performers, theme parks, exhibits, and venues across the globe, including partnerships with Taylor Swift, Cirque Du Soleil, Royal Opera House, Nike, NASA, Bloomberg, Google, Beyoncé, and The Olympics.

        The Director, Business Integration is responsible for leading acquired businesses from due diligence through integration into TAIT. This role develops and executes thoughtful, practical integration roadmaps that protect business continuity, preserve the strengths of each acquired company, realize deal value, and create long-term alignment with TAIT’s global strategy and operating model. TAIT is a highly complex, global organization operating across multiple markets, capabilities, regions, legal entities, and business models. Successful integration requires more than implementing a standard playbook. The Director must understand the strategic intent behind each acquisition, evaluate the unique needs of the acquired business, and determine what should be integrated, standardized, transformed, or intentionally preserved. The Director serves as the central leader connecting deal team (i.e., Finance, Legal, and Corporate Development), executive sponsors, acquired-company leadership, and TAIT’s functional teams. The role establishes clear governance, decision rights, milestones, dependencies, and accountability from diligence through stabilization and value realization.

        Responsibilities

        Due Diligence and Integration Planning

        • Partner with deal team and functional leaders during due diligence to identify integration requirements, risks, dependencies, costs, and opportunities.
        • Support the assessment of the acquired company’s operating model, leadership structure, culture, workforce, technology, financial processes, commercial practices, legal entities, and operational capabilities.
        • Translate diligence findings and the investment thesis / strategy into a comprehensive integration strategy and roadmap.
        • Define the appropriate integration approach based on the strategic purpose, maturity, complexity, and risk profile of each acquisition.
        • Identify critical Day 1 requirements, near-term stabilization priorities, and longer-term transformation opportunities.
        • Develop and monitor realistic integration budgets, timelines, resource requirements, and success measures.

        Integration Leadership and Governance

        • Serve as the central integration leader from pre-close through integration completion for both TAIT stakeholders and acquired entity leadership.
        • Establish integration governance, including workstreams, decision rights, executive sponsorship, escalation paths, and reporting cadences.
        • Coordinate cross-functional work across Finance, People, Culture, Legal, GTS, Commercial, Operations, Marketing, Procurement, and other relevant teams.
        • Clarify ownership, deliverables, interdependencies, and handoffs across each integration workstream.
        • Maintain the enterprise integration roadmap and ensure activities are appropriately sequenced and resourced.
        • Facilitate timely decisions while ensuring leaders understand the operational, financial, cultural, and customer implications.
        • Provide clear, concise progress updates to executive leadership and other key stakeholders.
        • Collaborate with Finance and functional leaders to quantify one-time integration costs required investments, and synergies pre-close, and ensure tracking of those costs and synergies post-close.
        • Develop a scalable TAIT integration framework / playbook covering diligence, pre-close planning, Day 1, stabilization, and execution.

        Business Continuity and Organizational Alignment

        • Support the protection of customer relationships, project delivery, revenue, talent, and operational continuity throughout the integration.
        • Partner with acquired-company leaders to understand the practices and capabilities that contribute to their success.
        • Balance enterprise consistency with the need to preserve differentiated capabilities, customer value, and local market strengths.
        • Support the alignment of leadership structures, accountabilities, reporting relationships, and decision-making processes.
        • Ensure integration activity reflects TAIT’s operating model while recognizing that different businesses may require different paths and timelines.
        • Identify operational friction, duplication, or unclear ownership and recommend practical solutions.

        People and Cultural Integration

        • Partner with People leaders to develop thoughtful organizational, talent, retention, communication, and change-management plans.
        • In collaboration with LiNC, assess cultural similarities and differences and incorporate those findings into the integration strategy.
        • Ensure acquired team members understand the integration vision, key decisions, expected changes, and available support.
        • Support leaders through organizational change while maintaining transparency, trust, and engagement.
        • Identify critical talent and organizational capabilities that should be protected during the transition.
        • Promote collaboration between acquired teams and the broader TAIT organization.

        Value Realization and Continuous Improvement

        • Establish measurable integration outcomes aligned with the acquisition thesis, including growth, operational, financial, organizational, and customer objectives.
        • Track synergies, integration costs, risks, milestones, and value-realization commitments.
        • Identify barriers to value creation and work with business and functional leaders to resolve them.
        • Conduct post-integration reviews to evaluate outcomes, capture lessons learned, and transition ongoing responsibilities to permanent business owners.
        • Build and continuously improve TAIT’s integration framework, tools, governance standards, and repeatable practices.
        • Develop a scalable approach that provides structure without treating every acquisition the same.

        Qualifications

        • Bachelor’s degree in business, finance, operations, organizational leadership, or a related discipline.
        • 10+ years of experience in integration, mergers & acquisitions (M&A), operations.
        • Significant experience leading mergers and acquisitions (M&A) integration, business transformation, enterprise program management, or complex organizational change.
        • Demonstrated experience supporting transactions from due diligence through post-close integration and value realization.
        • Experience working within a global, matrixed, project-based, or operationally complex organization.
        • Strong understanding of business operations and functional interdependencies across Finance, People, Culture, Technology, Legal, Commercial, and Operations.
        • Experience developing integration roadmaps, governance structures, financial models, executive reporting, and risk-management plans.
        • Demonstrated ability to influence senior leaders and drive decisions without relying solely on direct authority.
        • Experience working with founder-led, entrepreneurial, or culturally distinct acquired businesses is