Senior Laboratory Automation Scientist

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. The posting includes: - Intro about J&J (maybe not needed as section? Could be "About the role"? Actually "About Innovative Medicine" is a section. Could map to "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if content matches. We need to decide which sections have content. Content: - About Innovative Medicine: description of J&J Innovative Medicine, vision, etc. Could be considered "About the role"? Actually "About Innovative Medicine" is more about the division. Could map to "About the role". We'll include an

About the role

with that paragraph. - Then "We are searching for the best talent for a Senior Laboratory Automation Scientist to be located in Spring House, PA." That's maybe part of role description. - Then "Purpose: ..." That's responsibilities. - Then "You Will Be Responsible For" with bullet-like paragraphs (though not bullet list). We need to convert to

• for any list of duties/requirements/benefits. The responsibilities are described in paragraphs with bold headings (Workcell Architecture and Scientific Design, Inter-Workcell Integration and Data Provenance, Recovery, Governance, and Sustainment, Additional Responsibilities). We can treat each as a list item? Or we could keep as

  but instruction says use

  • for any list of duties/requirements/benefits. So we should make a list. Thus under Responsibilities heading, we will have
    with items for each major responsibility block. - Then "Qualifications/Requirements" section includes Education, Experience And Skills Required, Preferred Experience..., Other Travel..., etc. That's qualifications. We need to separate Requirements and Qualifications? The instruction lists both Requirements and Qualifications as possible headings. We could combine? Probably we should have a Requirements heading for mandatory qualifications, and Qualifications heading for preferred? But the posting lumps them. We could split: Requirements (Education, Experience And Skills Required) and Qualifications (Preferred Experience..., Other Travel...). Or we could just have one Qualifications section. Safer to follow instruction: include sections only when posting has real specific content. We have content for both Requirements and Qualifications. So we can make two sections:

    Requirements

    with Education and Experience And Skills Required (mandatory).

    Qualifications

    with Preferred Experience..., Other Travel..., etc. - Skills: The posting includes "Required Skills Preferred Skills:" at end but empty. No actual skills listed besides those in qualifications. Could we create a Skills section? Probably not, as no explicit skills list separate. We'll skip. - Benefits, Pay, Schedule: Not mentioned. So skip. Thus output HTML with sections: About the role, Responsibilities, Requirements, Qualifications. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, accommodation, etc. Also remove navigation, cookie, legal, duplicated lines. The posting includes EEO statement and accommodation request etc. Must remove those. Also remove "Learn more at jnj.com." and links? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO paragraph, accommodation request, working papers, etc. Also remove "Learn more at jnj.com." and "Learn more at https://www.jnj.com/innovative-medicine". Those are maybe not boilerplate but could be considered navigation? They are links; maybe we keep if they are part of description? The instruction says remove boilerplate, not necessarily all links. But "Learn more at jnj.com." is generic; could be considered boilerplate. Safer to remove. Also remove "Job Function R&D Product Development Job Sub Function R&D Electrical/Mechatronic Engineering Job Category Scientific/Technology All Job Posting Locations: Spring House, Pennsylvania, United States of America". That's metadata; we should fold minor metadata into a short

    or drop it. Since location is mentioned later in "located in Spring House, PA." We can drop the metadata line. We need to preserve all substantive information: purpose, responsibilities, qualifications, etc. Let's extract substantive paragraphs. Intro: "At Johnson & Johnson, we believe health is everything. Our strength in healthcare innovation empowers us to build a world where complex diseases are prevented, treated, and cured, where treatments are smarter and less invasive, and solutions are personal. Through our expertise in Innovative Medicine and MedTech, we are uniquely positioned to innovate across the full spectrum of healthcare solutions today to deliver the breakthroughs of tomorrow, and profoundly impact health for humanity." This is generic company description; could be considered boilerplate? It's not EEO but still maybe fluff. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not explicitly listed, but it's generic marketing. Might be considered boilerplate? Not sure. Safer to keep? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." This is substantive about company mission. Might be okay to keep as part of About the role. But we also have "As guided by Our Credo, Johnson & Johnson is responsible to our employees who work with us throughout the world. We provide an inclusive work environment where each person is considered as an individual. At Johnson & Johnson, we respect the diversity and dignity of our employees and recognize their merit." That's also generic EEO-like but not exactly EEO statement; still could be considered boilerplate. Might be removed? It's about work environment, could be considered benefits? Not explicit benefits. Might be considered fluff. I'd lean to remove generic fluff to keep focus on role. However the instruction only explicitly mentions removing cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The inclusive work environment paragraph is not EEO but could be considered similar. I'd keep it? Might be safe to keep as part of About the role. But we need to avoid filler like "commensurate with experience". Not present. Thus we will include About the role section with the company mission and inclusive environment paragraphs. Now Responsibilities: We'll list items: - Workcell Architecture and Scientific Design: Leading translation of scientific workflows into process maps, sample flows, consumable flows, method logic, instrument sequences, metadata needs, analytical outputs, data handoffs, and scientific decision points. Designing and deploying integrated workcells combining liquid handlers, plate handling devices, washers, centrifuges, incubators, readers, storage systems, barcode readers, labelers, analytical instruments, and orchestration software. Defining method transfer strategy from manual to automated execution, including pipetting approach, tolerance assumptions, deck layout, consumable selection, reagent stability, timing constraints, controls, and acceptance criteria. Leading UAT design for nominal workflows, edge cases, sample exceptions, data handoffs, intervention paths, recovery cases, and user acceptance. - Inter-Workcell Integration and Data Provenance: Owning upstream and downstream handoff requirements for assigned workcells, including labware compatibility, sample format, timing constraints, temperature or sterility constraints, storage conditions, queue logic, and data handoff expectations. Defining sample, labware, consumable, reagent, waste, intermediate product, and run state requirements for assigned workcells. Partnering with IT, data science, AI, and laboratory informatics teams to define metadata, sample lineage, experimental provenance, data integrity checks, file transfer expectations, and model-ready outputs. Supporting integration control documentation between workflows, workcells, orchestration layers, ELN, LIMS, GDB, data platforms, analytical systems, and vendor software. - Recovery, Governance, and Sustainment: Designing recovery logic for failed runs, interrupted workflows, missing samples, failed transfers, sample rescue, plate quarantine, rerouting, pause/resume situations, and manual interventions. Leading troubleshooting and root cause analysis for complex issues spanning method performance, liquid handling, consumables, assay response, scheduling, sample tracking, metadata, data capture, and user behavior. Supporting vendor selection, Tier 1 and Tier 2 coordination, FAT, SAT, UAT, risk assessments, readiness reviews, hypercare planning, training, and lifecycle support. Driving continuous improvement based on run metrics, failure mode analysis, user feedback, scientific output quality, throughput, hands-on time, and data completeness. - Additional Responsibilities: Support technology evaluations, proof-of-concept studies, workflow readiness assessments, user demonstrations, and vendor evaluations for future automation capabilities. Contribute to laboratory automation standards, workflow templates, data handoff expectations, training materials, and playbooks. Support audit, inspection, or quality documentation requests where automated scientific workflows intersect with regulated or quality driven environments. Participate in lessons learned and continuous improvement activities to improve future automation delivery and adoption. We need to ensure we don't lose any detail. Also include the "Purpose:" paragraph before responsibilities? Could be part of responsibilities as overview. We'll include as first list item maybe. Purpose: The Senior Laboratory Automation Scientist owns scientific automation readiness for one or more integrated workcells. The role translates complex biological, biochemical, analytical, and screening workflows into executable automated sequences that preserve sample identity, scientific intent, data context, and downstream decision value. The Senior Scientist will lead design, integration, qualification, optimization, and lifecycle support of integrated laboratory automation workcells for discovery and analytical workflows, with explicit responsibility for scientific operability, handoffs, method robustness, data provenance, exception recovery, user adoption and workflow readiness. This role is complementary to the Senior Automation and Robotics Engineer. The scientist owns the workflow, method, sample logic, data context, and user adoption; the engineer owns the physical system, machine behavior, robot motion, safety, serviceability, and engineering acceptance. We can include that as a list item as well. Now Requirements: Education and Experience And Skills Required. Education: A minimum of a Bachelor's degree in Biology, Biochemistry, Molecular Biology, Biotechnology, Analytical Sciences, Laboratory Automation, Engineering, Computer Science, or related field is required. An advanced degree is preferred. Experience And Skills Required: Bachelor’s degree with 6+ years, Master’s degree with 4+ years, PhD with 2+ years of relevant experience in laboratory automation, scientific automation, analytical automation, or workcell integration. Demonstrated understanding of laboratory workflows, sample handling, plate/tube formats, assay execution, consumable preparation, run documentation, and data capture. Hands-on or practical experience with automated liquid handlers or integrated laboratory automation equipment appropriate to the level of the role. Ability to translate scientific workflows into executable automated methods, worklists, run states, exception pathways, and user-facing procedures. Working knowledge of sample identity, labware identity, reagent identity, consumable state, barcode traceability, metadata capture, and downstream data requirements. Ability to collaborate with scientists, automation engineers, IT, data science, AI, EHS, facilities, vendors, and laboratory operations. Experience developing and implementing automated laboratory workflows or high-throughput methods. Experience with inter-workcell handoffs, method qualification, user training, exception recovery, technical documentation, and lifecycle support. We'll put that as list items under Requirements. Qualifications: Preferred Experience with ELN, LIMS, GDB, data lakes, request tracking, APIs, scripting, device drivers, scheduling logic, biosafety, contamination control, simulation, digital twin methods, FAIR data, or structured metadata. Experience with biologics discovery, protein production/purification, NGS, biophysics, cell-based assays, screening, analytical development, or protein characterization workflows. Experience with orchestration software such as Biosero Green Button Go, Cellario, Moment