Principal Data Architect II, Biotherapeutics and Genetic Medicine

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. We must not repeat job title. Must not include Job ID etc. Remove boilerplate: company description, overview? The "Company Description About AbbVie" is likely boilerplate; we should remove it. The "Overview Job Description" maybe part of description; we can include as prose under About the role? Actually we need to decide sections. We have content: - About the role: maybe the paragraph after Overview Job Description: "Biotherapeutics and Genetic Medicine (BGM) sits within AbbVies Discovery Research organization and supports discovery and optimization across biotherapeutic and genetic medicine modalities, including monoclonal antibodies, multispecifics, proteins, conjugates, AAV, LNPs, and siRNA. The Principal Data Architect will shape the cloud-native data foundation that enables predictive and generative AI/ML solutions in discovery scientist workflows. This role owns the architecture, adoption, and continuous improvement of a scalable data platform that connects laboratory data across dozens of assays, supports machine learning development and deployment, and improves how scientific data is used across the organization. The position reports to the Head of AI/ML in BGM and serves as a trusted advisor to senior leadership. This is a technical leadership role on the individual contributor track, with potential to expand into people management in the future. It requires close partnership with wet lab scientists, ML engineers, software engineers, data engineers, automation teams, and data governance partners. The role is central to building a robust, resilient, and scalable data foundation for BGMs AI/ML strategy." That's about the role. Responsibilities: list bullet points after "Responsibilities". We have bullet list: Define and drive the architecture for a scalable, cloud-native data platform that supports AbbVies AI/ML strategy in BGM.; Design data models and integration patterns that connect datasets generated across multiple lab groups and establish certified datasets for downstream scientific, operational, and machine learning use.; Partner with wet lab scientists and automation engineers to maximize the value of data captured through lab automation workflows.; Work with data scientists and deployment engineers to ensure data pipelines support both model development and production deployment.; Advance FAIR data practices and data stewardship in alignment with BGM strategic priorities.; Champion connected data, data-as-a-product, and cloud-first architecture principles across the organization.; Partner with data infrastructure and governance experts to ensure data policies are implemented effectively.; Align BGM data infrastructure initiatives with broader AbbVie efforts such as Convergence and ARCH.; Communicate platform impact through user stories, metrics, and KPIs that show the value of the data platform to AbbVies therapeutic program pipeline. Qualifications: after "Qualifications" we have a block: "MS with 14+ years or PhD with 8+ years in machine learning, computer science, applied mathematics, data science, computational biology, or a closely related field.6+ years of experience in data architecture after completion of graduate studies, with a track record of designing enterprise data platformsGraduate degree in computer science, data science, computational biology, computational chemistry, computational biophysics, or a related field.Experience designing enterprise data platforms.Strong technical skills in data modeling, data integration, data storage solutions, data pipelines, and AI/ML integration.Production programming experience in SQL, Python, or Java.Experience building cloud data infrastructure on AWS, Azure, or GCP.Ability to work across wet lab and dry lab scientific workflows.Experience collaborating across functions and building stakeholder alignment.Strong communication and interpersonal skills.Ability to apply data governance principles in day-to-day decision-making.Experience in the pharmaceutical or biotechnology industry." We need to separate maybe into Requirements and Qualifications? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have qualifications content; maybe treat as Qualifications. Requirements could be similar? There's also "Preferred Experience leading cross-functional technical teams..." That could be Skills? Or maybe Requirements includes mandatory qualifications; Qualifications includes preferred? But we need to follow instruction: include a section only when posting has real specific content for it. We have content for Qualifications (the list). We also have "Preferred Experience leading cross-functional technical teams across reporting lines and multiplying their impact through best practices.Experience working in large, cross-functional R&D environments." That could go under Skills or maybe Requirements? We'll treat as Skills. We also have Work Environment: Hybrid role based in Worcester, MA. On-site presence required 3 days per week. This is an individual contributor role. That's Schedule? Actually schedule: hybrid, on-site 3 days per week. So we can put Schedule section with that. Benefits: "We offer a comprehensive package of benefits including paid time off (vacation, holidays, sick), medical/dental/vision insurance and 401(k) to eligible employees. This job is eligible to participate in our long-term incentive programs." Also note about compensation range etc. There's a compensation range description: "Applicable only to applicants applying to a position in any location with pay disclosure requirements under state or local law: The compensation range described below is the range of possible base pay compensation that the Company believes in good faith it will pay for this role at the time of this posting based on the job grade for this position. Individual compensation paid within this range will depend on many factors including geographic location, and we may ultimately pay more or less than the posted range. This range may be modified in the future." However no actual numbers given. Since no specific numbers, we should not create Pay section because it's not specific (just says range described below but not provided). The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated (package of benefits). So we include Benefits. Pay: not stated with numbers, so omit. Schedule: we have hybrid role based in Worcester, MA. On-site presence required 3 days per week. This is an individual contributor role. That's schedule info. So include Schedule. Now we need to output HTML fragment with headings

