Senior Scientist (Membrane-based Chromatography)

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. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. Must not invent or summarize away detail. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Pay And Benefits section with pay range and benefits list. Also Work Environment, Job Type & Location, etc. We need to map content to appropriate sections. We have: - About the role: description paragraph after job title: "We are seeking a Lead Scientist to support the application development of our membrane-based chromatography products..." That's the role description. So we can put that under

About the role

with

. - Responsibilities: list of responsibilities bullet points. Use

• . - Requirements: maybe "Essential Skills" and "Additional Skills & Qualifications". Could combine into Requirements and Qualifications sections. The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Likely: - Requirements: essential skills (PhD/MS etc) maybe. - Qualifications: additional skills & qualifications (Master's etc). - Skills: maybe list of skills like hands-on experience, etc. But we have overlapping. Could treat "Essential Skills" as Skills section. But we also have "Additional Skills & Qualifications". Might be better to put essential skills under Skills, and qualifications under Qualifications. Requirements could be something like "Experience with downstream processing, chromatography..." but that's also skill. Given the instruction: "Prefer a few substantive sections over many thin ones." So we might combine similar content. We need to include sections only when posting has real specific content. The posting includes: - About the role (description) - Responsibilities (list) - Essential Skills (list) - Additional Skills & Qualifications (list) - Work Environment (travel, fast-paced) - Job Type & Location (Contract to Hire, Greenville, SC) - Pay And Benefits (pay range $48.00 - $48.00/hr, benefits list) - Workplace Type (fully onsite) - Application Deadline (Oct 2, 2026) - but we should remove application instructions? The instruction says remove application instructions. Deadline maybe considered part of posting but not instruction. Might keep as a short paragraph? Not sure. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Application Deadline could be considered application instruction? It's not exactly instruction to apply, but it's a deadline. Might be considered metadata; but we could keep as a short p under maybe a heading? There's no heading for deadline. Could include under a generic "Details" but not required. Safer to omit? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the deadline. But we don't have a heading for it; we could just put a

  after other sections. - About Actalent (company description) - that's boilerplate? It's about the company, not EEO. Might be considered substantive? It's generic but maybe keep? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This is not that. It's company overview. Could keep as a short paragraph under maybe "About the company"? But we don't have a heading for that. Could include under About the role? Might be redundant. Might be considered boilerplate but not explicitly excluded. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So company overview is not those. Keep. - Equal opportunity employer etc - that's EEO boilerplate, remove. - San Francisco Fair Chance Ordinance etc - legal boilerplate, remove. - Massachusetts Lie Detector - legal, remove. - Use of Artificial Intelligence (AI) - maybe legal? It's about hiring process; could be considered boilerplate; but not explicitly listed. Might be considered legal. Safer to remove. Thus we keep: About the role, Responsibilities, Essential Skills (maybe Skills), Additional Skills & Qualifications (maybe Qualifications), Work Environment, Job Type & Location, Pay And Benefits, Workplace Type, Application Deadline, About Actalent. Now map to headings: - About the role:

  About the role

  - Responsibilities:

  Responsibilities

  - Skills: maybe combine Essential Skills and Additional Skills & Qualifications? But we have separate headings for Skills and Qualifications. Could put Essential Skills under Skills, Additional Skills & Qualifications under Qualifications. Requirements maybe not needed if we have Skills and Qualifications. Could omit Requirements heading if no specific content distinct. But we could put "Requirements" as a heading for mandatory requirements (like PhD/MS, experience). However Essential Skills already includes that. Might be redundant. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Essential Skills and Additional Skills & Qualifications into one "Skills" section, and omit Qualifications. But we have a heading for Qualifications; we could still use it if we have content. Let's decide: We'll create: - Skills: list of essential skills (PhD/MS, experience, downstream processing, analytical methods, customer-facing, mentoring, etc.) - Qualifications: list of additional qualifications (Master's/PhD years, Bachelor's+10 years, Empower software, gels, people person, etc.) Thus we keep both. - Benefits:

  Benefits

  with list. - Pay:

  Pay

  with pay range. - Schedule: maybe not present; posting does not mention schedule (like full-time, part-time, shift). So we omit Schedule heading. - Work Environment: could be under a heading? Not in list; but we could include under a generic heading like "Work Environment" but not in allowed headings. The allowed headings are only those listed. So we must not create other headings. So we need to fit work environment info into existing headings. Could put under About the role? Or maybe under Responsibilities? Not ideal. Could put under a

  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 have other headings but they'd be non-standard. Safer to stick to allowed headings only. So we need to incorporate work environment info somewhere else, maybe as a

  under About the role or under Skills? But that would misrepresent. However the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples, not an exhaustive list; but likely they expect only those headings. To be safe, we can create a section for Work Environment using

  Work Environment

  even though not listed; but they said "e.g." meaning examples. So it's probably okay to use other headings if needed. However they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings; but they didn't forbid others. However they also said "Prefer a few substantive sections over many thin ones." So we could add Work Environment as a section if it has substantive content. It does. So we can include. Similarly Job Type & Location could be its own section. Application Deadline could be its own. About Actalent could be its own. Thus we will use headings for each substantive block. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. Now craft HTML. We'll produce:

  About the role

  We are seeking a Lead Scientist to support the application development of our membrane-based chromatography products. This role involves designing and executing complex experimental plans to generate high-quality application data, developing and optimizing analytical methods for biomolecule characterization, and translating scientific insights into customer-ready solutions. The position serves as a technical subject matter expert, collaborating closely with R&D, product development, manufacturing, and commercial teams to support technology transfer, product adoption, and customer success. In addition, the Lead Scientist provides technical leadership through mentoring junior team members, developing documentation and SOPs, and representing the company in technical presentations, conferences, and customer engagements.

  Responsibilities

  • Lead application development projects focused on downstream purification and membrane-based chromatography technologies.
  • Design, plan, and execute independent experimental programs to generate high-quality, application-relevant data.
  • Analyze and interpret complex datasets to inform product performance, application fit, and technical positioning.
  • Develop application workflows, protocols, and technical content to support product adoption.
  • Develop and implement robust analytical methods using HPLC, UPLC, fragment analyzers, gel-based assays, and related techniques for bioprocess and biomolecule characterization; provide training and technical guidance to team members.
  • Proactively generate and execute study plans to address technical and development concerns and challenges through innovative and meticulous characterization and troubleshooting efforts.
  • Develop and implement Standard Operating Procedures (SOPs) for new processes and products in collaboration with cross-functional teams.
  • Proactively generate scientific insights from literature and internally generated data, and effectively share knowledge and learnings with the team.
  • Partner with R&D, Product Development, Manufacturing, Marketing, and Sales teams to enable technology transfer and customer success.
  • Interface with customers to provide technical insights on product use and deliver application-level support in response to customer inquiries.
  • Lead and support technical presentations, application notes, and conference or customer engagements, acting as a technical representative as needed.
  • Mentor and provide technical guidance to junior scientists and team members.
  • Maintain clear, accurate experimental documentation and technical reports.

  Skills

  • PhD or MS in Chemical Engineering, Chemistry, Bioengineering, Biochemistry, Biology, or a related discipline with significant industry experience.
  • Strong experience in downstream processing, chromatography, purification, or bioprocessing applications.
  • Hands-on experience developing, validating, and applying analytical methods using HPLC, UPLC, fragment analyzers, and gel-based techniques.
  • Direct customer-facing experience.
  • Proven ability to mentor, train, and develop junior team members.
  • Ability to independently lead scientific projects and drive results.
  • Excellent data analysis, documentation, and communication skills.
  • Problem-solving expertise and conducting data-driven root cause analysis.
  • Experience working cross-functionally in a regulated or product-driven environment.
  • Strong communication skills and willingness to give presentations internally and externally.
  • Highly self-motivated, detail-oriented, and effective in a fast-paced, team-based laboratory environment.

  Qualifications

  • Master's (3-4 years industry experience) or PhD (1-2 years industry experience), or a Bachelor's with 10+ years, ideally from a biopharma experience with protein purification knowledge.
  • Experience with Empower software is a plus.
  • Secondary skills in running gels.
  • The ideal candidate should be a 'people person' willing to engage with customers and integrate well into a small team.