Production Technician 4 (Sensors)

We need to output HTML fragment with sections only when there is real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the job description. Given content: Job Description Summary, Job Description Basic Qualifications, etc. There's no explicit "About the role" heading but we can create one from summary? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real, specific content for it. So we need to decide which sections have content. We have: - Basic Qualifications: "High School Diploma or GED equivalency 5 years inspection experience in a Manufacturing environment Ability and willingness to use advanced hand tools and measuring devices (i.e. – optical comparators, CMM, programmable and specialized testers) as required. Ability to perform advanced mathematical calculations (addition, subtraction, etc.), may have to perform metric conversions, conversions to decimals, and use geometry." - Essential Functions & Responsibilities: a long list. - Desired Qualifications: many items. - Physical Demands: list. - Pay: "$27/hr.-$30.50/hr. This position is also eligible for an annual discretionary bonus based on a percentage of your base salary/ commission based on the plan." - Benefits: description of healthcare, retirement, other benefits. - Schedule: Not explicitly mentioned. There's mention of "working shifts beyond a standard workweek" but not schedule specifics. Probably we should not create Schedule section unless explicit schedule info. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits is stated, so we can include Benefits. Pay is stated, include Pay. Schedule not explicitly given; we have "working shifts beyond a standard workweek" but not a schedule like "full-time", "shift work". Might be considered schedule info? It says "This role may encounter high risk or hazardous operations, working with chemicals, and/or include working shifts beyond a standard workweek." That implies schedule may involve shifts beyond standard workweek, but not explicit. Safer to omit Schedule section. - About the role: Could be derived from Job Description Summary? The posting includes "Job Description Summary Job Description". Might be considered summary. We could treat that as About the role. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create About the role section with the summary content. The summary likely is the first paragraph: "Job Description Summary Job Description". Actually the text: "Job Description Summary Job Description Basic Qualifications ..." It seems like a heading. We'll extract the summary: maybe the first sentence before "Basic Qualifications". The text: "Job Description Summary Job Description Basic Qualifications". That seems redundant. But we can treat "Job Description Summary" as the summary. We'll include a brief paragraph: maybe "Job Description Summary". However we need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include the exact text that constitutes the summary. The summary appears to be "Job Description Summary Job Description". That's not meaningful but it's there. We could include it as a paragraph. Better: We could treat the content before "Basic Qualifications" as the About the role section. That is: "Job Description Summary Job Description". We'll output that as a

. Then Responsibilities: from "Essential Functions & Responsibilities" list. Requirements: Could be Basic Qualifications? Or maybe Requirements = Basic Qualifications. Qualifications: Desired Qualifications. Skills: maybe combine some skill statements from Desired Qualifications? But we have separate headings for Qualifications and Skills. The instruction says we can use those headings if there is real content. We have Basic Qualifications (requirements) and Desired Qualifications (qualifications). Skills could be extracted from Desired Qualifications like "Strong oral and written communication skills", "Demonstrated ability to analyze and resolve problems", etc. But we might just put Skills section with those skill-based items. We need to avoid thin sections; prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one? But we have headings list; we can choose to include only those with substantive content. We could include About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Desired Qualifications), Benefits, Pay. That's six sections. Skills maybe not needed if we already have Qualifications covering skills. But we could include Skills if there is distinct skill content not covered elsewhere. However Desired Qualifications includes many skill-like items. Might be okay to skip Skills. We must not repeat job title as heading; we don't have title. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO, legal, accommodation, export-controlled info, etc. Also remove "All job descriptions are subject to change." That's boilerplate? Might be considered legal; we should remove. Also remove "This document does not create a contract of employment..." etc. Also remove "If you are a qualified individual with a disability..." etc. Also remove "Additional Information GE Aerospace offers a great work environment..." maybe that's boilerplate but includes some content about work environment; but it's generic. Might be considered boilerplate; we should remove. Also remove "GE Aerospace is an Equal Opportunity Employer..." etc. Also remove "Any offer of employment is conditioned upon the successful completion of a drug screen..." etc. Also remove "Relocation Assistance Provided: No". Also remove "This posting is expected to close 11/30/26." That's maybe metadata but not boilerplate; could be considered minor metadata; we could fold into a short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we could include the closing date in a short p maybe under About the role? But better to drop minor metadata. We'll drop it. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the pay, benefits, responsibilities, qualifications, etc. Let's extract substantive content: About the role (summary): "Job Description Summary Job Description". Might be weird but we keep. Responsibilities (Essential Functions & Responsibilities): list of items: - Applies basic judgement and has the ability to propose different solutions. - Uses prior experience and on-the-job training to solve straightforward problems/tasks. - Accesses technical and analytic skills required to solve problems. - Daily dispositioning of nonconforming material - Partners cross-functionally with internal resources to arrive at decisions. - Applies established interpersonal skills and leads by example for peers and employees. - Develops understanding of GD&T and advanced measurement principles as applicable. - Identifies and documents non-conforming parts, while using Oracle to maintain inspection records. - Perform job responsibilities according to internal process specifications and third-party requirements. - Assist support functions in root cause analysis; Must be able to multi-task and work within deadlines. - Uses manual and automated measuring / testing equipment to assure product quality. - Cross-trains with employees as needed based upon knowledge and experience. - Compliantly completes all written and/or electronic labor tracking documentation. - Communicates with team to ensure all team members are aware of product deficiencies, new processes, or issues. Provide feedback to appropriate support functions. - Assists leading and supporting team initiatives; participates in Careful Selection process. - Report problems to appropriate resource and/or Coach. - Proactively work to improve efficiency and quality of products. - Participate in and support team initiatives. - Utilize proper PPE, safety equipment, and follow safety procedures per position requirements. - Understand and abides by the GE Leadership behaviors. - Other duties as be required We need to keep each as

