Sr Engineer, Emerging Device Technology
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. So we need to map content.
We have:
- Company Description: about AbbVie. Could be "About the company" but not listed as allowed heading? Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the role" could be used for overview of position. "Company Description" maybe not needed; but we could incorporate into About the role? Probably better to have "About the role" covering overview of position and maybe company description? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings. We need to decide which sections to include.
We have content for:
- Overview of Position (could map to About the role)
- Key Responsibilities (Responsibilities)
- Qualifications (Qualifications)
- Skills? Not explicitly listed but qualifications include skills; maybe we can combine.
- Benefits: Additional Information mentions benefits package: paid time off, medical/dental/vision insurance, 401(k), long-term incentive programs. So we can have Benefits section.
- Pay: Additional Information includes compensation range description but not actual numbers; it says "The compensation range described below is the range of possible base pay compensation..." but no actual numbers given. Since we must not create Pay section unless posting actually states them. It does not give numbers, just says range described below but not provided. So we should NOT include Pay section because no specific numbers. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits we have explicit mention, so include Benefits. Pay not given specific numbers, so omit.
- Schedule: not mentioned, omit.
- Requirements: Could be similar to Qualifications? Might be redundant. We could have Requirements section for things like travel, location flexibility? But we have qualifications and maybe requirements like "BS, MS, or PhD..." etc. That's qualifications. Could treat Requirements as same as Qualifications? But we need to avoid thin sections. Perhaps we combine Qualifications and Requirements into one Qualifications section. The instruction: "Prefer a few substantive sections over many thin ones." So we can have About the role, Responsibilities, Qualifications, Benefits. That's four sections.
We need to preserve all substantive information, not invent or summarize away detail. Must not omit details like location flexibility, travel, etc. So we need to include those details within appropriate sections.
Let's extract details:
Company Description: AbbVie mission, therapeutic areas, Allergan Aesthetics, website, social media. This is substantive; we need to preserve. Where to put? Could be part of About the role? Might be better to have a separate section but not allowed heading. Could we incorporate into About the role as a paragraph? The About the role section could include company description as context. That seems okay.
Overview of Position: details about role, responsibilities, etc. We'll put in About the role.
Key Responsibilities: bullet list.
Qualifications: bullet list (education, experience, skills, travel).
Benefits: bullet list (paid time off, medical/dental/vision insurance, 401(k), long-term incentive programs). Also note that compensation range described but no numbers; we omit pay.
Also note location flexibility: "* This position can also be based out of our South San Francisco, Irvine and Germany Locations". This is a note; we can include in About the role or Qualifications? Probably in About the role as a note.
Also note about travel: "Travel will be required, as necessary (10%-20%)". Include in Qualifications.
Also note about equal opportunity etc: boilerplate to remove.
We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we strip the EEO statements, the links, etc.
We must not include job ID/requisition numbers.
We must not repeat job title as heading.
Now produce HTML fragment:
About the role
About the role
... company description + overview + location flexibility ...
ThenResponsibilities
- ... each responsibility ...
Qualifications
- ... each qualification ...
Benefits
- ... each benefit ...
maybe within About the role. Benefits list: - paid time off (vacation, holidays, sick) - medical/dental/vision insurance - 401(k) to eligible employees - long-term incentive programs Also note about compensation range: we omit because no numbers. Now company description and overview: Company Description: "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." We need to fix spacing: "atwww.abbvie.com" should be "at www.abbvie.com". Also social media list missing spaces. We'll just keep as is but maybe add spaces for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. We can keep the exact text but we can fix obvious typos? The text has missing spaces; but it's part of the source. Should we preserve exactly? Probably we should keep as given, but we can add spaces to make it readable? The instruction says preserve ALL substantive information; not to invent or summarize away detail. Adding spaces is not inventing new info, just formatting. Might be okay. But safer to keep exactly as given? However the missing spaces make it hard to read but still substantive. I'd keep as is but maybe add a space after "at" and before "www". The original: "visit us atwww.abbvie.com." That's likely a typo; we could correct to "visit us at www.abbvie.com." That's still substantive info, just fixing a typo. I'd correct minor formatting. Similarly "Follow @abbvie onLinkedIn,Facebook,Instagram,XandYouTube." We'll add spaces: "Follow @abbvie on LinkedIn, Facebook, Instagram, X and YouTube." Now overview of position: The paragraphs after "Overview Of Position". We'll combine into About the role paragraph. Let's craft About the role paragraph: 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 at www.abbvie.com. Follow @abbvie on LinkedIn, Facebook, Instagram, X and YouTube. AbbVie's Device and Combination Product Development and Drug Delivery (DCPD) organization provides the expertise required to develop and advance drug delivery systems supporting AbbVie's biopharmaceutical portfolio. Within DCPD, the Landscaping & Platform Definition (L&PD) group leads front-end strategy and assessment activities focused on future delivery system needs across the pipeline. The team defines technical and business requirements, evaluates emerging delivery technologies, and conducts feasibility and fit-for-purpose assessments to identify the most viable solution pathways. The group assesses a broad range of delivery system technologies, including autoinjectors, patch pumps, continuous infusion systems, and connected delivery ecosystems. This work helps ensure AbbVie's delivery solutions align with pipeline, patient, clinical, and commercial needs while supporting long-term platform and portfolio strategies. As delivery system requirements continue to expand across AbbVie's pipeline, L&PD is growing its capability to assess, prioritize, and advance technologies with the strongest strategic and technical fit. In addition to supporting individual asset programs, the group also identifies scalable platform opportunities that may serve multiple pipeline applications. This role is intended for an individual with an understanding of drug delivery systems, familiarity with design control principles, and the ability to apply structured, strategic thinking to technology assessment, opportunity evaluation, and future delivery system definition in support of AbbVie's therapeutic pipeline. Overview Of Position: The Device Technology Horizon Engineer will play a key role in evaluating delivery system and device solutions that support AbbVie's therapeutic pipeline and contribute to improved patient outcomes. This role sits at the intersection of early needs assessment, technology evaluation, and strategic decision support, helping translate evolving therapeutic, clinical, and business needs into clear delivery system strategies and recommendations. Within the Device and Combination Product Development (DCPD) department and Landscaping & Platform Definition (L&PD) group, this individual will work cross-functionally with CMC, Asset Teams, Commercial, and external partners to identify and assess future delivery system opportunities for pipeline assets in early development. The role