Senior Director, AI Platform Architecture

We need to output HTML fragment with sections: About the role? Actually headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if content exists. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate. We need to parse the posting. Key sections: - About the Team: description. - About the Position: description. - Key Responsibilities: list. - Measures of Success: maybe part of Responsibilities? Could be separate but not required heading. We can include under Responsibilities or separate? The instruction: use headings for those specific headings only if real content. We have content for Responsibilities (Key Responsibilities). Also we have Qualifications section. Knowledge, Skills, and Abilities could be Skills. Also we have Compensation And Benefits (Pay and Benefits). Also Work Schedule Standard (Mon-Fri) Environmental Conditions Office -> schedule and maybe environmental conditions but we only need Schedule heading if present. It says Work Schedule Standard (Mon-Fri). So we have schedule info. Also Environmental Conditions Office maybe not needed. We also have location remote US etc. Could be part of About the role? Not a heading. Could be included in a paragraph under About the role? But we have About the Team and About the Position. Could combine? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections: About the role (maybe combine About the Team and About the Position?), Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. Requirements maybe not needed if not explicit; we have Qualifications (education, experience). Could treat Requirements as same as Qualifications? But we have both Qualifications and Knowledge, Skills, and Abilities. Could map Qualifications to Qualifications heading, Skills to Skills heading. Requirements maybe not needed. We must not create empty headings. So we need to ensure each heading has substantive content. Let's extract content: About the Team paragraph(s): "At PPD, Thermo Fisher’s clinical research group (CRG), we’re using digital innovation, data science, and AI to reimagine how life-changing therapies reach patients. Our teams combine deep scientific expertise with advanced analytics, automation, and digital platforms to make research smarter, faster, and more connected. We know that innovation happens when diverse minds meet. Our Digital Science, Data, and AI professionals collaborate closely with scientists, clinicians, and operational experts to solve real-world challenges in clinical research. Alongside our partnership with Open AI, you can be part of the collaboration that will help to improve the speed and success of drug development, enabling customers to get medicines to patients faster and more cost effectively. About the Team: CRG Digital AI is the engine that translates our digital strategy into scalable, production-ready AI capabilities that drive measurable business impact. Operating in close partnership with Product, Data, and Engineering, the team embeds AI across our digital portfolio to accelerate clinical trial execution, enhance data-driven decision-making, and unlock differentiated value for our customers. Through a combination of centralized platforms, standards, and federated execution, CRG Digital AI enables rapid innovation while ensuring consistency, quality, and responsible AI practices." We can combine into About the role paragraph. About the Position paragraph(s): "Reporting to the VP, Head of Analytics and AI, the Senior Director, AI Platform Architecture is a senior leadership role within CRG Digital responsible for defining, building, and scaling the foundational AI platform that enables the rapid development, deployment, and operation of AI-enabled products and solutions across CRG. This leader owns the end-to-end AI platform strategy, architecture, and delivery model—ensuring that AI capabilities are scalable, reusable, secure, and production-ready. Operating at the intersection of Applied AI (AAI), Data Platforms, and Digital Engineering, this role serves as the backbone of CRG’s AI ecosystem—providing the tools, infrastructure, standards, and services required to accelerate AI innovation while maintaining governance, compliance, and operational excellence. The Director will enable both centralized and federated AI execution, empowering product and engineering teams to build AI solutions efficiently and consistently." We can include that. Responsibilities: list under Key Responsibilities with subpoints. Need to preserve all detail. We'll convert each bullet into

. The bullet points are long sentences with sub-bullets (like Platform Architecture & Engineering includes sub-items). We need to preserve all detail; we can keep sub-bullets as nested

