Pharmacy Technician - Sterile IV Compounding (4x10 schedule)

We need to output HTML fragment with sections: About the role? The posting includes a paragraph about CAPS, then Position Summary, Responsibilities, Expertise: Knowledge & Skills, Expertise: Qualifications, Schedule, Salary range, Benefits. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to decide which sections to include based on content. We have: - About the role: could be the Position Summary paragraph: "Pharmacy Technician is responsible for assisting in the preparation of sterile IV medications in a 503A compounding pharmacy under the direct supervision of a licensed pharmacist." Also the introductory paragraph about CAPS could be considered about the role? Probably we can put that as About the role. - Responsibilities: list of duties. - Requirements: maybe combine Expertise: Knowledge & Skills and Expertise: Qualifications? The instruction says use headings: Requirements, Qualifications, Skills. We need to decide which sections to include. We have Knowledge & Skills (Expertise: Knowledge & Skills) and Qualifications (Expertise: Qualifications -Education/Experience/Training/Etc). Also we have Schedule and Pay (Salary range) and Benefits. We must not create sections with filler like "commensurate with experience". We have actual content for Schedule, Pay, Benefits. Thus sections: About the role, Responsibilities, Knowledge & Skills (maybe Skills), Qualifications, Schedule, Pay, Benefits. But we must follow allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: position summary + company intro. - Responsibilities: list. - Requirements: maybe combine Knowledge & Skills? Actually "Requirements" could be the Knowledge & Skills section (requires working knowledge, etc). Or we could put Knowledge & Skills under Skills heading. But we have both Skills and Qualifications headings. Let's assign: - Skills: Knowledge & Skills (requires working knowledge, etc.) - Qualifications: Education/Experience/Training etc. - Requirements: maybe we could omit if no distinct content; but we need to include only when posting has real specific content. We could combine Knowledge & Skills into Skills, and Qualifications into Qualifications, and maybe not include Requirements if no separate content. However we have "Expertise: Knowledge & Skills" and "Expertise: Qualifications". So we can map Knowledge & Skills to Skills, Qualifications to Qualifications. Requirements could be omitted. But we must not create empty headings. So we will not include Requirements if we don't have distinct content. Thus sections: About the role, Responsibilities, Skills, Qualifications, Schedule, Pay, Benefits. Check each for content: - About the role: we have introductory paragraph about CAPS and Position Summary. We'll combine. - Responsibilities: list of duties. - Skills: Knowledge & Skills bullet points. - Qualifications: Education/Experience/Training etc. - Schedule: given. - Pay: Salary range. - Benefits: B. Braun offers excellent benefits package. We must use

