BTS Senior Engineer, Technology I

We need to output HTML fragment with sections: About the role? Actually we have Company Description, Job Description, Responsibilities, Qualifications, Additional Information (benefits, pay). We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections when posting has real specific content. We have content for Responsibilities, Qualifications (Required and Preferred), Benefits (mentioned), Pay (compensation range described). Also maybe "About the role" could be from Job Description? The instruction: do NOT repeat the job title as a heading. Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include sections: About the role (maybe from Job Description paragraph), Responsibilities, Qualifications (maybe combine Required and Preferred), Benefits, Pay. Not include Requirements or Skills if not explicit separate. We have "Qualifications" includes required and preferred. Could treat as Qualifications section. Benefits: described. Pay: compensation range described. Schedule: not mentioned, so omit. We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, equal opportunity, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. Also remove "Company Description About AbbVie" maybe we can keep as part of About the role? Actually "Company Description" is separate but we can incorporate into About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities...). So we could have About the role section containing the company description and job description summary? But we must preserve all substantive information; we can include the company description as a paragraph under About the role. Also the job description paragraph about Sr. Engineer Technology... can be part of About the role. We must not repeat the job title as a heading. So we won't put "Sr. Engineer Technology" as heading. We need to output only HTML fragment, no /, no markdown fences. Let's extract content: Company Description: "About AbbVie AbbVie's mission is to discover and deliver innovative medicines and solutions that solve serious health issues today and address the medical challenges of tomorrow. We strive to have a remarkable impact on people's lives across several key therapeutic areas including immunology, oncology and neuroscience - and products and services in our Allergan Aesthetics portfolio. For more information about AbbVie, please visit us atwww.abbvie.com. Follow @abbvie onLinkedIn,Facebook,Instagram,XandYouTube." Job Description paragraph: "TheSr. EngineerTechnologyIenablesthe full lifecycle of AbbVie'sDigitalization of SoftwareLifeCycle from design and implementation through evidence collection, continuous monitoring, and inspection readiness. This is not a software testing or QA engineering role.This bridgesregulationwithtechnology functionsforIT governanceusingmodern tooling. This role calls for a quality and compliance professional who is deeply technology-aligned someone fluent in how CI/CD pipelines, source control platforms, test management systems, and artifact repositorieswork, and who uses that fluency to driveregulatoryexpectationthrough intelligent automation. The engineer translates between governance stakeholders and the engineering teams who build andmaintainthe tools." Note there are missing spaces due to formatting; we should preserve as is? Probably we should keep the text but maybe add spaces for readability? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The original text has missing spaces; we should keep it exactly as given? It might be okay to keep as is, but we could add spaces to make it readable? That would be altering. Safer to keep exactly as given, but it's ugly. However we could insert spaces where missing? That would be inventing? Not exactly; it's correcting formatting. Might be considered summarizing? I'd keep as is. Responsibilities list: many bullet-like sentences separated by periods. We need to put them in

