Quality Inspector I- 2nd Shift

Here's a thinking process: 1. **Analyze User Request:** - **Goal:** Reformat a job posting into clean, well-structured semantic HTML - **Rules:** - Use `

` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use `

• ` for lists of duties/requirements/benefits - Use `

  ` for prose - Do NOT repeat job title as heading (already shown) - Do NOT put Job ID / requisition numbers as headings - 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") - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Input Job Posting:** Let me parse the content carefully. The text is: "GENERAL JOB SUMMARY: Ensure all incoming and manufactured parts meet applicable standards. ESSENTIAL JOB FUNCTIONS: Read and interpret specifications and follow procedures.Performs inspections of in-process materials as required.Initiates Corrective Action documents when needed and follows up to completion.Takes measurements and records data.Communicates issues to appropriate personnel within the organization.Other duties may be assigned. SUPERVISORY RESPONSIBILITY: This position does not require supervisory responsibilities. Experience And Skills KNOWLEDGE, SKILLS, & ABILITIES: Ability to maintain sensitive and confidential information as required by government standards.Ability to interact effectively with peers and supervisors.Ability to interact appropriately with the public when necessary.Ability to adhere to workplace rules.Basic computer skills required.Basic analytical ability is required; requires minimal problem-solving skills within the framework of standard practice.Ability to follow specific, detailed instructions and read detailed prints.Knowledge of mechanical measuring; geometric tolerance. EDUCATION AND EXPERIENCE: High school graduate or equivalent required.Vocational degree in a related field or equivalent experience preferred.Minimum one year of related inspection experience in manufacturing required. WORK ENVIRONMENT/PHYSICAL REQUIREMENTS: Shop Floor environment.Ability to stand and sit for long periods of time.Ability to perform repetitive motion (rotating wrists, keyboarding, using small/large tools).Ability to lift up to 50 pounds.Ability to tolerate constant noise (i.e., machine motors).Ability to work safely in the presence of hazardous chemicals and hazardous conditions.Ability to follow standard precautions using personal protective equipment as required. Job Benefits Medical, Dental & Vision Insurance CoverageLife/ADD & Short/Long Term Disability Insurance401(k) Savings PlanEmployee Stock Purchase Plan (ESPP)Paid Time-Off (PTO)HolidaysEducation ReimbursementMedical, Dental & Vision Insurance CoverageLife/ADD & Short/Long Term Disability Insurance401(k) Savings PlanEmployee Stock Purchase Plan (ESPP)Paid Time-Off (PTO)HolidaysEducation Reimbursement Kratos Defense is an Equal Opportunity Affirmative Action Employer. EOE, Minorities, Females, Vet, Disabled, Sexual Orientation, Gender Identity or any other protected class. All qualified job seekers are encouraged to apply. Kratos Defense is committed to America's veterans by providing opportunities for them to continue contributing after service to our nation. We also work to provide reasonable accommodations to individuals with disabilities. EEO Is The Law Disability Accessibility Accommodation If you require an accommodation to navigate or apply to our careers site, please send your request to HRAccessibility@kratosdefense.com or call 858-964-2916. Any inquires not related to requesting an accommodation will be discarded. Pay Transparency The company will not discharge or in any other manner discriminate against employees or applicants because they have inquired about, discussed, or disclosed their own pay or the pay of another employee or applicant. Job Applicant Privacy Notice For applicants in the EU and California residents, please review our privacy notice." Now, I need to structure this into semantic HTML using `

  `, `

  • `, `

    `, following the rules. Let's identify sections and content: - The job title isn't explicitly given in the text, but the user says "do NOT repeat the job title as a heading (the page already shows it)". So I should not add a `` or `` for job title. I'll just start with sections. - Sections I can identify from the content: * General Job Summary (or About the role) * Essential Job Functions (or Responsibilities) * Supervisory Responsibility (maybe fold into Responsibilities or Requirements, but it's specific content) * Knowledge, Skills, & Abilities (or Skills/Qualifications) * Education and Experience (or Requirements) * Work Environment/Physical Requirements (or Working Conditions) * Job Benefits (specific benefits listed, but note there's duplication; I should deduplicate or list once) * Pay Transparency (but no specific pay numbers; rule says only include Benefits/Pay/Schedule sections if posting actually states them. It says "Pay Transparency" policy but no actual pay range. Rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits explicitly, and it states a Pay Transparency policy statement, but no pay range. I need to be careful. The rule says: "Prefer a few substantive sections over many thin ones. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text... never create Pay/Schedule/Benefits sections unless the posting actually states them." The Benefits section has actual listed benefits (though duplicated). Pay Transparency is a policy statement, not actual pay data. I think I should include Benefits with the actual listed benefits, but deduplicate. I should NOT include a Pay section with no pay info. Schedule isn't mentioned. So I'll include Benefits but not Pay/Schedule.) - Remove boilerplate: EEO statements, equal opportunity, disability accessibility, privacy notice, scam warnings, application instructions. The user says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I need to strip those out entirely. - Duplicated lines: "Job Benefits" section is duplicated verbatim. I should list benefits once, or note the duplication but the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." I think I should list the benefits once, as including the exact same list twice would be redundant and possibly considered filler. I'll deduplicate but keep all unique benefits. Actually, the text lists them twice exactly. I'll just include them once, as is reasonable for HTML reformatting. - "Other duties may be assigned." is part of Essential Job Functions. I'll include it. - "SUPERVISORY RESPONSIBILITY: This position does not require supervisory responsibilities." This is specific content, so I'll include it as a section or fold it. The rules say use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I can map: "Essential Job Functions" -> Responsibilities, "KNOWLEDGE, SKILLS, & ABILITIES" -> Skills, "EDUCATION AND EXPERIENCE" -> Requirements, "WORK ENVIRONMENT/PHYSICAL REQUIREMENTS" -> maybe Working Conditions or Qualifications. I'll need to map carefully. Let's outline sections with headings as per allowed list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Mapping: - GENERAL JOB SUMMARY -> About the role (or maybe Responsibilities, but it's a summary). I'll use "About the role" or keep "General Job Summary"? The rule says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists examples, not strict mandate that I must use exactly those, but likely I should use similar semantic ones. I'll use the exact ones listed if content maps, or reasonable equivalents. To be safe, I'll use the ones from the list that fit, and omit/avoid ones without content. Let's map each part: 1. GENERAL JOB SUMMARY: "Ensure all incoming and manufactured parts meet applicable standards." -> This is a summary. I'll put under "About the role" or maybe it's part of the role description. I'll create a section "About the role" with that paragraph. 2. ESSENTIAL JOB FUNCTIONS: list of duties. -> "Responsibilities" section. 3. SUPERVISORY RESPONSIBILITY: "This position does not require supervisory responsibilities." -> Could go under Responsibilities or Requirements. I'll include it in Responsibilities or make a small note. Since it's specific content, I'll include it. Maybe under Responsibilities as a sub-point, or separate small section. But rules prefer few sections. I'll fold it into Responsibilities or Requirements. Actually, I'll put it as part of Responsibilities text. 4. KNOWLEDGE, SKILLS, & ABILITIES: list of abilities. -> "Skills" section. 5. EDUCATION AND EXPERIENCE: "High school graduate or equivalent required. Vocational degree... preferred. Minimum one year... required." -> "Requirements" section. 6. WORK ENVIRONMENT/PHYSICAL REQUIREMENTS: list of physical demands. -> Could be "Qualifications" or "Working Conditions". I'll use "Qualifications" or maybe create a section. The list is substantial, so I'll make a section "Qualifications" or "Working Conditions". Rules say use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Work Environment/Physical Requirements" maps well to "Qualifications" or I could use a separate heading but rules limit. I'll map to "Qualifications" since it's part of the job's prerequisites/conditions. Actually, "Qualifications" typically refers to education/experience. Physical requirements might be separate. I'll check the rule: "Prefer a few substantive sections over many thin ones." I'll probably put physical requirements under "Requirements" or "Qualifications". To be safe, I'll create a "Qualifications" section that includes both education/experience and physical requirements, or keep them separate if I can map properly. Let's see: The headings listed are examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I can use any of these, or others? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I think it's suggesting valid heading names. I'll use those names where content fits, and omit others. Let's re-evaluate: I need to output ONLY the HTML fragment, no markdown fences, no /. I need to carefully extract only the relevant content, strip boilerplate, and structure. Let's list all content to keep, category by category: - General Job Summary: "Ensure all incoming and manufactured parts meet applicable standards." - Essential Job Functions: * Read and interpret specifications and follow procedures. * Performs inspections of