Quality Assurance Engineer

for prose. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to output only HTML fragment. Let's extract content: About the role: The Lasko Quality Assurance Engineer is responsible for determining why Lasko products fail after they reach the consumer. This position performs teardown and failure analysis on units returned to the Fort Worth distribution center, establishes root cause, and carries each issue into a documented corrective action with the function that owns the fix. This is an on-site position located at the Fort Worth, TX distribution center, supporting all Lasko brands and all manufacturing and supplier sources. That's a paragraph. Responsibilities: Essential Functions list: Returned Product Analysis, Root Cause and Corrective Action, Field Data Monitoring, Cross-Functional Support. Each has bullet points. We need to turn each essential function into a list item? The instruction: Use

• for any list of duties/requirements/benefits. So we can make a
  with each essential function as
  • containing its subpoints maybe as nested
    or as prose within
    • . We'll keep subpoints as separate sentences inside
    • maybe using
      inside? Simpler: each essential function as
      • and include its details as sentences. Requirements: Education/Experience: 3 to 5 years of experience in a manufacturing or product quality role required. Direct experience in failure analysis, product teardown, or returned-product evaluation required. Bachelor’s degree in Engineering, Manufacturing, Industrial Technology, or related technical field preferred. Experience with injection molding, mechanical and electrical assembly, or small motor products is an advantage. That's a list. Qualifications: Certifications And Special Requirements: Working knowledge of core quality tools: FMEA, CAPA. Familiarity with UL and ETL product safety requirements preferred. That's a list. Skills: Competencies And Abilities: list of abilities. We'll make a
        for each. Benefits: Why Join Lasko? includes flexible hours, hybrid work schedule for corporate team (but this role is on-site, still mention?), dog-friendly corporate headquarters, competitive salaries with bonus potential, comprehensive benefits package includes strong 401(k) match, wellness incentives, robust health coverage. Also mention culture values etc. We'll capture those. We should not include Pay or Schedule sections because no specific pay or schedule details given (flexible hours/hybrid schedule is mentioned but that's for corporate team; role is on-site, but still we could consider schedule info? It says flexible hours and a hybrid work schedule for our corporate team. Not specific to this role. So better not to include Schedule section as no explicit schedule for this role. Pay: competitive salaries with bonus potential is mentioned but not specific numbers; still it's a benefit. Could be considered Pay section? The instruction: 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. The posting does state "competitive salaries with bonus potential". That's somewhat specific? It's not a number but it's a statement about pay. However they said never create Pay section unless posting actually states them. It does state competitive salaries with bonus potential, which is a statement about pay. So we could include a Pay section with that sentence. But we also have Benefits section that includes benefits package. Could combine? The instruction prefers few substantive sections over many thin ones. We could include Benefits section that includes both benefits and pay info. But they have separate headings for Benefits and Pay. If we include Pay, we need to ensure we have real specific content. The phrase "competitive salaries with bonus potential" is somewhat vague but still a statement. Might be acceptable. However they said never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state competitive salaries with bonus potential, so we could include Pay. But we also have benefits details. To avoid many thin sections, maybe we combine pay and benefits into Benefits section, and omit Pay heading. The instruction: "Prefer a few substantive sections over many thin ones." So better to have Benefits section covering both compensation and benefits. We'll not create separate Pay section. Schedule: The posting mentions on-site position, flexible hours and hybrid work schedule for corporate team, but not specific schedule for this role. So we should not create Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Now produce HTML. We'll wrap each section in

        heading then content. For lists, use

        • . We need to preserve all substantive info, not lose any. Let's craft. About the role:

          The Lasko Quality Assurance Engineer is responsible for determining why Lasko products fail after they reach the consumer. This position performs teardown and failure analysis on units returned to the Fort Worth distribution center, establishes root cause, and carries each issue into a documented corrective action with the function that owns the fix. This is an on-site position located at the Fort Worth, TX distribution center, supporting all Lasko brands and all manufacturing and supplier sources.

          Responsibilities:

          Responsibilities

          then
          with each essential function as
          • . Inside each
          • we can include the subpoints as sentences. Essential Functions: - Returned Product Analysis: Perform teardown and failure analysis on units returned from retailers and consumers. Determine the failure mode and root cause of each unit investigated, and distinguish design, component, supplier, manufacturing, shipping, and consumer-use causes. Sample returned units at a frequency and quantity sufficient to represent the SKUs and sources under review. Maintain retention, labeling, and disposition of units held for investigation. Identify test and measurement equipment the site does not have and submit requests for it. - Root Cause and Corrective Action: Apply structured problem-solving methods to every investigation: 8D, 5-Why, Fishbone (cause and effect), Fault tree analysis, DMAIC. Document each investigation in a written failure analysis report stating the failure mode, the evidence, the root cause, and the recommended action. Recommend containment actions where a failure affects product already produced or already shipped. Verify the effectiveness of corrective actions using return data from the period following implementation. - Field Data Monitoring: Monitor return rate, retailer defective return data, warranty claims, and consumer service contacts by SKU and by platform, and identify changes that warrant investigation. Review consumer ratings and review content for early indications of product issues. Report emerging issues to the Manager, Field Quality within the timeframe defined for the issue class. - Cross-Functional Support: Provide failure analysis results to engineering, product integrity, supplier quality, and plant quality for use in design and process corrective action. Support Material Review Board activity for returned and nonconforming product. Support supplier corrective action requests with the physical evidence and analysis from returned units. We'll put each as
          • . Requirements:

            Requirements

            with items: 3 to 5 years of experience in a manufacturing or product quality role required. Direct experience in failure analysis, product teardown, or returned-product evaluation required. Bachelor’s degree in Engineering, Manufacturing, Industrial Technology, or related technical field preferred. Experience with injection molding, mechanical and electrical assembly, or small motor products is an advantage. Qualifications:

            Qualifications

            items: Working knowledge of core quality tools: FMEA, CAPA. Familiarity with UL and ETL product safety requirements preferred. Skills:

            Skills

            items: Ability to disassemble and diagnose mechanical and electrical consumer products, including motors, heating elements, controls, wiring, and molded plastic components. Proficiency with test and measurement equipment, including multimeters, dimensional measurement tools, and thermal measurement. Ability to read and interpret engineering drawings, GD&T, specifications, control plans, and PFMEAs. Ability to apply structured problem-solving methods (8D, 5-Why, fishbone, fault tree, DMAIC) without supervision. Proficiency with data analysis tools (Excel, Minitab, or similar). Ability to write a failure analysis report that a design engineer can act on. Ability to work independently at a site where no other quality engineering resource is located. Benefits:

            Benefits

            items: Flexible hours and a hybrid work schedule for the corporate team (promoting work-life balance). Dog-friendly corporate headquarters. Competitive salaries with bonus potential. Comprehensive benefits package that includes a strong 401(k) match, wellness incentives, and robust health coverage. Culture of GRACE with five core “Be” values: Growth Mindset — Be Bold; Recognition — Be Together; Authenticity — Be Real; Clear Communication — Be Clear; Extreme Ownership — Be Accountable. We could also include the mission statement etc. But that's more about Lasko; maybe we could include in About the role? Already we have a brief about role. The "About Lasko Products" and "Why Join Lasko?" includes mission and culture. We captured benefits and culture. Could also include a short paragraph about Lasko's mission etc. But we already included culture values. Might be enough. We must not include boilerplate like "About Lasko Products Love Your Air™ ..." That's substantive but could be included as a paragraph under Benefits or maybe a separate section "About the Company". But not in allowed headings list. We could incorporate into Benefits as prose. However the instruction: Use headings only from the list. So we cannot add a custom heading like "About Lasko". We could put that content under Benefits as a

            maybe. But we already have Benefits as a list; we could add a

            after the list. That's okay. Let's add a

            after the list describing Lasko's mission and history. But we must preserve all substantive info. The "About Lasko Products" paragraph includes history, mission, brands, etc. That's substantive. We'll include it as a

            under Benefits section (or maybe as a separate section but we don't have heading). We'll put it as a

            after the list. Similarly "Why Join Lasko?" includes flexible hours etc which we already captured. The rest about culture we captured. The paragraph about "At Lasko, we believe people do their best work..." we captured some. We'll include the rest as a

            . Let's craft Benefits section:

            Benefits

            • Flexible hours and a hybrid work schedule for the corporate team.
            • Dog‑friendly corporate headquarters.