• . The responsibilities are: - IT controls design assurance end-to-end design, implement, maintain, and continuously improve SLC framework across technology systems and platforms, applying a patient-centric, risk-based approach aligned with GAMP principles. - Drive controls automation identify opportunities to automate the collection, validation, and reporting of IT control evidence within CI/CD pipelines and integrated toolchains; embrace automation and electronic means over paper-based evidence, consistent with FDA/industry CSA guidance. - Leverage AI apply AI tooling to enhance control monitoring, trend analysis, and anomaly detection across regulated systems; understand the compliance and data integrity implications of self-learning systems and govern them accordingly. - Serve as the bridge compliance and technology teams translate between governance and regulatory requirements and the engineering teams responsible for tool configuration and pipeline design. - Partner with tool owners work directly with teams operating Jira, GitHub, JFrog, qTest, ServiceNow, and related platforms; embed controls at the source and ensure those tools produce the right evidence in the right form. - Maintain digital traceability own digital traceability records linking requirements, controls, system design elements, and verification evidence; ensure records are live, dynamic, and continuously audit-ready rather than static or paper-based. - Ensure data integrity by design apply ALCOA+ principles and data lifecycle controls across all governed systems. - Support audit and inspection readiness lead evidence preparation and coordinate remediation; ensure the team can respond confidently to regulatory inquiries supported by real-time, digital records. - Enable governance stakeholders surface interdependencies, communicate control status, and translate technical complexity into compliance-relevant language for leadership and governance audiences. - Contribute to continuous improvement support Validation 4.0 principles including quality by design, data integrity by design, and integrated environments; help evolve the controls assurance methodology as technology platforms and regulatory expectations change. We need to preserve all; we can split each sentence as a list item. Qualifications Required and Preferred: Required: - Bachelor's Degree with 6 years' relevant experience; Master's Degree with 5 years'; PhD with 0 years' - Demonstrated experience working in a regulated industry (pharmaceutical, medical device, or similar) - Fluency with modern software development toolchains GitHub, Jira, JFrog Artifactory, qTest, ServiceNow CMDB, and/or CI/CD platforms (Azure DevOps, AWS CodePipeline, or equivalent) - Ability to translate regulatory requirements into technical specifications, acceptance criteria, and control configurations - Experience embedding controls into DevOps workflows or software delivery pipelines - Comfort operating at the boundary between governance stakeholders and engineering teams able to communicate credibly in both directions - Ability to learn and work in a fast-paced environment Preferred: - Familiarity with AI systems in a regulated context including governance, validation, and data integrity considerations is a plus We can combine into Qualifications section with subheadings? Not required; we can just list all items, maybe separate required and preferred as separate
  with headings? But we cannot add extra headings not in list; but we could use

  to note "Required:" and "Preferred:" inside the section. That's okay. 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 short-term incentive programs." Pay: "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." We need to include the actual range? The posting didn't give numbers; it just says range described below but not provided. Actually there is no numeric range given. So we cannot include Pay section because no specific range. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated, so we can include Benefits. Pay: they mention compensation range described below but no numbers; it's not stated. So we should not include Pay section because no actual range. So we omit Pay. Schedule: not mentioned. Thus sections: About the role, Responsibilities, Qualifications, Benefits. We need to use

  for each section heading. We must not include boilerplate like EEO, equal opportunity, etc. Remove those lines at end. Now construct HTML:

  About the role

  About AbbVie AbbVie's mission is to discover and deliver innovative medicines and solutions that solve serious health issues today and address the medical challenges of tomorrow. We strive to have a remarkable impact on people's lives across several key therapeutic areas including immunology, oncology and neuroscience - and products and services in our Allergan Aesthetics portfolio. For more information about AbbVie, please visit us atwww.abbvie.com. Follow @abbvie onLinkedIn,Facebook,Instagram,XandYouTube.

  TheSr. EngineerTechnologyIenablesthe full lifecycle of AbbVie'sDigitalization of SoftwareLifeCycle from design and implementation through evidence collection, continuous monitoring, and inspection readiness. This is not a software testing or QA engineering role.This bridgesregulationwithtechnology functionsforIT governanceusingmodern tooling. This role calls for a quality and compliance professional who is deeply technology-aligned someone fluent in how CI/CD pipelines, source control platforms, test management systems, and artifact repositorieswork, and who uses that fluency to driveregulatoryexpectationthrough intelligent automation. The engineer translates between governance stakeholders and the engineering teams who build andmaintainthe tools.

  Then Responsibilities:

  Responsibilities

  • IT controls design assurance end-to-end design, implement, maintain, and continuously improve SLC framework across technology systems and platforms, applying a patient-centric, risk-based approach aligned with GAMP principles.
  • Drive controls automation identify opportunities to automate the collection, validation, and reporting of IT control evidence within CI/CD pipelines and integrated toolchains; embrace automation and electronic means over paper-based evidence, consistent with FDA/industry CSA guidance.
  • Leverage AI apply AI tooling to enhance control monitoring, trend analysis, and anomaly detection across regulated systems; understand the compliance and data integrity implications of self-learning systems and govern them accordingly.
  • Serve as the bridge compliance and technology teams translate between governance and regulatory requirements and the engineering teams responsible for tool configuration and pipeline design.
  • Partner with tool owners work directly with teams operating Jira, GitHub, JFrog, qTest, ServiceNow, and related platforms; embed controls at the source and ensure those tools produce the right evidence in the right form.
  • Maintain digital traceability own digital traceability records linking requirements, controls, system design elements, and verification evidence; ensure records are live, dynamic, and continuously audit-ready rather than static or paper-based.
  • Ensure data integrity by design apply ALCOA+ principles and data lifecycle controls across all governed systems.
  • Support audit and inspection readiness lead evidence preparation and coordinate remediation; ensure the team can respond confidently to regulatory inquiries supported by real-time, digital records.
  • Enable governance stakeholders surface interdependencies, communicate control status, and translate technical complexity into compliance-relevant language for leadership and governance audiences.
  • Contribute to continuous improvement support Validation 4.0 principles including quality by design, data integrity by design, and integrated environments; help evolve the controls assurance methodology as technology platforms and regulatory expectations change.
  Qualifications:

  Qualifications

  Required:

  • Bachelor's Degree with 6 years' relevant experience; Master's Degree with 5 years'; PhD with 0 years'
  • Demonstrated experience working in a regulated industry (pharmaceutical, medical device, or similar)
  • Fluency with