• for any list of duties/requirements/benefits. For Skills and Qualifications, they are not necessarily lists but could be formatted as
  • . The instruction: "Use
    • for any list of duties/requirements/benefits, and

      for prose." So for Skills and Qualifications, if they are list-like, we can use

      • . For About the role, we can use

        . For Schedule, Pay, Benefits we can use

        or

        • if list. Benefits is a list: healthcare, 401(k), tuition reimbursement. So we can use
          • . Schedule: we have a sentence; could be

            . Pay: salary range;

            . Now we must not include boilerplate like EEO, navigation, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. Let's extract exact text. About the role: Combine: "CAPS®, part of the B. Braun Group of Companies in the U.S., is the nation's largest network of outsourcing admixture pharmacies, has been delivering high-quality, same-day, admixture services and solutions to hospitals and outpatient facilities for more than 28 years. Along with the nation’s largest 503A sterile injectable outsourcing network, CAPS offers industry-leading batch compounding on a national scale. Position Summary: Pharmacy Technician is responsible for assisting in the preparation of sterile IV medications in a 503A compounding pharmacy under the direct supervision of a licensed pharmacist." We'll put as

            maybe two paragraphs. Responsibilities: list: - Adheres to all CAPS policies and procedures - Prepares compounded sterile products using aseptic technique. - Assists in the setup of the compounding room, equipment, and supplies for preparation of compounded sterile solutions, using aseptic technique. - Performs general cleaning and maintenance duties as directed. - Participates in cleanroom product introduction activities. - Prepares records and monitors results for pharmaceutical quality assurance testing. - The job function listed is not exhaustive and shall also include any responsibilities as assigned by the Supervisor from time to time. - General: It shall be the duty of every employee while at work to take reasonable care for safety and health of himself/herself and other persons. We need to keep all. We'll put each as

          • . Skills (Knowledge & Skills): - Requires working knowledge of technical field/area of specialization. - Exercises general application of principles, theories and concepts. - Follows established procedures and guidelines. - Works under direct supervision and from detailed verbal and/or written instructions. - Uses established procedures to accomplish assigned task. - May require some limited judgement in resolving problems. - Contacts are primarily with direct supervisor, peers and subordinates. We'll put as
            • . Qualifications (Education/Experience/Training/Etc): - REQUIRED: Pharmacy Technician License issued by the Washington Board of Pharmacy - Preferred: National Pharmacy Certification through PTCB or NHA ExCPT - High school diploma/G.E.D or equivalent required. - cGMP training/experience desired, training will be provided - Aseptic processing training/experience desired, training will be provided We'll put as
              • . Schedule: - Schedule: (4x10) 10 hour shifts from 7:30am - 6pm. Work 4 days per week between Monday - Sunday w/ alternating weekends. Holidays/Overtime as needed We'll put as

                . Pay: - Salary range is $20.23 - $30.90/hr We'll put as

                . Benefits: - B. Braun offers an excellent benefits package, which includes healthcare, a 401(k) plan, and tuition reimbursement. We'll put as

                • maybe each benefit as separate li. We must not include the rest: "While performing the duties of this job, the employee is regularly required to stand..." etc. That's physical demands; could be considered part of Requirements? But we didn't include Requirements section. However that is substantive info about physical demands. Should we include it? The instruction: include a section ONLY when posting has real, specific content for it. We have physical demands content. Could be part of Requirements or maybe we could add a section "Requirements" for physical demands. But we already have Skills and Qualifications. The physical demands are not skills or qualifications; they are job demands. Could be placed under Requirements heading. Since we have a heading "Requirements" allowed, we could use that for physical demands. That would be appropriate. Thus we add a Requirements section with physical demands bullet list. Let's extract physical demands: "While performing the duties of this job, the employee is regularly required to stand. The employee frequently is required to use hands to handle or feel and reach with hands and arms. The employee must occasionally lift and/or move up to 50 pounds." Also there is sentence about targeted range etc. That's compensation details; we already have Pay. The sentence about targeted range etc is more about compensation; we could incorporate into Pay section maybe as a

                  but we already have salary range. The targeted range sentence is somewhat filler but contains info about factors considered. It's not boilerplate; it's substantive about compensation determination. We could include it in Pay section as additional

                  . But we must not include placeholder like "commensurate with experience". This is not placeholder; it's actual description. So we can add to Pay section. Thus Pay section: include salary range and the targeted range explanation. Let's extract that paragraph: "The targeted range for this role takes into account a range of factors that are considered when making compensation and hiring decisions; included but not limited to: skill sets; experience and training; licensure and certifications; and other business and organizational needs. The disclosed range estimate has not been adjusted for the geographic differential associated with the location at which the position may be filled. Compensation decisions are dependent on the facts and circumstances of each case. The range provided is a reasonable estimate." We'll include as

                  after salary range. Now Benefits: we have the sentence about benefits package. Also there is a line about "To learn more about B. Braun and our safety healthcare products or view a listing of our employment opportunities, please visit us on the internet at www.bbraunusa.com." That's navigation/link; we should remove as per instruction to remove cookie/navigation/legal/EEO etc. That's basically a link to website; it's navigation. Remove. Also "Through its “Sharing Expertise®” initiative, B. Braun promotes best practices for continuous improvement of healthcare products and services." That's maybe boilerplate? It's about company initiative; could be considered not essential to job posting; but it's substantive about company. Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories; it's about company initiative. Might be okay to keep? But it's not directly about the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. This is substantive about company but not about the job. However earlier we included company intro in About the role. This initiative is extra; could be considered part of About the role? Might be okay to include in About the role as additional sentence. But we need to decide if we keep it. It's not boilerplate like EEO; it's a specific initiative. I'd keep it in About the role. Then "We are an equal opportunity employer..." that's EEO boilerplate; remove. "Know Your Rights: Workplace Discrimination is Illegal, click here." remove. Thus final HTML fragment includes sections: About the role, Responsibilities, Skills, Qualifications, Requirements, Pay, Benefits, Schedule? Wait we have Schedule separate; we need to decide order. The allowed headings list includes Schedule. We'll include Schedule section. Thus sections: About the role, Responsibilities, Skills, Qualifications, Requirements, Pay, Benefits, Schedule. Check each for content: - About the role: includes company intro, position summary, Sharing Expertise initiative. - Responsibilities: list. - Skills: Knowledge & Skills list. - Qualifications: Education/Experience/Training list. - Requirements: Physical demands list. - Pay: salary range + targeted range explanation. - Benefits: list of benefits. - Schedule: schedule sentence. Now ensure we don't repeat job title as heading. We didn't. Now output only HTML fragment, no /, no markdown. We'll produce:

                  About the role

                  ...

                  etc. Make sure to escape any HTML special characters? The text includes ®, ©? We have "CAPS®". The ® is okay as is. Also “Sharing Expertise®” includes ® and curly quotes. We'll keep as is; but need to ensure we use straight