Senior Machine Learning & Computer Vision Engineer

We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about company, mission, etc. That could be "About the role" or maybe "About the company". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have: - Intro about company, mission, culture: could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for the introductory description. - Then responsibilities: The posting includes "In This Role, You Will Have The Opportunity To" then bullet-like paragraphs: Software Development & Architecture, Machine Learning & Computer Vision, Performance Optimization, Industrial Application Development, Collaboration. Those are responsibilities. So we can have a "Responsibilities" section with a

  • for each bullet. - Then "The Essential Requirements Of The Job Include" with subheadings: Education, Experience, Technical Skills, Domain Knowledge, Soft Skills. Those are qualifications/requirements. According to headings list, we have Requirements, Qualifications, Skills. We could combine: maybe "Requirements" for Education, Experience; "Qualifications" for Technical Skills, Domain Knowledge; "Skills" for Soft Skills? But we need to avoid thin sections. Perhaps we can have one "Requirements" section that includes all subpoints as
    • items, but we need to preserve structure? The instruction: Use
      • for any list of duties/requirements/benefits. So we can flatten. We need to preserve all substantive information. So we need to include Education, Experience, Technical Skills, Domain Knowledge, Soft Skills details. Could list them as separate
        • items, maybe with bold headings inside
        • ? But we cannot add extra tags beyond
          • and

            . We could embed headings inside

          • as plain text, e.g., "
          • Education: Bachelor’s degree...". That's okay as it's still inside
          • . The instruction didn't forbid other tags inside
          • , but to be safe we can just put plain text with the label. Similarly for Benefits: The posting mentions benefits: "Molecular Devices, a Danaher operating company, offers a broad array of comprehensive, competitive benefit programs..." then later: "We offer comprehensive package of benefits including paid time off, medical/dental/vision insurance and 401(k) to eligible employees." Also mentions bonus/incentive pay. So we have Benefits section content. Also Pay: "The annual salary range for this role is $111,500 – 133,000." and bonus eligibility. So we have Pay section. Schedule: Not mentioned (on-site role location Bellevue, WA, but schedule not given). So we should not create Schedule section. We must not include boilerplate like EEO, legal, accommodation contact, etc. Remove those. We must not include duplicated lines. We need to preserve all substantive info: company description, role responsibilities, requirements, qualifications, skills, benefits, pay. We need to avoid filler like "commensurate with experience" etc. Not present. We need to output only HTML fragment. Let's craft:

            About the role

            Bring more to life. Are you ready to accelerate your potential and make a real difference within life sciences, diagnostics and biotechnology? At Molecular Devices, one of Danaher’s 15+ operating companies, our work saves lives—and we’re all united by a shared commitment to innovate for tangible impact. You’ll thrive in a culture of belonging where you and your unique viewpoint matter. And by harnessing Danaher’s system of continuous improvement, you help turn ideas into impact – innovating at the speed of life. Join Molecular Devices and help drive scientific discovery for life science customers in academia, biotech, pharma, and government. Our automated and AI-enabled technology empowers researchers to tackle complex questions and gain deep insights, accelerating the development of safer, more effective therapeutics. As part of our team—rooted in collaboration, authenticity, and innovation—you’ll ultimately contribute to groundbreaking science that enhances lives globally and shapes a healthier future for all. Learn about the Danaher Business System which makes everything possible.

            Then responsibilities:

            Responsibilities

            • Software Development & Architecture: Design, develop, and maintain high-performance machine learning and computer vision applications tailored for life science imaging challenges. Architect robust, scalable, and maintainable software systems that integrate seamlessly with existing industrial workflows. Collaborate with cross-functional teams, including data scientists, bioinformaticians, and domain experts, to translate research prototypes into production-ready systems.
            • Machine Learning & Computer Vision: Develop and implement state-of-the-art algorithms (e.g., convolutional neural networks, object detection, segmentation) to process and analyze biological image data. Optimize existing machine learning models and computer vision pipelines for performance, accuracy, and scalability. Stay current with the latest research and advancements in computer vision, deep learning, and AI as they relate to life sciences.
            • Performance Optimization: Identify performance bottlenecks in software and implement optimization strategies to enhance processing speed and efficiency. Leverage parallel computing, GPU acceleration, and efficient data management techniques to ensure high throughput and low latency. Conduct rigorous testing and benchmarking to validate performance improvements and ensure software reliability in industrial environments.
            • Industrial Application Development: Ensure the software meets industrial standards for reliability, security, and compliance with regulatory requirements specific to the life science domain. Develop comprehensive documentation, including technical specifications, user guides, and maintenance procedures. Participate in code reviews, pair programming, and agile development practices to maintain high code quality and efficient development cycles.
            • Collaboration: Work closely with research teams and other stakeholders to understand user requirements and translate them into technical solutions. Contribute to a culture of continuous improvement by sharing best practices, tools, and techniques across the team.
            Then Requirements/Education/Experience etc. Could split into Requirements and Qualifications and Skills but we want few substantive sections. Perhaps we can have "Requirements" covering Education, Experience, Technical Skills, Domain Knowledge; and "Skills" covering Soft Skills. But we also have "Qualifications" heading available. Let's think: The posting has "Essential Requirements Of The Job Include Education: ... Experience: ... Technical Skills: ... Domain Knowledge: ... Soft Skills:". So we could map: - Requirements: Education and Experience - Qualifications: Technical Skills and Domain Knowledge - Skills: Soft Skills That seems reasonable and uses three headings. We need to ensure we don't create thin sections; each will have substantive content. Let's craft:

            Requirements

            • Education: Bachelor’s degree in Computer Science, Engineering, or a related field; Master’s or Ph.D. preferred.
            • Experience: 7+ years of professional software development experience, with a strong focus on industrial application development. Proven expertise in developing machine learning and computer vision solutions, preferably in the life sciences or a related field. Demonstrated experience in performance optimization techniques, including the use of GPU acceleration and parallel processing.

            Qualifications

            • Technical Skills: Proficiency in programming languages such as Python and C/C++. Extensive experience with machine learning frameworks and libraries (e.g., TensorFlow, PyTorch, OpenCV). Strong understanding of computer vision algorithms and image analysis techniques. Expertise in optimizing code for performance and scalability in high-demand industrial applications. Familiarity with software development best practices, version control systems (e.g., Git), and agile methodologies. Experience with cloud platforms (e.g., AWS, Google Cloud, Azure) is a plus.
            • Domain Knowledge: Understanding of life science imaging techniques (e.g., microscopy, medical imaging, high-content screening) and the associated data challenges. Knowledge of regulatory standards and data privacy requirements in the life sciences is an advantage.

            Skills

            • Soft Skills: Excellent problem-solving skills and attention to detail. Strong communication and collaboration abilities to work effectively with cross-disciplinary teams. Ability to manage multiple projects concurrently and deliver high-quality results under tight deadlines.
            Then Benefits:

            Benefits

            • Comprehensive, competitive benefit programs including health care, paid time off, medical/dental/vision insurance, and 401(k) for eligible employees.
            • Bonus/incentive pay eligibility.
            Then Pay:

            Pay

            The annual salary range for this role is $111,500 – $133,000. This is the range that we in good faith believe is the range of possible compensation for this role at the time of this posting. This range may be modified in the future. This job is also eligible for bonus/incentive pay.

            We should not include the note about wages not being considered until earned etc. That's boilerplate legal; remove. We should not include the "Check out our benefits at Danaher Benefits Info." That's maybe okay but it's a link; we can keep as part of benefits? It's not substantive detail; maybe we can drop as it's just a reference. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The link is not substantive detail; we can drop it. We should not include the "Note: No amount of pay is considered to be wages or compensation until such amount is earned, vested, and determinable." That's legal boilerplate; remove. We should not include the "Join our winning team today..." etc at end; that's marketing fluff but maybe substantive? It's more of a call to action; could be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The closing marketing paragraph is not exactly boilerplate but could be considered application instructions? It's not instructions to apply; it's just encouraging. Might be okay to keep but it's somewhat generic. However we already have an About the role section that covers similar content; we could drop the closing paragraph to avoid duplication. The instruction says preserve ALL substantive information; but if it's duplicated or generic fluff, maybe it's okay to drop? It's not duplicated exactly but similar to earlier. Safer to keep? The instruction says remove duplicated lines. Not duplicated exactly. But it's more of a closing marketing. I'd lean to keep it as part of About the role? But we already have About the role covering mission etc. The closing paragraph is: "Join our winning team today. Together, we’ll accelerate the real-life impact of tomorrow’s science and technology. We partner with customers across the globe to help them solve their most complex challenges, architecting solutions that bring the power of science to life. For more information, visit www.danaher.com." This