for each section. Use

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

  for prose. We need to decide which content goes to which section. About the role: prose paragraph(s) from overview. Responsibilities: list of duties. Requirements: maybe the mandatory qualifications? The qualifications block includes many items; we could split: Requirements = mandatory (MS/PhD + years experience etc). Qualifications = maybe the same? But we have both headings; we need to decide content for each. Could treat Requirements as the bullet list of mandatory qualifications (like degree, years experience, experience designing enterprise data platforms, technical skills, programming, cloud, wet/dry lab, collaboration, communication, data governance, pharma experience). Qualifications could be the preferred experience (leading cross-functional teams, large cross-functional R&D). Skills could be maybe technical skills list? But we already have technical skills in qualifications. Hmm. Better: Use Requirements for the mandatory qualifications (the block before "Preferred Experience"). Use Qualifications for the preferred experience? Or maybe Skills for technical skills list. Let's parse: Qualifications block: "MS with 14+ years or PhD with 8+ years in machine learning, computer science, applied mathematics, data science, computational biology, or a closely related field. 6+ years of experience in data architecture after completion of graduate studies, with a track record of designing enterprise data platforms Graduate degree in computer science, data science, computational biology, computational chemistry, computational biophysics, or a related field. Experience designing enterprise data platforms. Strong technical skills in data modeling, data integration, data storage solutions, data pipelines, and AI/ML integration. Production programming experience in SQL, Python, or Java. Experience building cloud data infrastructure on AWS, Azure, or GCP. Ability to work across wet lab and dry lab scientific workflows. Experience collaborating across functions and building stakeholder alignment. Strong communication and interpersonal skills. Ability to apply data governance principles in day-to-day decision-making. Experience in the pharmaceutical or biotechnology industry." Then after that: "Preferred Experience leading cross-functional technical teams across reporting lines and multiplying their impact through best practices. Experience working in large, cross-functional R&D environments." Thus we can assign: - Requirements: the mandatory qualifications (the first block). Could be list. - Qualifications: maybe the same? But we need to avoid duplication. Could treat Qualifications as the preferred experience? Actually "Qualifications" heading often includes both required and preferred. But we have separate headings; we can put mandatory under Requirements, and preferred under Qualifications. Skills could be maybe technical skills list? But we already have technical skills in the mandatory block. Could still list them under Skills as a separate list. But we must not invent content; we need to use what's there. If we split, we must ensure we don't lose any info. We can distribute. Option: Requirements: list of mandatory qualifications (the first block). Qualifications: list of preferred experience (the second block). Skills: maybe we could list technical skills (data modeling, etc.) but that's already in mandatory block; we could still list them under Skills but that would duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay? It says do not invent or summarize away detail. Duplication is not prohibited but might be redundant. Better to avoid duplication. So we could put technical skills under Skills, and not repeat them elsewhere. But then we would need to remove them from Requirements/Qualifications. However the mandatory block includes "Strong technical skills in data modeling, data integration, data storage solutions, data pipelines, and AI/ML integration." That's a skill. If we move it to Skills, we still preserve it. We just need to ensure we don't lose any other info. Thus we can structure: - About the role: prose. - Responsibilities: ul list. - Requirements: ul list of mandatory qualifications except the technical skills line (move to Skills). Also include degree, years experience, experience designing enterprise data platforms, production programming experience, cloud experience, ability to work across wet/dry lab, collaboration, communication, data governance, pharma experience. - Qualifications: ul list of preferred experience (leading cross-functional teams, large cross-functional R&D). - Skills: ul list of technical skills (data modeling, data integration, data storage solutions, data pipelines, AI/ML integration) plus maybe production programming languages? Actually production programming experience is also a skill; but we already have it under Requirements maybe. Could keep it under Requirements. Let's keep production programming experience under Requirements. Skills list: data modeling, data integration, data storage solutions, data pipelines, AI/ML integration. - Benefits: ul list of benefits (paid time off, medical/dental/vision insurance, 401(k), long-term incentive programs). - Schedule: prose about hybrid role, on-site 3 days per week, individual contributor. We must not include Pay. Now ensure we don't include boilerplate like company description, overview, additional information about compensation range, EEO, etc. Let's craft HTML. We'll start with

  About the role

  then

  ...

  . Then

  Responsibilities

  • ...
  ...
  . Then

  Requirements

  ...
  . Then

  Qualifications

  ...
  . Then

  Skills

  ...
  . Then

  Benefits

  ...
  . Then

  Schedule

  ...

  . Make sure to preserve all substantive information. Let's extract exact sentences. About the role paragraph: We'll combine the overview description: "Biotherapeutics and Genetic Medicine (BGM) sits within AbbVies Discovery Research organization and supports discovery and optimization across biotherapeutic and genetic medicine modalities, including monoclonal antibodies, multispecifics, proteins, conjugates, AAV, LNPs, and siRNA. The Principal Data Architect will shape the cloud-native data foundation that enables predictive and generative AI/