Sr. Specialist, Supplier Quality Engineer

We need to output HTML fragment with sections: About the role? The posting includes description of company culture etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie, application instructions. We need to include sections only when posting has real specific content. Let's parse the posting: - Intro paragraph about L3Harris dedication etc. Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put company overview under "About the role". That seems appropriate. - Job Title: Spec, Quality Engr (but we do NOT repeat job title as a heading). So we just include content. - Job Code: QEP4 (metadata, can be folded into short p or dropped). We'll maybe include in a short p under About the role? Or drop. - Job Location: Clifton, NJ (metadata). Could be in About the role. - Job Schedule: 9/80: Employees work 9 out of every 14 days- totaling 80 hours worked- and have every other Friday off. That's schedule info, so we need a Schedule section. - Job Description: This position is responsible for quality improvement issues related to suppliers and/or subcontractors of materials, products or services used in development or manufacturing and responsible for managing incoming material discrepancies. That's a description; could be part of About the role or Responsibilities. - Essential Functions: list of duties (lead supplier quality activities, etc). That's responsibilities. - Travel up to 25% percent (maybe part of responsibilities). - Active secret clearance (qualification? maybe requirement). - Qualifications: Bachelor’s Degree ... OR Master’s ... OR 10 years experience. That's qualifications. - Preferred Additional Skills: list of skills (ability to focus, etc). That's Skills. - In compliance with pay transparency requirements, the salary range for this role in New Jersey is $96k - $178k. This is Pay. - L3Harris also offers a variety of benefits, including health and disability insurance, 401(k) match, flexible spending accounts, EAP, education assistance, parental leave, paid time off, and company-paid holidays. That's Benefits. - The rest is EEO etc, remove. We need to output HTML fragment with headings

