Field Applications Specialist - West Region

We need to output HTML fragment with sections: About the role? The posting includes many paragraphs. We need to extract sections: About the role (maybe summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, duplicated lines, application instructions. Must preserve all substantive info. We need to decide what content goes where. The posting includes: - Intro about Waters and BD (some fluff). Might be considered "About the role"? Actually "About the role" could be the Position Summary and Role Purpose. - Responsibilities: list of bullet points under "Key Responsibilities" with subheadings: Customer Engagement & Training, Post-Sale Technical Support & Expertise, Workflow Optimization & Adoption, Customer Success & Retention, Expansion & Opportunity Identification, Cross-Functional Collaboration. - Required Qualifications & Experience: list bullet points. - Preferred: list bullet points. - Work Environment & Travel: paragraph. - Why Waters: paragraph. - As Part Of Waters, You Will: bullet list. - Who Thrives In This Role: bullet list. - Who This Role Is Not For: bullet list. - Compensation: paragraph with pay range. - Additional info: "Required Skills Optional Skills Primary Work Location USA CA - Milpitas 155 Additional Locations Work Shift ..." plus benefits mention. We need to include Pay section if posting actually states them: yes compensation paragraph gives base pay range $95,600 - $153,000 USD Annually plus incentives. So include Pay section. Schedule: Not explicitly stated; maybe travel 60-70% etc. Not schedule like shift. No explicit schedule. So we should not create Schedule section. Benefits: The posting mentions "Total Rewards program" and "competitive package of compensation and benefits programs" but no specific benefits listed. It says "You can learn more on our career site under 'Our Commitment to You.'" That's vague. No specific benefits like health, 401k, etc. So we should not create Benefits section unless specific content. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits not stated specifically, so omit. We need to include sections: About the role (maybe Position Summary + Role Purpose), Responsibilities, Requirements (maybe Required Qualifications & Experience), Qualifications (maybe Preferred?), Skills (maybe Required Skills? but not listed explicitly; there is "Required Skills Optional Skills" but no list). Could combine Required Qualifications & Experience as Requirements, and Preferred as Qualifications? Or we could have Requirements and Qualifications separate. The instruction: prefer a few substantive sections over many thin ones. So we could combine Required and Preferred into Qualifications? But we have both Required and Preferred; we could have Requirements (Required) and Qualifications (Preferred). Or we could have Requirements (Required Qualifications & Experience) and Skills (maybe from "Required Skills Optional Skills" but not detailed). Since there is no explicit skill list, maybe we skip Skills. We also have "Work Environment & Travel" could be part of About the role or separate? Could be its own section but not in list of allowed headings? Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Work Environment & Travel not allowed; we could incorporate into About the role or Responsibilities? Probably About the role includes summary and work environment. We also have "Why Waters", "As Part Of Waters, You Will", "Who Thrives In This Role", "Who This Role Is Not For". Those could be part of About the role or maybe we could omit as they are fluff? But we must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that info somewhere. Could be included in About the role section as prose. Thus About the role section could contain: Position Summary, Role Purpose, Why Waters, As Part Of Waters You Will, Who Thrives In This Role, Who This Role Is Not For, Work Environment & Travel. But we must not include filler like "commensurate with experience". Not present. We need to format with

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive info: that includes bullet points under Responsibilities, Required Qualifications & Experience, Preferred, etc. We need to avoid duplication: there may be duplicated lines (maybe some repeated). We'll need to check. Let's extract content. First, intro paragraphs about Waters and BD: Might be considered fluff but substantive? It describes company. Could be part of About the role. We'll include. Now, Position Summary: "Enable science. Drive adoption. Deliver customer outcomes. At Waters, Field Applications Specialists are critical to ensuring customers realize the full value of their investment through expert scientific engagement, application guidance, and workflow optimization. Operating at the intersection of science and customer success, you guide users from onboarding through long-term adoption—translating complex technologies into meaningful scientific and operational outcomes. This role goes beyond troubleshooting. It requires the ability to understand customer workflows, deliver impactful training, and proactively drive utilization and adoption. You will partner closely with commercial, service, and marketing teams to strengthen customer outcomes, increase product adoption, and uncover opportunities for growth. This is a high-impact role where scientific expertise, customer engagement, and execution directly influence utilization, customer retention, and long-term value creation." Role Purpose: "As part of the Waters Biosciences division, ensure successful customer onboarding, product adoption, and sustained success by providing high-impact technical training, workflow optimization, and application expertise that enables customers to achieve their desired outcomes." Key Responsibilities: bullet list with subheadings. We need to turn each bullet into

• . The subheadings could be part of the li text or we could keep them as bold? But we just need to output list items; we can include the subheading as part of the li text. Let's extract each bullet: Under Customer Engagement & Training: - Lead customer onboarding to ensure a seamless transition from purchase to implementation - Deliver high-quality, application-focused training tailored to customer workflows and expertise levels - Educate customers on best practices to maximize instrument and application performance - Support initial setup, validation, and readiness of customer workflows Post-Sale Technical Support & Expertise: - Provide advanced application support and troubleshooting across instruments and workflows - Partner with customers to resolve complex technical challenges efficiently - Serve as a trusted scientific advisor for ongoing application needs - Escalate and coordinate resolution of complex issues with internal teams Workflow Optimization & Adoption: - Drive utilization through proactive engagement and scientific consultation - Advise customers on optimizing workflows and improving outcomes - Identify gaps and recommend best-practice solutions - Enable customers to achieve measurable success with technologies and reagents Customer Success & Retention: - Strengthen customer satisfaction and long-term retention through consistent engagement - Reinforce value realization and ensure achievement of intended outcomes - Build strong, trusted relationships with scientific stakeholders - Support broader customer success initiatives aligned to business objectives Expansion & Opportunity Identification: - Identify opportunities to expand application usage and workflow breadth - Surface unmet needs for additional products, reagents, or capabilities - Partner with Account Managers and Technical Sales Specialists to support growth opportunities - Contribute insights to territory and account development strategies Cross-Functional Collaboration: - Partner closely with commercial, technical sales, service, and marketing teams - Support coordinated, account-based customer engagement strategies - Provide field insights to inform product development and training programs - Contribute to a collaborative, team-based customer success model Now Required Qualifications & Experience: - Bachelor’s degree in life sciences or related field - Hands-on experience with flow cytometry applications and cell sorting - Strong troubleshooting capabilities across complex workflows - Ability to translate scientific concepts into practical application - Strong training, communication, and presentation skills - Valid driver’s license with at least 3 years of driving history - Ability and willingness to travel extensively (60–70%), including multi-day overnight travel Preferred: - Advanced degree in life sciences or related field - Experience with spectral flow cytometry - Experience operating and troubleshooting cell sorters - Prior customer-facing application support or training experience - Familiarity with FlowJo, Infinicyt, OMIQ, or FCS Express - Experience in workflow optimization and method development - Experience working cross-functionally in commercial or field environments Work Environment & Travel: - Field-based role with frequent on-site and remote customer engagement - Travel driven by customer and business needs Why Waters: - Waters plays a critical role in advancing scientific discovery and improving human health. Our teams partner with leading organizations across Pharma, Biotech, Academic, and Government sectors to solve complex scientific challenges. As Part Of Waters, You Will: - Enable customers to achieve meaningful scientific outcomes - Work with innovative technologies and applications - Collaborate across scientific and commercial teams - Directly contribute to customer success and long-term value creation Who Thrives In This Role: - Scientists passionate about training, teaching, and enabling others - Customer-centric professionals who build long-term scientific partnerships - Problem-solvers who enjoy optimizing workflows and applications - Collaborative partners who work effectively across teams - Self-driven individuals committed to delivering high-impact field engagement Who This Role Is Not For: - Individuals seeking non-customer-facing or purely transactional roles - Those uncomfortable with travel and field-based engagement - Candidates who prefer reactive rather than proactive customer interaction Compensation: - The expected Base Pay Range for this role is $95,600 - $153,000 USD Annually plus incentives. Final compensation will be determined based on experience, skills, and geographic location. Candidates whose job duties will be physically performed within unincorporated Los Angeles County limits: All qualified Applicants with arrest or conviction records will be considered for employment in accordance with the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act. BD abides by any and all laws or regulations that impose restrictions or prohibitions for hiring applicants with criminal histories for posted positions. We also have "Required Skills Optional Skills Primary Work Location USA CA - Milpitas 155 Additional Locations Work Shift ..." plus benefits mention. This seems like metadata; we can drop as per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. This is minor metadata; we can drop it or include as short p. Probably drop. We also have "At BD, we reward, support and develop our associates through our comprehensive Total Rewards program..." That's benefits-ish but vague; we can drop as not specific. We must not include EEO boilerplate etc. So we need to remove all Equal Opportunity paragraphs, etc. Now we need to decide sections. We could have:

  About the role

  containing: intro paragraphs about Waters and BD, Position Summary, Role Purpose, Why Waters, As Part Of Waters You Will, Who Thrives In This Role, Who This Role Is Not For, Work Environment & Travel. But that may be long; but allowed. Alternatively we could split into About the role (summary) and maybe a separate section for "What Success Looks Like"? Not in allowed headings. So we incorporate. We need to ensure we don't create sections with filler. All content we include is substantive. Now we need to output only HTML fragment, no /, no markdown. We'll produce:

  About the role

  ... combined prose ...

  Then

  Responsibilities

  ...
  Then

  Requirements

  ...
  (for Required Qualifications & Experience) Then

  Qualifications

  ...
  (for Preferred) Then

  Pay

  ... compensation paragraph ...

  We should not include Benefits or Schedule. Check if any list items are duplicated: