Electronics/Avionics Tech II

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Must preserve all substantive info. We need to parse the job posting. Key sections: - Job Description: description paragraphs about role, responsibilities, etc. - Position Responsibilities: list of duties. - Basic Qualifications (Required Skills & Experience): list. - Other Qualifications & Desired Competencies: list. - Physical Demands: list. - Environmental Conditions Critical To Performance: description. - Clearance Level: maybe not needed? It says "No Clearance". Could be minor metadata; we can drop or put in short p. - ITAR Requirement: description. - Benefits: paragraph. - Who We Are: company description (maybe not needed? It's substantive but could be considered "About the role"? Might be considered "About the company". The instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who We Are" could be considered "About the role"? Not exactly. Might be considered "About the role" or maybe we can omit as not requested. But we need to preserve ALL substantive information; we cannot drop substantive info unless it's boilerplate. "Who We Are" is substantive about company. Could fit under "About the role"? Not exactly but maybe we can include as a paragraph under a heading like "About the role" or maybe we create a section "About the company"? Not in allowed headings. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are the expected headings; we should stick to those. So we need to map content to those headings. Thus: - About the role: could include the Job Description summary paragraph(s) and maybe Who We Are? But "About the role" likely refers to description of the role. So we can put the Job Description paragraph(s) there. - Responsibilities: list of duties from Position Responsibilities. - Requirements: could combine Basic Qualifications (Required Skills & Experience) and maybe Other Qualifications & Desired Competencies? But we have separate headings Qualifications and Skills. The instruction lists Qualifications and Skills as separate possible headings. We need to decide where to put what. We have Basic Qualifications (Required Skills & Experience) - that's like requirements. Other Qualifications & Desired Competencies - could be qualifications. Physical Demands and Environmental Conditions maybe could be under Qualifications? Or maybe we can create a separate section "Requirements" for basic qualifications, and "Qualifications" for other qualifications, and "Skills" for specific skills like soldering etc. But we need to avoid thin sections. Better: Use: - About the role: description paragraph(s). - Responsibilities: list of duties. - Requirements: Basic Qualifications (Required Skills & Experience) plus maybe Physical Demands and Environmental Conditions? But those are not exactly requirements but could be. - Qualifications: Other Qualifications & Desired Competencies. - Skills: maybe the specific technical skills like soldering, crimping, etc. But those are already in Basic Qualifications. Could combine. Given the instruction: "Prefer a few substantive sections over many thin ones." So we should combine where possible. Thus we could have: - About the role (description) - Responsibilities (list) - Requirements (combined Basic Qualifications + Other Qualifications + Physical Demands + Environmental Conditions + ITAR Requirement? maybe) - Benefits (section) We might not need Skills separate if covered. Pay and Schedule: not present (no pay/schedule specifics). Benefits mentions 9/80 work schedule (that's schedule). So we could include Schedule under Benefits? But we have a separate Schedule heading if schedule info present. The posting says "a 9/80 work schedule". That's schedule info. So we should create a Schedule section with that detail. Also Benefits section for medical, dental, vision, 401K with company matching, paid holiday shutdown. Pay: not specified, so we omit Pay section. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. We need to ensure we don't include filler like "commensurate with experience". Not present. Now extract content. About the role: The Job Description paragraph(s): "The Electronics/Avionics Technician II position is critical in ensuring the safety, reliability, and efficiency of our avionics systems. This position will be responsible for performing advanced troubleshooting, repairs, and maintenance on a variety of aircraft systems, including navigation, communication, and flight control systems. The ideal candidate will possess a strong understanding of electronic systems and will be proficient in utilizing diagnostic equipment and troubleshooting techniques. The successful applicant will have a keen attention to detail, excellent problem-solving skills, and the ability to work under pressure to meet tight deadlines. This position necessitates a high degree of technical competence and the ability to interpret complex technical manuals and schematics." That's the description. Also maybe include "Who We Are"? But that's about company, not role. Might be considered extra but we could incorporate under About the role? Might be stretching. However instruction says preserve ALL substantive information. If we omit Who We Are, we lose substantive info about company. But maybe it's considered boilerplate? It's not boilerplate; it's descriptive. However the allowed headings don't include "About the company". Could we put it under About the role as extra? Might be okay but could be considered misplacement. However we could add a separate section "About the company" but not in allowed headings; but instruction says use h3 for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, just gives examples. So we could add another heading like "About the company". But to be safe, maybe we incorporate it under About the role as a brief note? Might be considered not accurate but still preserves info. Alternatively, we could create a section "About the role" and then after that a paragraph about company under same heading? Might be okay. Better: Keep About the role as the description; then add a separate section "About the company" using h3. The instruction didn't forbid other headings; it just gave examples. So we can add. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule, About the company. Now extract Responsibilities list: From "Position Responsibilities" block: - Monitoring and servicing systems - Diagnosing problems and troubleshooting equipment - Running tests and completing reports - Updating and improving existing systems - Repairing or replacing faulty equipment - Inspecting buildings, equipment, and systems - Developing and implementing preventative maintenance procedures - Managing heating and plumbing systems (Remove) <-- note "(Remove)" indicates we should remove this line? It says "(Remove)" after that line. So we should remove that line. - Planning and scheduling repairs - Use work orders to determine the type and quantity of wire harness and assemblies to manufacture. - Follow assembly drawings and work instructions to manufacture wire harnesses. - Ability to master the basic skills needed to solder, strip, crimp, perform heat shrink, manage cable shields including foil and braid. - Assemble circular connectors based on standard operating procedures. - Assemble major functional subassemblies for the UAV which incorporate many of the harnesses manufactured in the area. - This position works with management and engineering for direction on new assemblies. - Work with the production assistant on new work orders and the stock room personnel to acquire kits to build work orders. - Other duties as assigned. We need to remove the line "Managing heating and plumbing systems (Remove)" entirely. Also note some lines are more like skills but they are in responsibilities; we keep them. Now Requirements: combine Basic Qualifications (Required Skills & Experience) and Other Qualifications & Desired Competencies, Physical Demands, Environmental Conditions, ITAR Requirement maybe. Basic Qualifications: - High school diploma or GED equivalent is required. - 1 - 2 years of working experience required. - Excellent wire soldering, stripping, crimping, and heat shrink skills, cable shields including foil and braid. - Capable of reading and understanding assembly drawings, and written work instructions to produce the highest quality avionics wire harness cables and assemblies. - Adept at wire harness assembly utilizing schematics, and wiring diagrams. - Experience using dedicated contact crimping tools for attaching connector contacts. - Experience assembling circular connectors. - Strong work-ethic and the flexibility to work in a dynamic environment. - Certifications IPC 610, J-STD-001, IPC/WHMA-A-620 - Previous experience in wire harness manufacturing role for a UAV company. Other Qualifications & Desired Competencies: - Good written and verbal communication skills. - Good analytical, time management and organizational skills. - Basic computer skills and proficiency with office software and productivity tools. - Demonstrated knowledge of Microsoft Office Suite (Word, PowerPoint, Excel). Physical Demands: - Ability to sit, stand, stoop, reach, lift (up to 10 lbs.), bend, etc. - Hand and wrist dexterity to utilize the computer. - May require travel to sites/program and special functions. Environmental Conditions Critical To Performance: - Work is in an office environment, climate controlled through central air conditioning/heating. - Ability to be qualified physically for respirator use, initially and ongoing as required. - May have some exposure to outside environment while traveling. ITAR Requirement: - This position requires access to information that is subject to compliance with the International Traffic Arms Regulations (“ITAR”) and/or the Export Administration Regulations (“EAR”). In order to comply with the requirements of the ITAR and/or the EAR, applicants must qualify as a U.S. person under the ITAR and the EAR, or a person to be approved for an export license by the governing agency whose technology comes under its jurisdiction. Please understand that any job offer that requires approval of an export license will be conditional on AeroVironment’s determination that it will be able to obtain an export license in a time frame consistent with AeroVironment’s business requirements. A “U.S. person” according to the ITAR definition is a U.S. citizen, U.S. lawful permanent resident (green card holder), or protected individual such as a refugee or asylee. See 22 CFR 120.15. Some positions will require current U.S. Citizenship due to contract requirements. We could include that as part of Requirements. Now Benefits: - AV offers an excellent benefits package including medical, dental vision, 401K with company matching, a 9/80 work schedule and a paid holiday shutdown. - For more information about our company benefit offerings please visit: http://www.avinc.com/myavbenefits. - We also encourage you to review our company website at http://www.avinc.com to learn more about us. But we should remove application instructions? The Benefits paragraph includes links; those are not application instructions but informational. We can keep. Now Schedule: - a 9/80 work schedule (mentioned in Benefits). Also maybe we can note that as schedule. Thus Schedule section: "9/80 work schedule". Now About the company: "Who We Are" paragraph(s): "Based in California, AeroVironment (AVAV) is a global leader in unmanned aircraft systems (UAS) and tactical missile systems. Founded in 1971 by celebrated physicist and engineer, Dr. Paul MacCready, we’ve been at the leading edge of technical innovation for more than 45 years. Be a part of the team that developed the world’s most widely used military drones and created the first submarine-launched reconnaissance drone, and has seven innovative vehicles that are part of