Specialist, Quality Control Analytical
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. Must include sections only when posting has real, specific content. Remove boilerplate etc. We need to parse the posting. Company Overview: description of company, but not necessarily a section heading? Could be "About the role"? Actually "Company Overview" is about the company, not role. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings. We have: - Position Summary: description of role: "The Specialist, Quality Control Analytical will provide testing support for various programs (fusion proteins, cell therapies and cancer vaccines), which can include but is not limited to, wet chemistry, chromatography (HPLC, Capillary Electrophoresis), spectroscopy (UV-Vis), and ELISA. The position will be responsible for providing testing support through In Process testing, and suitability for use testing, method development, optimizations, and investigational studies. The Specialist will undertake complex troubleshooting and investigations." That's about responsibilities. Could be under "Responsibilities" heading. - Essential Functions: list of duties: Provides testing support through In Process, and suitability for use testing; Provides support for method development, optimizations and investigational studies; Creates testing protocols and reports; Performs lab maintenance and lab support Functions including completing maintenance records and deliverables; Provides quality systems and documentation support and completes change controls, standard operating procedures (SOPs) and test method updates, and associated documents; Performs ad-hoc and cross-functional duties and/or projects assigned to support business needs and provide developmental opportunities. That's also responsibilities. - Education & Experience: Bachelor’s degree in Biochemistry or related discipline with 4+ years of experience in the Biotechnology industry required; or Master’s degree in Biochemistry or related discipline with 2+ years of experience in the Biotechnology industry required; Hands-on experience with HPLC and ELISA preferred; Must have experience working in cGMP laboratory. That's qualifications/requirements. - Knowledge, Skills, & Abilities: list of skills: Strong interpersonal, communication, organizational, and problem-solving skills; Working knowledge of QC testing requirements, methodology, and general equipment such as pH meter and analytical balance; Knowledge of cGMP, FDA, and USP regulations and a basic understanding of statistics; Ability to be flexible and manage multiple priorities in a fast-paced environment; Ability to thrive in an efficient, highly interactive, goal-oriented team environment; Knowledge of MS Word and Excel. That's skills. - Working Environment / Physical Environment: This position works on site in Dunkirk, NY; Flexibility in working schedule, i.e., off-hours; Exposure to onsite in-lab environment. That could be Schedule? Actually schedule info: Flexibility in working schedule, i.e., off-hours. Could be under Schedule heading. - The position is eligible for a discretionary bonus and equity award. The hourly base pay range for this position is below. The specific rate will depend on the successful candidate’s qualifications, prior experience as well as geographic location. $33.65 (entry-level qualifications) to $37.00 (highly experienced) per hour. That's Pay. - Benefits: list of benefits: Medical, Dental and Vision Plan Options; Health and Financial Wellness Programs; Employer Assistance Program (EAP); Company Paid and Voluntary Life/AD&D, Short-Term and Long-Term Disability; Healthcare and Dependent Care Flexible Spending Accounts; 401(k) Retirement Plan with Company Match; 529 Education Savings Program; Voluntary Legal Services, Identity Theft Protection, Pet Insurance and Employee Discounts, Rewards and Perks; Paid Time Off (PTO) includes: 11 Holidays; Exempt Employees are eligible for Unlimited PTO; Non-Exempt Employees are eligible for 10 Vacation Days, 56 Hours of Health Pay, 2 Personal Days and 1 Cultural Day. We need to include Benefits section only if posting has real specific content. It does. - Schedule: we have flexibility in working schedule, off-hours. Also maybe mention onsite. Could be schedule. - About the role: maybe we could use Position Summary as About the role. But we already used Responsibilities for duties. Could combine? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have content for: - About the role: maybe a brief overview of the role (Position Summary). Could be used. - Responsibilities: Essential Functions (list). Could also include Position Summary but we can split. - Requirements: Education & Experience (maybe also knowledge, skills?). But Requirements often includes education/experience. We'll put Education & Experience under Requirements. - Qualifications: maybe also includes knowledge, skills? But we have Skills separate. Could put Knowledge, Skills, & Abilities under Skills. - Skills: maybe we can put Knowledge, Skills, & Abilities under Skills. - Benefits: as above. - Pay: hourly range. - Schedule: flexibility in working schedule, off-hours; also onsite location maybe. We must not create sections with filler like "commensurate with experience". We have specific content. We must not repeat job title as heading. Not needed. We must not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to cut out the AI tools statement, equal opportunity statement, etc. Also remove "The application window is anticipated to close..." etc. Also remove "ImmunityBio uses artificial intelligence..." etc. Also remove "We are committed to equal employment opportunity..." etc. Also remove "ImmunityBio employees are as valuable..." etc? That's benefits description but we need to keep benefits specifics. The paragraph about benefits includes a lot of fluff but we can keep the list. The introductory sentences about benefits may be considered boilerplate? It says "We have built a resource of robust benefit offerings..." That's somewhat generic but still part of benefits description. Might be okay to keep but we could trim to just the list. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits intro is not exactly those categories, but could be considered fluff. However we need to preserve ALL substantive information; do NOT invent or summarize away detail. The benefit list is substantive; the introductory sentences are not substantive? They are somewhat generic but still part of the posting. Safer to keep them? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The introductory sentences are not substantive detail but they are not prohibited. However they might be considered boilerplate? Not exactly. I'd keep them but maybe we can keep them as a
before the list. Similarly, the company overview paragraphs may be considered "About the company" not required heading. Could we include them under About the role? Might be irrelevant. The instruction says use headings for sections like About the role, Responsibilities, etc. It doesn't forbid other headings, but we should prefer those headings. We could include a section "About the role" with the Position Summary. The company overview could be omitted as not required heading; but we must preserve ALL substantive information. If we omit company overview, we lose substantive info about the company. However the instruction says we should output only HTML fragment, not necessarily include all info if not under those headings? It says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep all substantive info from the posting. That includes company overview. But we don't have a heading for company overview; we could put it under a generic
without heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to include other headings if needed, but they gave examples. Safer to incorporate company overview into About the role? But About the role is about the role, not company. However we could treat About the role as including company overview? Might be misaligned.
Alternatively, we could create a section "About the company" using but not in the list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we could add other headings like "Company Overview". That would preserve info. However they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies we should use those headings for sections, but we could also use others if needed. However to be safe, we could fit company overview into About the role? Might be okay.
But we also have "Why ImmunityBio?" section which is also company overview/benefits of working there. That could be part of About the role or maybe we could incorporate into Benefits? Actually "Why ImmunityBio?" includes bullet points: Opportunity to join a publicly traded biopharmaceutical company..., Work with collaborative team..., Ability to join a growing company..., etc. That's more about the role/opportunity. Could be under About the role.
Thus we can create About the role section that includes company overview, why ImmunityBio, position summary.
Responsibilities: Essential Functions.
Requirements: Education & Experience.
Qualifications: maybe not needed separately if we have Requirements covering education/experience and Skills covering knowledge/skills. But we could have Qualifications as combination of education/experience and maybe preferred experience? However we already have Requirements for education/experience. Qualifications could be things like "Hands-on experience with HPLC and ELISA preferred; Must have experience working in cGMP laboratory". That's also qualifications. Could put under Requirements as well.
Skills: Knowledge, Skills, & Abilities.
Benefits: list.
Pay: hourly range.
Schedule: flexibility in working schedule, off-hours; also onsite location.
We must not create sections with filler like "commensurate with experience". We have specific.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce something like:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we could add other headings like "Company Overview". That would preserve info. However they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies we should use those headings for sections, but we could also use others if needed. However to be safe, we could fit company overview into About the role? Might be okay.
But we also have "Why ImmunityBio?" section which is also company overview/benefits of working there. That could be part of About the role or maybe we could incorporate into Benefits? Actually "Why ImmunityBio?" includes bullet points: Opportunity to join a publicly traded biopharmaceutical company..., Work with collaborative team..., Ability to join a growing company..., etc. That's more about the role/opportunity. Could be under About the role.
Thus we can create About the role section that includes company overview, why ImmunityBio, position summary.
Responsibilities: Essential Functions.
Requirements: Education & Experience.
Qualifications: maybe not needed separately if we have Requirements covering education/experience and Skills covering knowledge/skills. But we could have Qualifications as combination of education/experience and maybe preferred experience? However we already have Requirements for education/experience. Qualifications could be things like "Hands-on experience with HPLC and ELISA preferred; Must have experience working in cGMP laboratory". That's also qualifications. Could put under Requirements as well.
Skills: Knowledge, Skills, & Abilities.
Benefits: list.
Pay: hourly range.
Schedule: flexibility in working schedule, off-hours; also onsite location.
We must not create sections with filler like "commensurate with experience". We have specific.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce something like:
About the role
About the role
Company overview text...
Why ImmunityBio? ...
Position Summary: ...
But we need to avoid repeating the job title as heading. Not needed. We need to use- for any list of duties/requirements/benefits. So for Responsibilities we need a list. For Requirements maybe list? It's a combination of education/experience; could be list. For Skills list. For Benefits list. We need to preserve all substantive information. Let's extract exact sentences. Company Overview paragraph: "ImmunityBio is a vertically integrated commercial stage biotechnology company developing next-generation therapies that bolster the natural immune system to defeat cancers and infectious diseases. The Company’s range of immunotherapy and cell therapy platforms, alone and together, act to drive and sustain an immune response with the goal of creating durable and safe protection against disease. Designated an FDA Breakthrough Therapy, ANKTIVA is the first FDA-approved immunotherapy for non-muscle invasive bladder cancer CIS that activates NK cells, T cells, and memory T cells for a long-duration response. The Company is applying its science and platforms to treating cancers, including the development of potential cancer vaccines, as well as developing immunotherapies and cell therapies that we believe sharply reduce or eliminate the need for standard high-dose chemotherapy. These platforms and their associated product candidates are designed to be more effective, accessible, and easily administered than current standards of care in oncology and infectious diseases." Why ImmunityBio? paragraph: "Why ImmunityBio?