Lead, Avionics Install - 1113
West Star Aviation Inc. · Perryville, MO · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent. Remove boilerplate.
We need to parse the posting.
Let's extract sections:
- About the role: The paragraph after "What you can expect as a Lead Avionics Install Technician at West Star:" includes description of role. Could be considered About the role. Also earlier paragraph about company culture maybe not needed.
- Responsibilities: The bullet list of duties: many sentences describing duties. We'll need to list them as
- . Must not duplicate.
- Requirements: Education, Experience, Initiative, Sense of Responsibility, Physical Requirements, Mental Requirements, Supervision, Working Conditions, Equipment Used. Possibly separate sections: Qualifications (Education, Experience), Skills (Initiative, Sense of Responsibility, etc.), but we can follow instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include.
We have content for:
- About the role: description of role.
- Responsibilities: list of duties.
- Requirements: maybe combine Education, Experience, Physical, Mental, etc. Could be "Requirements". Or we could split into Qualifications (Education, Experience) and Skills (Initiative, Sense of Responsibility, etc.). But we need to avoid thin sections. Let's see what we have.
Education: "Your Education What you’ll need to bring with you: A High school diploma or equivalent. Electrical tech school. Aircraft specific factory training preferred. A valid driver’s license approved for airline travel and/or a valid passport is ideal, but not mandatory. Aircraft specific factory training is preferred."
Experience: "Your Experience 8+ years prior experience on aircraft avionics system installation, troubleshooting and maintenance. 2+ years of corporate aircraft experience. Advanced knowledge and use of Corridor systems is preferred."
Initiative: "Your Initiative We’re looking for a team player who is self-motivated and able to perform in a fast paced environment where working under specific deadlines and time constraints will be common."
Sense Of Responsibility: list of items: Attend work every day as scheduled to include overtime and weekend assignments. Notify supervisor in advance of shift starting if unable to work. Must have reliable transportation to get to work each and every day. Must perform all work in accordance with Federal Aviation Administration guidelines. Follow all company and safety rules during performance of duties. Maintain customer oriented work habits. Direct the work and flow of multiple projects. Supervision of team members in daily operations and duties. Completion of work orders, FAA paperwork.
Physical Requirements: list.
Mental Requirements: list.
Supervision: "Will directly supervise multiple technicians. Will work under supervision of assigned Team Leader and Operations Manager. Work with other Team Leaders on multiple projects in a cooperative manner."
Working Conditions: description.
Equipment Used: list.
Compensation & Benefit Information: includes shift differential, semi-annual discretionary bonus, 401(k) company match, employer contribution to HSA. Also "Benefits Effective Day One for Eligible Employees" list.
Pay: Not explicit salary numbers, but mention "Weekly Competitive & Industry Leading Pay means you are paid more often". That's not a specific number; but we might still include Pay section if there is any mention of pay. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Weekly Competitive & Industry Leading Pay means you are paid more often". That's a statement about pay frequency, not amount. Could be considered Pay info. Also "Additional compensation in the form of a shift differential will be provided if the employee is assigned to an alternate shift. Other forms of compensation include a semi-annual discretionary bonus, 401(k) company match and employer contribution to a Health Savings Account (HSA)." That's compensation details. So we can include Pay section with those details.
Schedule: Not explicitly stated; maybe "Weekly Competitive & Industry Leading Pay means you are paid more often" implies weekly pay, but schedule of work hours not given. There's mention of shift differential for alternate shift, but not schedule. No explicit schedule like "Monday-Friday 8am-5pm". So we should not create Schedule section.
Benefits: we have benefits list: Medical, Dental and Vision Coverage with HSA and FSA options, Life Insurance, Disability Benefits & Supplemental Benefits, 401(k) Plan with Employee Contributions & Employer Match, Paid Company Holidays & Weekly Paid Time Off Accruals, Flexible Work Schedules include 5x8, 4x10 and 3x12, Weekly Competitive & Industry Leading Pay means you are paid more often, Bonus Opportunity based on Company and Site Performance, Internal Mobility & Career Advancement opportunities. Also "Benefits Effective Day One for Eligible Employees". So we can include Benefits section.
Now we need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also "Qualifications" for education/experience, "Skills" for initiative, sense of responsibility, etc. But we could combine education/experience into Requirements, and initiative/sense of responsibility into Skills. However we must not create thin sections. Let's see if we have enough content for each.
We could do:
- About the role (description)
- Responsibilities (list of duties)
- Requirements (Education + Experience + Physical + Mental + Supervision + Working Conditions + Equipment Used) maybe too big but okay.
- Skills (Initiative, Sense of Responsibility) maybe thin but we can include.
- Benefits (list)
- Pay (compensation details)
We should not include Schedule.
We must not repeat job title. Must not include metadata like Job ID, location? The location is part of posting but maybe we can include location in About the role? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could include in a short p at top maybe. But we need to preserve ALL substantive information; location is substantive? It's location of job. Might be considered metadata but still substantive. The instruction says fold minor metadata into a short
or drop it. Location could be considered minor metadata; we could include in a short p at beginning. However we also have About the role section; we could preface with a p containing location and employment type. But we need to avoid repeating job title. The posting includes "Full Time On-Site Perryville, MO 63775, USA". We could include that in a p. We must not include boilerplate like "Apply", "Privacy Policy", etc. Now craft HTML. We'll start with a p for location and employment type: maybe "
Full Time On‑Site – Perryville, MO 63775, USA
". Then About the role:About the role
...
Responsibilities:Responsibilities
- ... each duty as li
Requirements
- ... maybe combine many items
Skills
- ... initiative, sense of responsibility items
Benefits
- ... benefits
Pay
- ... compensation details