SIMULATOR TECH I
NOVA Technologies · Dyess, AR · 1 mo ago
On-siteEngineeringFull-time
We need to output only HTML fragment with sections: headings
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, duplicate lines, application instructions, EEO, etc. We need to parse the posting. Key sections: - About the role / Opportunity: "THE OPPORTUNITY Support C-130J MATS training operations at Dyess AFB by maintaining, operating, troubleshooting, and documenting training-device systems. As a Simulator Technician I, you'll perform routine technical work using established procedures and technical data while developing proficiency across device systems and subsystems." - Responsibilities: "WHAT YOU'LL DO ..." list of duties. - Requirements / Qualifications: "WHAT YOU'LL BRING ..." includes high school diploma, 2 years experience, ability to use technical manuals, physical requirements, CompTIA Security+, DoD Secret clearance. - What would set you apart: "WHAT WOULD SET YOU APART ..." includes associate's degree, experience, EDMS. - Position Details: location, schedule, travel, security. - Compensation and Benefits: "COMPENSATION AND BENEFITS ..." says non-exempt hourly, compensation may be governed by federal wage-determination or CBA, benefits per CBA, NOVA plan. - About Nova Technologies: description. We need to decide which sections to output. Must include only sections with real specific content. Avoid filler like "commensurate with experience". The posting includes specifics: location, schedule, travel %, security clearance, compensation statement (though vague but mentions hourly, governed by wage-determination, CBA). Benefits: says benefits per CBA, NOVA plan terms. That's specific enough? It mentions benefits eligibility per CBA, NOVA plan terms and contract requirements. That's somewhat specific but not detailed. Probably we should include Benefits section if there is any mention. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state compensation: "This is a non-exempt position paid on an hourly basis. Compensation and benefits may be governed by applicable federal wage-determination or collective-bargaining requirements based on the assigned site and labor classification." That's stating compensation basis. So we can include Pay section with that sentence. Benefits: "Benefits and eligibility are provided in accordance with applicable CBA, NOVA plan terms and contract requirements." That's a statement about benefits. So we can include Benefits section. Schedule: The posting includes schedule details: "Schedule: Full-time, hourly, FLSA non-exempt, on-site position aligned to Government site hours. The source job description states 40 hours per work week and requires availability for evenings, weekends, overtime, and any shift or day of the week as program support requires." That's specific. So include Schedule section. Location: Could be part of About the role? But we could include a separate section? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Location is not listed as a possible heading; but we could embed location in About the role or maybe in a short paragraph. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So location can be folded into a short
maybe under About the role or as its own paragraph without heading. Probably we include location in a short paragraph after the heading About the role? But we need headings only for those categories. We could have a
that includes location and maybe travel. Travel: "Travel: Approximately 10%. Domestic and international travel may be required." That's specific; we could include under a heading? Not listed. Could fold into About the role or maybe a separate paragraph under About the role. We need to avoid duplication. Let's structure:
About the role
Support C-130J MATS training operations at Dyess AFB by maintaining, operating, troubleshooting, and documenting training-device systems. As a Simulator Technician I, you'll perform routine technical work using established procedures and technical data while developing proficiency across device systems and subsystems. Location: Dyess AFB, TX. Travel: Approximately 10% domestic and international.
Responsibilities
- Prepare, operate, and support C-130J MATS training devices for student and instructor use, including setup, readiness testing, initialization, DMO activities, and mission support.
- Troubleshoot routine initialization, operational, electronic-circuit, and equipment issues using maintenance manuals, technical data, wiring diagrams, schematics, and test equipment.
- Perform preventive maintenance, system readiness testing, pre- and post-operational checkouts, basic simulator modifications, and parts replacement under established procedures and technical guidance.
- Document maintenance and repair activity in EDMS, including work orders, repair actions, equipment status, off-site repairs, and calibration requirements.
- Support inventory accountability by receiving, storing, issuing, marking, packaging, shipping, inspecting, and tracking parts, supplies, and equipment.
- Provide basic networking/information-systems support on training devices and networks and communicate through phone, inter-phone, and radio circuits as required.
- Follow site safety, technical, operational, and program procedures and develop proficiency across assigned device systems and subsystems.
Requirements
- High school diploma or equivalent.
- Two (2) years of related experience may substitute for the absence of a technical college degree; may substitute with equivalent military or additional related experience.
- Ability to use technical manuals, diagrams, electrical schematics, test equipment, and maintenance procedures to perform routine technical work and troubleshoot problems.
- Ability to meet the physical requirements of the role, including lifting at least 40 pounds overhead, climbing into simulator or aircraft cockpit areas, and stooping, bending, or crawling around training devices.
- CompTIA Security+ certification.
- DoD Secret clearance or the ability to obtain and maintain a Secret clearance.
Qualifications
Maybe we can combine Requirements and Qualifications? The instruction lists both as possible headings. We have "WHAT YOU'LL BRING" which is requirements. "WHAT WOULD SET YOU APART" is qualifications/preferred. So we can have Requirements (mandatory) and Qualifications (preferred). Let's do that.Qualifications
- Associate's degree or technical college education in electronics, avionics, simulation systems, information systems, or a related technical field.
- Experience supporting aircraft training devices, simulators, electronics maintenance, networking/information systems, inventory control, or military aviation training environments.
- Experience with EDMS or comparable maintenance and inventory-management systems.
Skills
We could include technical skills like using manuals, test equipment, networking support, etc. But we already covered many in requirements. Could still add a Skills section summarizing: technical troubleshooting, preventive maintenance, documentation, inventory, basic networking, safety compliance. But we must not invent content; we can derive from posting. The posting mentions ability to use technical manuals, diagrams, schematics, test equipment, maintenance procedures; ability to meet physical requirements; CompTIA Security+; DoD Secret; etc. Those are more qualifications than skills. However we could still create a Skills section with items like: technical troubleshooting, preventive maintenance, system documentation, inventory management, basic networking/information systems support, safety and procedural compliance. That is derived from responsibilities. It's okay as long as we don't invent. It's basically summarizing responsibilities. Might be acceptable. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe we skip Skills to avoid thin section. We already have About the role, Responsibilities, Requirements, Qualifications, Pay, Benefits, Schedule. That's 7 sections. Could be okay. Pay section:Pay
This is a non-exempt position paid on an hourly basis. Compensation may be governed by applicable federal wage‑determination or collective‑bargaining requirements based on the assigned site and labor classification.
Benefits section:Benefits
Benefits and eligibility are provided in accordance with applicable CBA, NOVA plan terms and contract requirements.
Schedule section:Schedule
Full‑time, hourly, FLSA non‑exempt, on‑site position aligned to Government site hours. The role averages 40 hours per work week and requires availability for evenings, weekends, overtime, and any shift or day of the week as program support requires.
We might also include location and travel in About the role paragraph as we did. We must not include boilerplate like EEO, application instructions, accommodation, etc. Also must not include "About NOVA Technologies" maybe? That's not required but could be considered "About the company". Not in allowed headings list. Could we include a section like "About the company"? Not in list; better to omit. 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