and appropriate content. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. We need to avoid filler like "commensurate with experience", etc. Not present. We need to not repeat job title as heading. We need to not put Job ID/requisition numbers as headings; fold minor metadata into short p or drop. Thus we can have:

  About the role

  L3Harris is dedicated to recruiting and developing high-performing talent who are passionate about what they do. Our employees are unified in a shared dedication to our customers’ mission and quest for professional growth. L3Harris provides an inclusive, engaging environment designed to empower employees and promote work-life success. Fundamental to our culture is an unwavering focus on values, dedication to our communities, and commitment to excellence in everything we do. L3Harris is the Trusted Disruptor in defense tech. With customers’ mission-critical needs always in mind, our employees deliver end-to-end technology solutions connecting the space, air, land, sea and cyber domains in the interest of national security. Job Code: QEP4. Location: Clifton, NJ.

  But we need to ensure we don't repeat job title. That's fine. Then Responsibilities: Use

  Responsibilities

  then
  • each essential function. List them: - Lead supplier quality activities across multiple programs with minimal supervision. - Serve as the primary quality interface between suppliers and internal cross-functional teams including engineering, manufacturing, supply chain, logistics, and program management. - Drive supplier corrective action requests, root cause analysis, containment, and verification of permanent corrective actions. - Assess supplier performance, identify risk areas, and develop mitigation and recovery plans to support program execution and delivery commitments. - Conduct supplier evaluations, audits, and process reviews to ensure compliance with quality requirements, specifications, and contractual expectations. - Monitor supplier quality metrics and performance trends to proactively address issues affecting cost, quality, and schedule. - Support material review board activities, nonconformance resolution, and disposition coordination with internal stakeholders and suppliers. - Partner with sourcing and supply chain teams to support supplier selection, qualification, development, and performance improvement efforts. - Review and interpret engineering drawings, specifications, flow-down requirements, and quality clauses to ensure supplier compliance. - Provide leadership in resolving complex supplier-related issues that impact production, product acceptance, and customer commitments. - Support production readiness, first article inspections, process validation, and implementation of quality planning requirements as needed. - Coordinate and communicate supplier quality status, risks, and corrective action progress to program and functional leadership. - Travel to supplier locations as required to support audits, investigations, source inspections, and recovery efforts. - Act as an independent, experienced resource capable of prioritizing and executing day-to-day supplier quality responsibilities across a demanding, fast-paced environment. - Willingness to travel up to 25 percent. We need to keep the exact phrasing? Preserve all substantive information; we can keep as is. Then Requirements? The posting has Qualifications section (education/experience) and also Active secret clearance maybe a requirement. Also maybe "Active secret clearance" is a requirement. We'll put under Requirements. But we also have a Qualifications heading separate. The instruction includes both Requirements and Qualifications as possible headings. We need to decide what goes where. Typically Requirements could be mandatory qualifications (education/experience, clearance). Qualifications could be preferred? But they listed Qualifications as education/experience. Preferred Additional Skills as skills. We could treat: - Requirements: Active secret clearance, willingness to travel up to 25%, maybe also the education/experience? But they have a Qualifications section for education/experience. Let's follow the posting: they have "Qualifications:" heading with education/experience. Then "Preferred Additional Skills:" heading with skills. So we can map:

    Qualifications

    for education/experience.

    Skills

    for preferred additional skills.

    Requirements

    maybe for Active secret clearance and willingness to travel? But the instruction says include a section ONLY when posting has real specific content. We have content for Requirements (clearance, travel). So we can include. But we also have Pay and Schedule sections. Pay: salary range $96k - $178k. Benefits: list. Schedule: 9/80 description. We need to avoid fluff like "This is not a guarantee of compensation or salary, as final offer amount may vary based on factors including but not limited to experience and geographic location." That's substantive? It's a disclaimer about pay. Should we include? It's part of pay info. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should include that sentence as part of Pay section. Similarly benefits description includes "The specific programs and options available to an employee may vary depending on date of hire, schedule type, and the applicability of collective bargaining agreements." That's substantive; include. Now we need to ensure we don't include boilerplate like EEO etc. Remove. Now produce HTML. We need to use

    for each section heading. Inside each section, we can have

    for prose,

    • for lists. We need to avoid duplicate lines. Let's craft. About the role: combine intro paragraphs and job description maybe. We have intro about L3Harris (first paragraph). Then Job Description sentence: "This position is responsible for quality improvement issues related to suppliers and/or subcontractors of materials, products or services used in development or manufacturing and responsible for managing incoming material discrepancies." That's substantive. We can put that in About the role as a paragraph. We also have Job Code and Location as metadata; we can include in a short p. Thus About the role:

      L3Harris is dedicated to recruiting and developing high-performing talent who are passionate about what they do. Our employees are unified in a shared dedication to our customers’ mission and quest for professional growth. L3Harris provides an inclusive, engaging environment designed to empower employees and promote work-life success. Fundamental to our culture is an unwavering focus on values, dedication to our communities, and commitment to excellence in everything we do. L3Harris is the Trusted Disruptor in defense tech. With customers’ mission-critical needs always in mind, our employees deliver end-to-end technology solutions connecting the space, air, land, sea and cyber domains in the interest of national security.

      Job Code: QEP4. Location: Clifton, NJ.

      This position is responsible for quality improvement issues related to suppliers and/or subcontractors of materials, products or services used in development or manufacturing and responsible for managing incoming material discrepancies.

      That seems fine. Now Responsibilities: list as above. Now Requirements: include Active secret clearance and willingness to travel up to 25 percent. Also maybe "Willingness to travel up to 25 percent" is already in responsibilities list; but we can keep it there; but we might duplicate. Better to keep travel in responsibilities (since it's a duty). The requirement could be just Active secret clearance. However the posting says "Willingness to travel up to 25 percent Active secret clearance" as a line under Essential Functions? Actually it's after Essential Functions list: "Willingness to travel up to 25 percent Active secret clearance". It seems like two items: willingness to travel up to 25% and Active secret clearance. So we can keep travel in responsibilities (makes sense) and clearance as requirement. Thus Requirements:

      Active secret clearance required.

      Now Qualifications: education/experience. We need to preserve the exact text: "Bachelor’s Degree in: Industrial, Mechanical or Electrical Engineering with a minimum of 4 years’ experience in supporting design, development, manufacturing and/or supplier quality activities OR, Master’s Degree in: Industrial, Mechanical or Electrical Engineering with a minimum of 2 years’ experience in supporting design, development, manufacturing and/or supplier quality activities. In lieu of a degree, minimum of 10 years of prior related experience." We'll put that in a

      . Now Skills: Preferred Additional Skills list. We need to list each item as

    • . The list includes many items, some duplicated (Supplier Development and Engagement experience appears twice). We should preserve as given but maybe we can keep duplicates? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplicates are part of the posting; we should keep them? It says remove duplicated lines. That refers to duplicated lines in the posting (like repeated boilerplate). But the duplicated skill lines might be intentional? It appears they listed "Supplier Development and Engagement experience" twice inadvertently. Should we keep both? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines likely refer to repeated boilerplate lines, not necessarily skill duplicates. But to be safe, we could keep both as they are part of the substantive content (though duplicated). However removing duplicated lines could be interpreted as removing any duplicate lines. I'd lean to keep them because they are part of the "Preferred Additional Skills" list; removing one would be summarizing away detail. I'd keep both. List items: - Ability to focus, prioritize, and multi-task successfully to drive projects to closure - Ability to perform trend analysis - Ability to work in a team environment -