Design Assurance Quality Engineer

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

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

• for lists of duties/requirements/benefits, and

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

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting: - Company Overview: This is prose about the company. Could be "About the company" or similar. - Job Description: This is a prose description of the role. Could be "About the role". - Responsibilities: A long list of bullet points (though they're not formatted as bullets in the text, they're separate lines). I should format as

  • . - Requirements: A list of requirements. Should be
    • . - Benefits: Listed at the end: "Medical/Dental/Vision Insurance, Short-Term Disability, Long-Term Disability, Life Insurance, Paid Vacation Days, Paid Holidays, and 401k." This is a list, so Benefits section with
      • . - Pay: The posting says "The salary estimates are estimates from this job board and not a guarantee of Biomerics’ salary range." This is not a real pay statement from the company, it's a disclaimer. So I should NOT create a Pay section. - Schedule: Not mentioned. The job type is "Full-time" but that's minor metadata. Could fold into a short

        or drop. The user says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." Job Type is minor metadata. I could include a short

        at the top or in a "Details" section? But the rules say use

        for section headings like Schedule. Since there's no schedule details, I won't create a Schedule section. I'll just mention full-time in a brief intro paragraph. Also, there's a line: "Please, No Recruitment Agency calls or emails (we are not using recruitment services for this or any other role posted)." This is boilerplate/application instruction, should be removed. Also: "Travel up to 30% to support Brooklyn Park, MN location." This is a requirement/detail. Could be included in Requirements or a separate "Travel" section? But the rules say only use headings like those listed. Travel could be part of Requirements or a note. I'll include it as a list item in Requirements. Now, structure: - Maybe start with a

        for company overview? But the rules say use

        for section headings. The company overview is substantive. Could be "About the company" or "Company overview". The user gave examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "About the company" is not listed but could be considered similar. However, the rule says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so other headings are allowed if they have real content. But the posting has a "Company Overview" section. I'll include it as a section with heading "Company Overview" or "About the company". I'll use "Company Overview" as it's in the posting. - Then "About the role" for the Job Description paragraph. - Then "Responsibilities" with the list. - Then "Requirements" with the list. - Then "Benefits" with the list. - No Pay, no Schedule. I need to ensure I don't duplicate the job title. The job title is not given in the text? The user didn't provide a job title. The posting starts with "Job Type Full-time Description Company Overview...". There's no explicit job title. The role is "Design Assurance Quality Engineer" from the Job Description. But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". So I should not include a heading with the job title. That's fine. Now, I'll write the HTML. First, Company Overview: prose, so

        Company Overview

        then

        ...

        But the company overview is multiple paragraphs. I'll combine into one

        or multiple

        . The rule says use

        for prose. I'll use a single

        with line breaks? Better to use multiple

        tags. But the rule says "use

        for prose". I'll use separate

        for each paragraph. The company overview text: "Biomerics is a world-class manufacturer and innovative polymer solutions provider for the medical device and biotech indus-tries. As a vertically integrated company, we specialize in designing, developing, and producing medical devices for diagnostic and interventional procedures. We are focused on next-genera-tion solutions for vascular access, electrophysiology, cardiac rhythm management, neurovascular, structural heart, and cardiovascular markets. At Biomerics, we are dedicated to our diverse employee base. We understand that a strong, skilled, and engaged workforce is the foundation of our continued success as a business. We strive to live up to Biomerics' values in all our interactions. It is an exciting time to be part of our collective team, and there is no limit to the impact that can be achieved here at Biomerics. We improve and advance the lives of our employees and the patients who depend on our products. At Biomerics, we believe in integrity, partnership, empowerment and accountability, trust, agility, teamwork, and excellence, and we care. Our team-oriented, customer-focused corporate culture prioritizes building strategic, mutually beneficial partnerships with customers and our team members." That's multiple sentences. I'll keep as one

        or split? I'll keep as one

        for simplicity. Next, Job Description: "The Design Assurance Quality Engineer provides Quality Engineering support for new product development (NPD) projects from concept through design transfer and commercialization, while also supporting sustaining engineering activities for existing products throughout their lifecycle. This position partners with Design Engineering, Manufacturing Engineering, Operations, Supplier Quality, Business Development, and Quality to ensure customer, quality, and regulatory requirements are appropriately incorporated throughout product development and ongoing product support. The Design Assurance Quality Engineer supports design controls, risk management, verification and validation, supplier and material qualification, design transfer, and product/process change activities in accordance with the Quality Management System (QMS) and applicable regulatory requirements. This position reports to the Site Quality Manager." I'll put under

        About the role

        and then

        with that text. Responsibilities: The list is long. Each line is a responsibility. I'll make each a

      • in a
        . The text has each responsibility on a new line. I'll copy them exactly. Requirements: The list under "Requirements". Each bullet point. I'll make
        • . Benefits: The list: "Medical/Dental/Vision Insurance, Short-Term Disability, Long-Term Disability, Life Insurance, Paid Vacation Days, Paid Holidays, and 401k." I'll split into separate
        • items. Also, there is "Travel up to 30% to support Brooklyn Park, MN location." This is under Requirements. I'll include as a requirement item. Now, the "Job Type Full-time" at the very top. That's minor metadata. I'll include a short

          at the beginning: "Job Type: Full-time" or just "Full-time position." But the rule says fold minor metadata into a short

          or drop it. I'll include a

          at the top: "Full-time position." Or maybe "Job Type: Full-time". I'll do a

          before sections. But the output should be only the HTML fragment. I'll start with a

          for the job type, then sections. However, the rule says "Do NOT repeat the job title as a heading". The job title is not in the text, but the role is Design Assurance Quality Engineer. I won't include it as heading. Now, I need to ensure I don't include any boilerplate: "Please, No Recruitment Agency calls or emails..." and "The salary estimates are estimates from this job board and not a guarantee of Biomerics’ salary range." These are removed. Also, "Biomerics offers the following benefits:" is part of benefits section. Now, write HTML. I'll structure:

          Full-time position.

          Company Overview

          Biomerics is a world-class manufacturer and innovative polymer solutions provider for the medical device and biotech industries. As a vertically integrated company, we specialize in designing, developing, and producing medical devices for diagnostic and interventional procedures. We are focused on next-generation solutions for vascular access, electrophysiology, cardiac rhythm management, neurovascular, structural heart, and cardiovascular markets. At Biomerics, we are dedicated to our diverse employee base. We understand that a strong, skilled, and engaged workforce is the foundation of our continued success as a business. We strive to live up to Biomerics' values in all our interactions. It is an exciting time to be part of our collective team, and there is no limit to the impact that can be achieved here at Biomerics. We improve and advance the lives of our employees and the patients who depend on our products. At Biomerics, we believe in integrity, partnership, empowerment and accountability, trust, agility, teamwork, and excellence, and we care. Our team-oriented, customer-focused corporate culture prioritizes building strategic, mutually beneficial partnerships with customers and our team members.

          About the role

          The Design Assurance Quality Engineer provides Quality Engineering support for new product development (NPD) projects from concept through design transfer and commercialization, while also supporting sustaining engineering activities for existing products throughout their lifecycle. This position partners with Design Engineering, Manufacturing Engineering, Operations, Supplier Quality, Business Development, and Quality to ensure customer, quality, and regulatory requirements are appropriately incorporated throughout product development and ongoing product support. The Design Assurance Quality Engineer supports design controls, risk management, verification and validation, supplier and material qualification, design transfer, and product/process change activities in accordance with the Quality Management System (QMS) and applicable regulatory requirements. This position reports to the Site Quality Manager.

          Responsibilities

          • Provide Quality Engineering and Design Assurance support throughout the new product development lifecycle, from concept and prototyping through design transfer and production for BBPK and BSLC sites.
          • Manage and support quality deliverables associated with the design process, including Design History File (DHF) and Engineering Project File documentation.
          • Participate as the Quality representative on cross-functional design and development teams to ensure customer requirements, product specifications, quality requirements, and applicable regulatory requirements are appropriately documented and addressed.
          • Collaborate with Design Engineers and Technicians in the development, review, execution, and documentation of verification and validation protocols and reports.
          • Support design control activities, including review of design inputs, design outputs, design reviews, verification, validation, and design transfer documentation.
          • Participate in the development and maintenance of DF