Service Operations Coordinator Lead - ONSITE

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content. Job posting includes intro paragraphs about company, mission, etc. That could be "About the role" or maybe "About the company". But we must use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. Let's parse: - About the role: description of role: Service Operations Coordinator Lead serves as primary liaison, day-to-day coaching, etc. Also "In This Role, You Will Have The Opportunity To Provide responsive customer support..." etc. So we can put that under About the role. - Responsibilities: list of duties: Provide responsive customer support by managing inquiries, quotes, orders, scheduling, equipment records, and service operations while ensuring data accuracy, compliance, and continuous process improvement. Lead medical exchange and service order operations, including order administration, third-party billing, audit/compliance support, equipment documentation, and resolution of complex processing and system issues. Drive operational excellence through KPI reporting, dashboard management, trend analysis, process improvement initiatives, and onboarding, training, and coaching of new associates. - Requirements: "The Essential Requirements Of The Job Include Associates Degree, Bachelor's degree preferred. 6+ years of experience in customer service, dispatching, service coordination, or order management. 3+ years of experience using ERP, CRM, or other business systems, such as SAP, Oracle, Microsoft Dynamics 365, NetSuite, Salesforce, or similar platforms." - Qualifications: maybe overlapping with requirements? Could treat as same? But we need separate sections only if content. Could put qualifications as "Associates Degree, Bachelor's degree preferred." but that's already in requirements. Might combine? However we need to follow instruction: include a section ONLY when posting has real, specific content for it. We can decide to put qualifications as same as requirements? Might be redundant. Better to treat "Qualifications" as education and experience? But we already have Requirements covering that. Could treat Qualifications as "Associates Degree, Bachelor's degree preferred." and Requirements as experience and systems. But the text lumps them together. We could split: Qualifications: Associates Degree, Bachelor's degree preferred. Requirements: 6+ years experience..., 3+ years experience using ERP... That seems reasonable. - Skills: maybe not explicitly listed. Could infer from responsibilities: customer service, dispatching, service coordination, order management, ERP/CRM, KPI reporting, dashboard management, trend analysis, process improvement, onboarding, training, coaching. But we should not invent. The posting does not have a separate "Skills" section with bullet list. It mentions experience using ERP, CRM, etc. Could treat those as skills. But we need to avoid inventing. However we can extract skills from the text: "customer service, dispatching, service coordination, order management", "ERP, CRM, or other business systems such as SAP, Oracle, Microsoft Dynamics 365, NetSuite, Salesforce", "KPI reporting, dashboard management, trend analysis, process improvement initiatives", "onboarding, training, and coaching". Those are skills. It's okay to list them as skills. Not inventing, just extracting. - Benefits: The posting mentions "Leica Microsystems, a Danaher operating company, offers a broad array of comprehensive, competitive benefit programs... Check out our benefits at Danaher Benefits Info. We offer a comprehensive package of benefits including paid time off, medical/dental/vision insurance and 401(k) to eligible employees." So we have benefits content. - Pay: "The hourly range for this role is $35.00-$39.00 per hour. 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." So we have pay. - Schedule: Not mentioned explicitly. There's mention of fully ONSITE at facilities in Deerfield, IL. That's location, not schedule. No schedule info. So we should NOT create Schedule section. We also need to include location? Not required as heading. Could fold into a short

maybe under About the role? But we can include location as a paragraph maybe under About the role or separate? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. Location is minor metadata; we could include a short p under About the role or maybe after responsibilities. But we can also drop it. However location is relevant; but we can include as a short p under About the role: "Location: Deerfield, IL (onsite)". That's minor metadata. We must remove boilerplate: EEO, legal, application instructions, etc. Also remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Structure: Use

for each section heading, then content: either

for prose,

