Customer Quality Engineer - Automotive Manufacturing

We need to output HTML fragment with sections: Benefits, Responsibilities, Qualifications, maybe Work Environment & Schedule, Onboarding? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content for it. So we need to parse the posting. Content: - Benefits: listed: 401(k), Bonus based on performance, Dental insurance, Health insurance, Paid time off, Vision insurance. So Benefits section with

• each. - Responsibilities: many bullet points. Should be a
  • list. - Qualifications: list of qualifications. - Work Environment & Schedule: includes description: Primarily on customer production floors and quality labs (PPE required). Day shift with flexibility for off‑shift/weekend coverage during excursions, builds, or audits. That's content for Work Environment & Schedule. Could be separate sections: Work Environment and Schedule? The instruction says we can use headings like Work Environment & Schedule? Not listed but we can use similar. They gave examples but not limited. Probably we can create a heading "Work Environment & Schedule". Or separate "Work Environment" and "Schedule". Since they gave both, we can combine. - Onboarding: details about first 2 weeks training in Dallas. That's content; could be a section "Onboarding". Not in examples but okay. - Location & Travel: also content. Could be a section "Location & Travel". Might be considered. We must not repeat job title as heading. No Job ID etc. We must not include boilerplate like EEO etc. The posting didn't have that. We must not create Pay or Schedule sections unless posting actually states them. It mentions Day shift with flexibility for off‑shift/weekend coverage; that's schedule info. So we could include Schedule as part of Work Environment & Schedule. Or separate Schedule heading with content. Since they said "Prefer a few substantive sections over many thin ones." So combine. Thus sections: Benefits, Responsibilities, Qualifications, Work Environment & Schedule, Onboarding, Location & Travel. Check each for real specific content. Benefits: yes. Responsibilities: yes. Qualifications: yes. Work Environment & Schedule: includes description of environment and shift flexibility. Onboarding: includes first 2 weeks full-time in Dallas for training. Location & Travel: includes 100% on-site at Lathrop, routine travel between sites, occasional off-shift/weekend support. We must not include filler like "commensurate with experience". Not present. Now format: Use

    for each heading. Then content: For lists use

    • . For prose use

      . We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given, maybe rephrase? Must preserve meaning but can keep same wording. We need to extract bullet points from responsibilities paragraph. The responsibilities are a long paragraph with semicolons and sentences. We need to convert each duty into list items. Must not lose any detail. Let's parse responsibilities: "Customer‑site presence — Lathrop (100%) Lead on‑site containment (stop/hold/segregate), build suspect lists, coordinate rework/returns. Run MRB & GP12 for AOI‑flagged parts: image pull‑up, objective‑evidence review (e.g., continuity logs), pass/fail decisions; no ship without evidence. Perform LPAs, line walks, verify corrective actions; maintain daily scorecards (DPPM, escape rate, time‑to‑containment). Serve as the day‑to‑day voice to customer SQ/production; deliver concise, data‑first updates and recovery plans. Support trials/builds/audits; collect early signals (fit‑up, assembly, electrical continuity) and escalate with annotated prints. Align on change points and readiness with customer teams; feed learnings back to Dallas. Close the loop with stamping/assembly/test/pack to prevent recurrence; align control plans, CTQs, and measurement methods. Convert customer feedback into structured 8D/5Why/Is–Is Not; drive sustainable corrective actions. Support AOI parameter tuning, continuity‑gate/“release‑code” processes, and eMRB/evidence capture (images, logs, sign‑offs). Systems, data & communications Maintain SN‑level traceability: AOI images, MRB/GP12 decisions, objective measurements (e.g., continuity), and release codes. Publish daily “Reno/Austin → Dallas” briefs (in English; Chinese summaries preferred): top defects, hotspots, escapes, ETA to clean‑point, risks/asks. Escalate early with quantified impact and interim mitigations." We need to split into list items. Could keep each sentence as an item, but ensure we don't lose detail. Let's create list items: - Customer‑site presence — Lathrop (100%) - Lead on‑site containment (stop/hold/segregate), build suspect lists, coordinate rework/returns - Run MRB & GP12 for AOI‑flagged parts: image pull‑up, objective‑evidence review (e.g., continuity logs), pass/fail decisions; no ship without evidence - Perform LPAs, line walks, verify corrective actions; maintain daily scorecards (DPPM, escape rate, time‑to‑containment) - Serve as the day‑to‑day voice to customer SQ/production; deliver concise, data‑first updates and recovery plans - Support trials/builds/audits; collect early signals (fit‑up, assembly, electrical continuity) and escalate with annotated prints - Align on change points and readiness with customer teams; feed learnings back to Dallas - Close the loop with stamping/assembly/test/pack to prevent recurrence; align control plans, CTQs, and measurement methods - Convert customer feedback into structured 8D/5Why/Is–Is Not; drive sustainable corrective actions - Support AOI parameter tuning, continuity‑gate/“release‑code” processes, and eMRB/evidence capture (images, logs, sign‑offs) - Maintain SN‑level traceability: AOI images, MRB/GP12 decisions, objective measurements (e.g., continuity), and release codes - Publish daily “Reno/Austin → Dallas” briefs (in English; Chinese summaries preferred): top defects, hotspots, escapes, ETA to clean‑point, risks/asks - Escalate early with quantified impact and interim mitigations That seems comprehensive. Now Qualifications: list: - 3–7 years in Supplier Quality / Resident Engineering / Manufacturing Quality (automotive or high‑volume preferred) - Able to read and interpret engineering drawings with GD&T (GN&D)—feature controls (position/profile/flatness), datums, and basic stack‑ups; can communicate deviations clearly with design/manufacturing engineering using annotated markups - Hands‑on with MRB, GP12/containment, AOI image review, defect mapping, and customer‑side interactions - Proficient in 8D/5Why, SPC, control plans, PFMEA; comfortable creating measurement plans from prints - Strong data skills (Excel/Sheets; bonus: Power BI/Tableau or basic Python for trend analysis) - Excellent cross‑functional and customer‑facing communication; decisive under time pressure - Language: English required; Mandarin Chinese speaking preferred (ability to summarize daily updates in both languages is a plus) - Able to travel routinely between to Lathrop, California. - Preferred: Experience in metal stamping/busbar/assembly; exposure to electrical/continuity checks and AOI tuning. - Prior resident engineer role at an OEM/customer site. - MES/QMS/eMRB experience and evidence‑based release processes; ability to draft bilingual work instructions. We need to keep each as list item. Now Work Environment & Schedule: description: "Primarily on customer production floors and quality labs (PPE required). Day shift with flexibility for off‑shift/weekend coverage during excursions, builds, or audits." We can make two list items or a paragraph. Since it's prose, we can use

      . Onboarding: "First 2 weeks full‑time in Dallas for Quality & Engineering training (process, CTQs, AOI, MRB/GP12, eMRB/evidence capture)." That's a sentence. Location & Travel: "100% on‑site at the customer’s Lathrop factory. Routine travel between sites; occasional off‑shift/weekend support during ramps." We can make a paragraph. Now Benefits: list items. Now output HTML fragment only. Let's craft:

      Benefits

      • 401(k)
      • Bonus based on performance
      • Dental insurance
      • Health insurance
      • Paid time off
      • Vision insurance

      Responsibilities

      • Customer‑site presence — Lathrop (100%)
      • Lead on‑site containment (stop/hold/segregate), build suspect lists, coordinate rework/returns
      • Run MRB & GP12 for AOI‑flagged parts: image pull‑up, objective‑evidence review (e.g., continuity logs), pass/fail decisions; no ship without evidence
      • Perform LPAs, line walks, verify corrective actions; maintain daily scorecards (DPPM, escape rate, time‑to‑containment)
      • Serve as the day‑to‑day voice to customer SQ/production; deliver concise, data‑first updates and recovery plans
      • Support trials/builds/audits; collect early signals (fit‑up, assembly, electrical continuity) and escalate with annotated prints
      • Align on change points and readiness with customer teams; feed learnings back to Dallas
      • Close the loop with stamping/assembly/test/pack to prevent recurrence; align control plans, CTQs, and measurement methods
      • Convert customer feedback into structured 8D/5Why/Is–Is Not; drive sustainable corrective actions
      • Support AOI parameter tuning, continuity‑gate/“release‑code” processes, and eMRB/evidence capture (images, logs, sign‑offs)
      • Maintain SN‑level traceability: AOI images, MRB/GP12 decisions, objective measurements (e.g., continuity), and release codes
      • Publish daily “Reno/Austin → Dallas” briefs (in English; Chinese summaries preferred): top defects, hotspots, escapes, ETA to clean‑point, risks/asks
      • Escalate early with quantified impact and interim mitigations

      Qualifications

      • 3–7 years in Supplier Quality / Resident Engineering / Manufacturing Quality (automotive or high‑volume preferred)
      • Able to read and interpret engineering drawings with GD&T (GN&D)—feature controls (position/profile/flatness), datums, and basic stack‑ups; can communicate deviations clearly with design/manufacturing engineering using annotated markups
      • Hands‑on with MRB, GP12/containment, AOI image review, defect mapping, and customer‑side interactions
      • Proficient in 8D/5Why, SPC, control plans, PFMEA; comfortable creating measurement plans from prints
      • Strong data skills (Excel/Sheets; bonus: Power BI/Tableau or basic Python for trend analysis)
      • Excellent cross‑functional and customer‑facing communication; decisive under time pressure
      • Language: English required; Mandarin Chinese speaking preferred (ability to summarize daily updates in both languages is a plus)
      • Able to travel routinely between to L