• . The instruction: Use
  • for any list of duties/requirements/benefits. So we can have nested lists. We'll extract each main responsibility heading and its content. Key Responsibilities sections: - AI Platform Strategy & Ownership - Define and execute the AI platform strategy and roadmap, aligned to CRG Digital and AI priorities - Establish the AI platform as a shared capability layer supporting all AI-enabled products and workflows - Ensure alignment with enterprise architecture, data platform (MDP), and security strategies - Drive a platform-first approach to AI development, enabling reuse and scalability across domains - Platform Architecture & Engineering - Lead the design and development of the AI platform architecture, including: * Model development, training, and deployment frameworks * MLOps and LLMOps pipelines * Model serving, monitoring, and lifecycle management * Integration with data platforms (e.g., Snowflake, Databricks) * Ensure platform supports GenAI, agentic workflows, and traditional ML use cases * Establish standards for performance, scalability, reliability, and cost efficiency - Reusable AI Capabilities & Tooling - Build and scale reusable AI components, including: * Model libraries and templates * Prompt frameworks and orchestration tools * Workflow automation and agent frameworks * Enable rapid development through self-service tools and developer enablement * Reduce duplication and accelerate time-to-market through standardization and reuse - MLOps, Governance & Responsible AI Enablement - Establish and operationalize AI lifecycle management practices, including: * Model versioning, validation, deployment, and monitoring * Performance tracking and drift detection * Partner with AI Risk/Governance teams to embed compliance, security, and responsible AI principles into the platform * Ensure auditability, traceability, and adherence to regulatory and enterprise standards - Federated AI Enablement - Provides self-service platform capabilities to AI Engineering; ensures adoption through ease-of-use and standardization - Enable a federated AI model, allowing domain/product teams to build AI capabilities while leveraging centralized platform standards - Provide tooling, frameworks, and guardrails to ensure consistency and quality across distributed teams - Act as a central enablement layer supporting both AAI and product-aligned engineering teams - Cross-Functional Integration - Partner closely with: * AAI (Applied AI) for solution design and AI architecture * Data Platforms for data ingestion, quality, and readiness * Digital Engineering for product integration and delivery - Ensure seamless integration of platform capabilities into AI products and workflows - Partner & Ecosystem Management * Define and manage relationships with technology vendors and platform partners (e.g., cloud, AI tooling providers) * Evaluate and integrate emerging AI technologies and tools into the platform ecosystem * Optimize the balance between build vs. buy vs. partner decisions - Team Leadership & Capability Building - Lead a high-performing team of AI platform engineers, MLOps specialists, and platform architects - Define skills, roles, and career paths for AI platform talent - Drive capability building in AI engineering, platform operations, and emerging AI technologies - Foster a culture of innovation, reliability, and continuous improvement Measures of Success: could be included under Responsibilities or separate but not a required heading. We could add as a sub-section under Responsibilities maybe as a paragraph. But we have no heading for Measures of Success; we could just include as a paragraph after responsibilities. The instruction: only include sections when posting has real, specific content for it. We have content for Measures of Success but no heading in list; we could incorporate into Responsibilities as a paragraph. Qualifications: list: - Bachelor’s degree required; advanced degree preferred (computer science, engineering, AI/ML, or related field) - 12 years of experience in software engineering, data platforms, AI/ML engineering, or platform leadership roles - Proven track record of building and scaling AI/ML platforms or data platforms in enterprise environments - Strong understanding of AI/ML and GenAI technologies, MLOps/LLMOps practices and Cloud platforms and modern data architectures - Experience operating in complex, matrixed organizations with cross-functional stakeholders - Experience in regulated environments (healthcare/life sciences) preferred Knowledge, Skills, and Abilities (Skills): - Deep technical and strategic understanding of AI platform architecture and operations - Strong systems thinking with ability to balance innovation, scalability, and governance - Ability to translate platform capabilities into business and product impact - Strong leadership and team-building capabilities - Excellent stakeholder management and ability to influence across Product, Data, AI, and Engineering teams - Ability to operate in a fast-paced, evolving technology landscape Benefits: from Compensation And Benefits section: - A choice of national medical and dental plans, and a national vision plan, including health incentive programs - Employee assistance and family support programs, including commuter benefits and tuition reimbursement - At least 120 hours paid time off (PTO), 10 paid holidays annually, paid parental leave (3 weeks for bonding and 8 weeks for caregiver leave), accident and life insurance, and short- and long-term disability in accordance with company policy - Retirement and savings programs, such as our competitive 401(k) U.S. retirement savings plan - Employees’ Stock Purchase Plan (ESPP) offers eligible colleagues the opportunity to purchase company stock at a discount - Also mention variable annual bonus based on performance. Pay: salary range: $167,500.00–$278,000.00 (based in North Carolina). Also variable annual bonus. Schedule: Work Schedule Standard (Mon-Fri). Also Environmental Conditions Office (maybe not needed). So schedule: Standard Monday-Friday. We also have location remote US (east coast preference). Could be included in About the role paragraph or separate but not a heading. We must not include boilerplate like EEO, etc. Remove lines like "At Thermo Fisher Scientific, we are committed to fostering a healthy and harmonious workplace..." etc. Also remove "Please see below for the required qualifications for this position, which also includes the possibility of equivalent experience:" and the following sentences about communication etc. Those are generic boilerplate; we should remove them. Also remove "Must be able to pass a comprehensive background check..." etc. That's also boilerplate; remove. Also remove "Band 9 level role Location: Remote US (east coast preference). Relocation assistance is NOT provided. Must be legally authorized to work in the United States without sponsorship." Might be considered metadata but not boilerplate? It's location info; could be kept as part of About the role? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Location is minor metadata; we could include in a short paragraph under About the role. But we already have About the role paragraph; we could add location there. However we must preserve ALL substantive information; location is substantive? It's about where job is based; could be considered metadata but still substantive. We'll include it in a paragraph after About the role maybe. We must not include "Compensation And Benefits" heading? We'll have Benefits and Pay headings. Now construct HTML. We'll start with

    About the role

    then

    containing combined About the Team and About the Position plus location maybe. Then

    Responsibilities

    then
    with nested lists. Then

    Qualifications

    then
    . Then

    Skills