Jobs · Quality Assurance · Arizona

2nd Shift Quality Inspector III

Collins Aerospace · Phoenix, AZ · 3 wk ago
On-siteQuality AssuranceFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits, Pay, Schedule. Only include sections with real content. From posting: - About the role: description about RTX, Collins Aerospace, Powers & Controls team looking for Quality Inspector. That's prose. - Responsibilities: list of duties: "What You Will Do" bullet list. Also maybe "Secondary responsibility will be to complete final inspections." etc. - Requirements: "U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract." Also maybe "Security Clearance Type: None/Not Required" but that's not a requirement. Also "Position Role Type: Onsite". Might be considered requirement? But we can include as part of About? Probably not. We'll include a Requirements section with US citizenship requirement. - Qualifications: "You Must Have HS diploma with a minimum of 2 years of relevant experience. In the absence of a HS diploma or GED, 4 years of relevant experience is required. Familiarity with principles of Quality Inspection." Also "Qualifications We Prefer ..." list. - Skills: maybe not explicit separate; but we could combine with Qualifications? The instruction says use sections like Skills if present. There's no explicit Skills heading; but we could infer from "Experience with FAA 8130 creation. Experience working with SAP or any other ERP system. Experience working with blueprints and/or technical drawings. Solder experience. Prior experience with component level troubleshooting. A&P License." Those are preferred qualifications, not skills. We could put them under Qualifications (Preferred). Or we could create a Skills section with those items. However instruction: "Prefer a few substantive sections over many thin ones." So better to keep Qualifications include both must-have and preferred. - Benefits: list of benefits described. - Pay: Not mentioned except sign-on bonus of $3,000 for external candidates. That's pay-related. Should we include Pay section? The posting mentions "External candidates will receive a sign-on bonus of $3,000". That's a pay detail. So we can include Pay section with that info. - Schedule: "2nd Shift: Monday – Friday, 3:30 - 12:00 am Training could take place on 1st Shift or 2nd Shift depending on need: if 1st Shift, Monday to Friday, 6am to 2:30pm for up to 60 days". Also "You may occasionally need to provide weekend and holiday support". So schedule details exist. Include Schedule section. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, legal, etc. Also remove "Learn More & Apply Now!" etc. Also remove "Apply now and be part of the team..." etc. Also remove "Please ensure the role type..." etc. Also remove "#TopOpps #P&CPM". Also remove "As part of our commitment..." etc. Also remove "Privacy Policy and Terms". Also remove "Date Posted: 2026-09-22 Country: United States of America Location: US-AZ-PHOENIX-1007 ~ 1007 E University Dr ~ 1007 E UNIVERSITY DR Position Role Type: Onsite U.S. Citizen, U.S. Person, or Immigration Status Requirements: U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract. Security Clearance Type: None/Not Required Security Clearance Status: Not Required". Actually we need to keep US citizenship requirement but not the other metadata like date posted etc. We'll fold minor metadata into short p or drop it. So we can include a short p for "Position Role Type: Onsite" maybe? But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short p with "Position Role Type: Onsite". Also maybe include "U.S. citizenship required" as part of Requirements. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from responsibilities, qualifications, benefits, pay, schedule, etc. We need to output only HTML fragment, no /, no markdown fences. Let's craft sections:

About the role

At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With three market‑leading businesses, world‑class operations and investments in research and development, RTX offers capabilities and opportunity no one else can. Collins Aerospace is a leader in technologically advanced, intelligent solutions that help redefine the aerospace and defense industry. With a comprehensive portfolio and deep technical expertise, we help customers meet the demands of the global market. Join us and help shape the future of aerospace and defense. Our Powers & Controls team is looking for a Quality Inspector to perform inline inspection of repaired electronic components, and associated paperwork. This position requires a keen focus on physically inspecting aircraft components and reviewing paperwork to ensure that workmanship standards, quality requirements, customer requirements are satisfied, and components are returned to service in an airworthy condition with all required documentation accurately completed. The secondary responsibility will be to complete final inspections.