• for lists. We need to decide which content is list vs prose. Responsibilities: list of duties ->
  • each duty. Requirements: list ->
    • . Qualifications: maybe list ->
      • . Skills: list ->
        • . Benefits: list ->
          • . Pay: could be prose

            with the range and bonus info. About the role: prose

            maybe multiple paragraphs. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract exact phrasing. About the role: The posting includes paragraphs before "The Service Operations Coordinator Lead serves as the primary liaison..." Also earlier paragraphs about company mission. Should we include those? They are about company, not role. But "About the role" heading expects role description. Could include the role description paragraphs. The earlier company description could be considered "About the company" but we don't have that heading. Could we include it under About the role? Might be okay but it's not role-specific. However we must preserve all substantive information; we could include it as a paragraph under About the role (makes sense). But we might also create a separate section? Not allowed headings beyond given list. So we can put company overview in About the role as introductory prose. Let's capture: First paragraph: "Bring more to life. Are you ready to accelerate your potential and make a real difference within life sciences, diagnostics and biotechnology? At Leica Microsystems, 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. Shape the future with us!" Second paragraph: "At Leica Microsystems, we have been shaping the future for over 175 years with groundbreaking optical and digital solutions. With a culture rooted in customer focus, innovation, and teamwork, we lead the market in microscopy, imaging, and analysis, unveiling the invisible and empowering our customers to build a better, healthier world. Joining Leica Microsystems means contributing to scientific discoveries and supporting surgeons in making critical decisions. Our advanced microscopes and AI-based image analysis solutions enable users to gain profound insights into development and engineering challenges. Here, you will work on meaningful projects alongside passionate colleagues, driving progress and pushing the boundaries of what’s possible. Learn about the Danaher Business System which makes everything possible." Then role description: "The Service Operations Coordinator Lead serves as the primary liaison between customers, Field Service Engineers, and internal teams, ensuring timely service execution and an outstanding customer experience. This position will provide day-to-day coaching and guidance to the Service Operations team, supports the manager in driving operational excellence, and serves as a key resource for escalations, process improvements, and team development. This position reports to the Sr. Customer Support Manager, is part of the Technical Service team, and will be fully ONSITE at our facilities in Deerfield, IL" Then "In This Role, You Will Have The Opportunity To Provide responsive customer support by managing inquiries, quotes, orders, scheduling, equipment records, and service operations while ensuring data accuracy, compliance, and continuous process improvement..Lead medical exchange and service order operations, including order administration, third-party billing, audit/compliance support, equipment documentation, and resolution of complex processing and system issues.Drive operational excellence through KPI reporting, dashboard management, trend analysis, process improvement initiatives, and onboarding, training, and coaching of new associates." Note there are some formatting issues (double periods). We'll keep as is. Now Responsibilities: we can break into three bullet points as above. Requirements: "Associates Degree, Bachelor's degree preferred. 6+ years of experience in customer service, dispatching, service coordination, or order management. 3+ years of experience using ERP, CRM, or other business systems, such as SAP, Oracle, Microsoft Dynamics 365, NetSuite, Salesforce, or similar platforms." We could split into bullets: Education, Experience, Systems experience. Qualifications: maybe we treat education as Qualifications, experience as Requirements. But we already used education in Requirements. Let's instead assign Qualifications: Associates Degree, Bachelor's degree preferred. Requirements: 6+ years experience..., 3+ years experience using ERP... That seems logical. Skills: list of skills: customer service, dispatching, service coordination, order management; ERP, CRM, SAP, Oracle, Microsoft Dynamics 365, NetSuite, Salesforce; KPI reporting, dashboard management, trend analysis, process improvement initiatives; onboarding, training, coaching. We could combine into bullet list. Benefits: "broad array of comprehensive, competitive benefit programs that add value to our lives. Whether it’s a health care program or paid time off, our programs contribute to life beyond the job." plus "We offer a comprehensive package of benefits including paid time off, medical/dental/vision insurance and 401(k) to eligible employees." We can list: paid time off, medical/dental/vision insurance, 401(k), health care program (maybe same as medical). We'll keep as bullet list. Pay: "The hourly range for this role is $35.00-$39.00 per hour. 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'll put in

            . Now we need to ensure we don't include boilerplate: EEO, legal, application instructions, etc. Remove those. Also remove duplicated lines: there may be duplicate sentences; we need to ensure we only include each piece once. Let's craft HTML. We'll start with

            About the role

            then

            containing the company overview and role description. Might be long; we can split into multiple

            for readability but not required. We'll include location as a short p maybe after role description: "

            Location: Deerfield, IL (onsite)

            " but that's minor metadata; we could fold into About the role paragraph. Better to include location as a short p under About the role. Now Responsibilities:

            Responsibilities

            • Provide responsive customer support by managing inquiries, quotes, orders, scheduling, equipment records, and service operations while ensuring data accuracy, compliance, and continuous process improvement.
            • Lead medical exchange and service order operations, including order administration, third-party billing, audit/compliance support, equipment documentation, and resolution of complex processing and system issues.
            • Drive operational excellence through KPI reporting, dashboard management, trend analysis, process improvement initiatives, and onboarding, training, and coaching of new associates.
            Qualifications:

            Qual