Key Account Quality Engineer

We need to output HTML fragment with sections: About the role? Actually we have "Position Summary" and "Key Responsibilities", "Required Qualifications", "Preferred Qualifications (Not Required)", "Key Performance Indicators". Also maybe "Travel Requirements". 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 (the page already shows it) and 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. Thus we need to decide which sections to include. The posting includes: About Company (company description). Position Summary (maybe "About the role"?). Key Responsibilities (Responsibilities). Required Qualifications (Requirements/Qualifications). Preferred Qualifications (maybe "Preferred Qualifications" but not required). Travel Requirements (maybe "Travel" but not listed as a standard heading; we could include under "Schedule"? Not exactly. Travel is not pay/schedule/benefits. Could be a separate section like "Travel Requirements". But the instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, not exclusive. However we should prefer a few substantive sections over many thin ones. Could combine some. We have a lot of content: About Company (company description) maybe not needed as a section? Could be "About the company" but not in list. Might be okay to include as a

  before sections? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It doesn't forbid a company description heading. But we should keep sections minimal. We could have sections: About the role (Position Summary), Responsibilities (Key Responsibilities), Qualifications (Required Qualifications), Preferred Qualifications (maybe as part of Qualifications?), Travel Requirements (maybe as its own section), Key Performance Indicators (maybe as a section). But that's many sections. We could combine Required and Preferred Qualifications into one "Qualifications" section with subpoints? But we need to preserve all substantive info; we can list both required and preferred under same section using

  • and maybe mark preferred. Travel Requirements: we could include under "Schedule"? Not exactly. Travel is not schedule. Could be its own heading "Travel". But instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Travel not listed but could be considered under "Schedule"? Not really. However we could include Travel as a

    inside Responsibilities or Qualifications? Probably better to have its own section "Travel". The instruction says "include a section ONLY when the posting has real, specific content for it". Travel has specific content: Frequent travel (30–50%) across North America. So we should include a section for Travel. Key Performance Indicators: also specific content; could be a section "Performance Metrics" or "Key Performance Indicators". Not in the example list but we can still use

    . The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, just gives examples. So we can add. Thus final HTML: series of

    headings with content. We need to use

    • for any list of duties/requirements/benefits. For prose, use

      . We must preserve all substantive information. Let's extract. About Company: description paragraph. We'll put as

      maybe under a heading "About Company"? Not in examples but okay. Could be first

      before any heading? The instruction says output only HTML fragment; we can start with a

      about company. But they said "Prefer a few substantive sections over many thin ones." Maybe we can combine About Company into a section "About the company". But we can also just put it as a

      before sections. But we need to avoid duplication: The posting includes "About Company Minth Group stands as a global leader..." We'll keep that. Position Summary: "The Quality Engineer is responsible for ensuring customer satisfaction through effective quality management, rapid response to issues, and proactive continuous improvement. This role serves as a key liaison between Minth production plants and OEM customers (GM, Ford, Stellantis and other OEMS that may be located in North America), supporting corrective actions, customer visits, scorecard performance, and plant quality alignment across North America." We'll put under heading

      About the role

      with

      . Key Responsibilities: list of bullet points. We'll put under

      Responsibilities

      with
      • each. Required Qualifications: list: Bachelor’s Degree in Engineering (Mechanical, Industrial, Manufacturing, or related field) Or 5 to 10 years experience in automotive quality. 5+ years of automotive quality engineering experience Experience with OEM customers (GM, Ford, Stellantis required) Strong background in customer-facing roles Technical Skills Knowledge of IATF 16949 Experience with Automotive Core Tools (APQP, PPAP, FMEA, SPC, MSA) Experience with customer portals (preferred) Proficiency in Microsoft Office Soft Skills Strong communication and presentation skills Excellent problem-solving ability Ability to manage multiple priorities High accountability and sense of urgency Strong customer focus We need to preserve all. Could separate into Technical Skills and Soft Skills subheadings? But we can just list as
        • items. Preferred Qualifications (Not Required): ASQ Certified Quality Engineer (CQE) Six Sigma Green Belt or Black Belt Experience in metal or plastics manufacturing Warranty analysis experience Travel Requirements: Frequent travel (30–50%) across North America Key Performance Indicators: Customer PPM performance Scorecard ratings Corrective action closure timing Warranty claim reduction Customer satisfaction We'll output sections: About the role, Responsibilities, Qualifications (maybe combine required and preferred?), Travel, Performance Metrics. But we need to avoid thin sections. Travel is just one line; could be included under Responsibilities? Not really. Could be a

          under Responsibilities? But it's a separate aspect. Could be included under "Schedule"? Not exactly. However we could make a section "Travel" with a

          . That's thin but it's specific content; instruction says prefer a few substantive sections over many thin ones. Travel is thin but still substantive; we could combine Travel into Responsibilities as a bullet? It is a requirement, not a responsibility. Could be under Qualifications as a bullet? Travel requirement is not a qualification but a job condition. Could be under "Requirements". Might be okay to add a bullet under Qualifications: "Willingness to travel frequently (30–50%) across North America". That would preserve info and avoid extra section. Similarly, Key Performance Indicators could be under Responsibilities? They are metrics used to evaluate performance; could be under a section "Performance Expectations". But we could also add a section "Key Performance Indicators". That's also thin but maybe okay. We need to decide. Given instruction: "Prefer a few substantive sections over many thin ones." So we should try to minimize sections. Perhaps we can have three sections: About the role, Responsibilities, Qualifications (including required, preferred, travel, KPIs). But we need to keep the info clear. We could have:

          About the role

          ...position summary...

          Responsibilities

          ...list...

          Qualifications and Requirements

          ...list required qualifications, preferred qualifications, travel requirement, KPIs...
          But mixing different types may be okay. However we need to preserve all substantive info; we can list them as separate
        • items. We must not invent or summarize away detail. So we need to keep exact phrasing? Not required to keep exact wording but preserve all info. We can rephrase slightly but must not lose detail. Let's extract each piece. About Company: We'll keep as a

          before sections. Position Summary: We'll put as

          under About the role. Responsibilities: list each bullet: - Act as the primary quality interface for assigned OEM customers (GM, Ford, Stellantis) - Lead and support customer visits, audits, and reviews - Ensure timely communication of quality issues and improvements - Maintain strong relationships with OEM quality teams - Lead 8D problem-solving activities for customer complaints and internal issues - Drive containment, root cause analysis, and corrective actions - Ensure timely submission and closure of corrective action reports - Utilize tools such as 5 Why, Fishbone, and Fault Tree Analysis - Monitor customer scorecards (PPM, warranty, delivery) - Identify trends and lead improvement initiatives - Develop and implement action plans to address performance gaps - Conduct regular visits to Minth plants across North America - Ensure alignment with customer requirements - Support plant quality teams in issue resolution and audit preparation - Verify effectiveness of corrective actions - Coordinate sorting and inspection activities - Ensure effective containment at customer sites and plants - Work with third-party inspection providers - Ensure compliance with IATF 16949 and customer-specific requirements - Support internal and external audits - Participate in APQP and ensure PFMEA and control plans are updated - Drive continuous improvement initiatives - Support Lean and Six Sigma activities - Promote a culture of quality ownership That's many. Qualifications: Required: - Bachelor’s Degree in Engineering (Mechanical, Industrial, Manufacturing, or related field) Or 5 to 10 years experience in automotive quality. - 5+ years of automotive quality engineering experience - Experience with OEM customers (GM, Ford, Stellantis required) - Strong background in customer-facing roles - Knowledge of IATF 16949 - Experience with Automotive Core Tools (APQP, PPAP, FMEA, SPC, MSA) - Experience with customer portals (preferred) – note: this is listed under Technical Skills but marked preferred. - Proficiency in Microsoft Office - Strong communication and presentation skills - Excellent problem-solving ability - Ability to manage multiple priorities - High accountability and sense of urgency - Strong customer focus Preferred Qualifications (Not Required): - ASQ Certified Quality Engineer (CQE) - Six Sigma Green Belt or Black Belt - Experience in metal or plastics manufacturing - Warranty analysis experience Travel Requirements: - Frequent travel (30–50%) across North America Key Performance Indicators: - Customer PPM performance - Scorecard ratings - Corrective action closure timing - Warranty claim reduction - Customer satisfaction We could include travel and KPIs under Qualifications section as additional bullets. Thus final HTML:

          About Company Minth Group stands as a global leader in the manufacturing of exterior and structural automotive