That's about. Responsibilities: list from "What You Will Do". We'll extract each bullet. Let's list them: - Inspect rework and assembly performed by others, and solder electronic components per IPC-A-610 and J-STD. - Articulate and understand written instructions from customer flow down, such as purchase orders and customer technical documentation. - Read and interpret technical data such as component maintenance manuals (CMMs), assembly/work instructions, and engineering prints. - Generating Authorized Release Certificates (ARC) for multiple regulatory civil aviation authorities or Certificates of Conformance for military customers. - Ensuring no defects in assembly, soldering, bonding, or finish. - Performing unit shakedown to check for foreign objects and loose internal hardware. - Marking defects and removing rejects, setting them aside for repair. - Reading and interpreting technical data such as service bulletins, component maintenance manuals, or engineering prints. - Ensuring appropriate record keeping. - Reviewing work order documentation for accuracy and completeness, ensuring adherence to specifications and conformance to company standards and customers’ requirements. - Effectively interacting with team members and support staff as well as external customers when applicable (source inspection, external approvals, etc.) - Issuing scrap certificates. - Comply with ESD and FOD programs. - Provide constructive feedback to teammates when corrections are needed. - Work with minimal oversight and in a multi-discipline team environment, providing insight and solutions to complicated issues both technical and procedural. Note there is duplicate "Reading and interpreting technical data such as..." appears twice (once earlier, later). We should keep both? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplicate lines are present in source; we should not remove duplicates unless they are considered boilerplate? It says remove duplicated lines. So we should remove duplicated lines. The duplicate line: "Reading and interpreting technical data such as service bulletins, component maintenance manuals, or engineering prints." appears earlier as "Read and interpret technical data such as component maintenance manuals (CMMs), assembly/work instructions, and engineering prints." and later "Reading and interpreting technical data such as service bulletins, component maintenance manuals, or engineering prints." They are not exact duplicates but similar. The instruction says remove duplicated lines; likely means exact duplicate lines. We'll keep both as they are not identical. However there is also "Reading and interpreting technical data such as component maintenance manuals (CMMs), assembly/work instructions, and engineering prints." vs later "Reading and interpreting technical data such as service bulletins, component maintenance manuals, or engineering prints." Not exact duplicate. We'll keep both. Now Requirements section: US citizenship required. Also maybe "Position Role Type: Onsite" could be minor metadata; we could put in a short p under Requirements or separate. But we can include a short p: "Position Role Type: Onsite". However instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short p for that. Thus Requirements:

Requirements

Position Role Type: Onsite

U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract.

Qualifications: Must have and Preferred. We'll create:

Qualifications

You must have:

  • HS diploma with a minimum of 2 years of relevant experience.
  • In the absence of a HS diploma or GED, 4 years of relevant experience is required.
  • Familiarity with principles of Quality Inspection.

Preferred qualifications:

  • Experience with FAA 8130 creation.
  • Experience working with SAP or any other ERP system.
  • Experience working with blueprints and/or technical drawings.
  • Solder experience.
  • Prior experience with component level troubleshooting.
  • A&P License.
Benefits: list as given. We'll create:

Benefits

  • Medical, dental, and vision insurance
  • Three weeks of vacation for newly hired employees
  • Generous 401(k) plan that includes employer matching funds and separate employer retirement contribution, including a Lifetime Income Strategy option
  • Tuition reimbursement program
  • Student Loan Repayment Program
  • Life insurance and disability coverage
  • Optional coverages you can buy: pet insurance, home and auto insurance, additional life and accident insurance, critical illness insurance, group legal, ID theft protection
  • Birth, adoption, parental leave benefits
  • Ovia Health, fertility, and family planning
  • Adoption Assistance
  • Autism Benefit
  • Employee Assistance Plan, including up to 10 free counseling sessions
  • Healthy You Incentives, wellness rewards program
  • Doctor on Demand, virtual doctor visits
  • Bright Horizons, child and elder care services
  • Teladoc Medical Experts, second opinion program
  • And more!
Pay: sign-on bonus.

Pay

External candidates receive a sign‑on bonus of $3,000.

Schedule: details.

Schedule

2nd Shift: Monday – Friday, 3:30 am – 12:00 am (note: 3:30 - 12:00 am as posted). Training could take place on 1st Shift or 2nd Shift depending on need: if 1st Shift, Monday to Friday, 6 am to 2:30 pm for up to 60 days. You may occasionally need to provide weekend and holiday support to meet customer needs.

We need to ensure we didn't miss any substantive info: Physical Demands, Working Environment, etc. Those are also substantive. Should we include them? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Physical Demands and Working Environment are specific content. Should we create sections for them? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No explicit heading for Physical Demands or Working Environment. So we must fit them into existing sections or maybe incorporate into About the role or Responsibilities? The instruction says use those headings for section headings. It

Similar jobs