inside

. Requirements (Basic Qualifications): list: - High School Diploma or GED equivalency - 5 years inspection experience in a Manufacturing environment - Ability and willingness to use advanced hand tools and measuring devices (i.e. – optical comparators, CMM, programmable and specialized testers) as required. - Ability to perform advanced mathematical calculations (addition, subtraction, etc.), may have to perform metric conversions, conversions to decimals, and use geometry. We'll put each as
• . Qualifications (Desired Qualifications): list many items. We'll extract each bullet: - 5 – 10 year’s inspection experience in a manufacturing environment. - Knowledge of Quality System requirements (AS9100). - Knowledge of electrical components and test methods to include ohm meter, gauss meter, surge test, bipot, etc. - Knowledge of assembly techniques; knowledge of geometric dimensions and tolerances. - Proficiency in understanding special process operations (e.g., brazing, soldering, welding, coating, etc.) as required within the department. - Demonstrates blueprint interpretation, electrical inspection, mechanical inspection, and procedural knowledge. - Inspect all raw materials and purchased parts to determine conformance to design requirement. - Use statistical process control and statistical quality control techniques as required. - Possess Weld and Braze inspection certification; Ability and willingness to pass visual acuity exam. - General knowledge of electrical components and test methods. - Possess knowledge of inspection in multiple areas of the site. - Assembly, solder, or electronics manufacturing experience preferred. - Experience in self-directed team environment; lean manufacturing knowledge. - Strong oral and written communication skills. - Demonstrated ability to analyze and resolve problems. - Humble: respectful, receptive, agile, eager to learn. - Transparent: shares critical information, speaks with candor, contributes constructively. - Focused: quick learner, strategically prioritizes work, committed. - Leadership ability: strong communicator, decision-maker, collaborative. - Problem-solver: analytical-minded, challenged existing processes, critical thinker. We'll keep each as
• . Physical Demands: maybe we could include as a section? Not in headings list but we could treat as Requirements? But we have no heading for Physical Demands. Could we include under Requirements? The instruction only lists certain headings; we could add other headings if needed? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples but not exclusive? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should only use those headings. So we should not create a Physical Demands section. We could fold physical demands into Requirements or Responsibilities? Probably better to drop it as it's not covered by headings. But we must preserve ALL substantive information; dropping physical demands would lose info. However we could incorporate physical demands into Requirements as a list item? But it's not a requirement per se; it's a physical demand. Could be considered part of Requirements. The instruction says we can use those headings; we could add a section for Physical Demands if we think it's substantive, but not listed. Safer to include it under Requirements as a list item? Might be okay. But we need to follow instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. I think we should stick to those headings only. So we need to map all content to those headings. Physical demands could go under Requirements (maybe as a sub-item). We'll add a list item: "Ability to continuously use hands and fingers in repetition; ability to occasionally bend, stoop, twist, crouch, squat, climb, and/or balance; ability to continuously sit; ability to occasionally lift to 20 lbs.; ability to push/pull up to 22 lbs.; may encounter high risk or hazardous operations,