Training Expert - Signals Intelligence (SIGINT)
ASEC · Jacksonville, FL · 1 mo ago
On-siteHuman ResourcesFull-time
We need to output HTML fragment with sections: headings using for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, duplicated lines, application instructions. Also remove "Who We Are" maybe? It's not a required heading but could be considered "About the role"? Actually "Who We Are" is about company, not role. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings if present. The posting includes: Description (What You'll Do) -> could be About the role or Responsibilities. There's a "Key Responsibilities:" list. There's "Requirements What You'll Bring:" with Required Qualifications, Preferred Qualifications, Equally Important (soft skills). There's also "Security Clearance Requirement:" which is a qualification. There's also "Who We Are:" and "Why work at ASEC?" which includes benefits etc. There's also "Not the right opportunity..." etc which is boilerplate.
We need to include sections only when posting has real specific content. So we can have:
-
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, duplicated lines, application instructions. Also remove "Who We Are" maybe? It's not a required heading but could be considered "About the role"? Actually "Who We Are" is about company, not role. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings if present. The posting includes: Description (What You'll Do) -> could be About the role or Responsibilities. There's a "Key Responsibilities:" list. There's "Requirements What You'll Bring:" with Required Qualifications, Preferred Qualifications, Equally Important (soft skills). There's also "Security Clearance Requirement:" which is a qualification. There's also "Who We Are:" and "Why work at ASEC?" which includes benefits etc. There's also "Not the right opportunity..." etc which is boilerplate.
We need to include sections only when posting has real specific content. So we can have:
- About the role
with paragraph summarizing the description? But we must preserve ALL substantive information; we cannot summarize away detail. However we can keep the description as prose in
. The description includes multiple sentences; we can keep them as is. -
Responsibilities
with- for each bullet from Key Responsibilities.
-
Requirements
maybe combine Required Qualifications, Preferred Qualifications, Equally Important, Security Clearance Requirement. Could also split into Qualifications and Skills. The instruction says we can use Qualifications and Skills headings. We need to decide. We have Required Qualifications (5 years related technical experience, SIGINT SME with 5 years SIGINT collection and operational watch floor experience, MPTOD, IO Aperture, Point Guard, and One Roof operational experience). Preferred Qualifications (Military SIGINT Signals Analyst program graduates, VQ Special Evaluator (SPECEVAL) or Supervisor (SPECSUP) instructor, MQ-4C SC instructor, Training material development and instructional experience). Equally Important (soft skills). Security Clearance Requirement (US citizenship and active DoD Top Secret/SCI clearance). We could put these underRequirements
with sub-sections? But we only allowed headings as listed; we could still useRequirements
and then within that useor
- . We must not invent headings not listed. So we can put all under Requirements.
Alternatively we could split into Qualifications and Skills. The Equally Important are skills. So we could have
Qualifications
for required/preferred qualifications and security clearance, andSkills
for the soft skills. That seems appropriate. We also have Benefits: from "Why work at ASEC?" includes: 100% employee-owned company, ESOP, Comprehensive benefits package including 11 paid holidays, medical/dental/vision coverage, HSA/FSA options, disability insurance, 401(k) with company match, Tuition assistance, Veteran-friendly employer, Thriving employee culture. That's benefits. So we can haveBenefits
with- .
Pay and Schedule: Not mentioned. So we should NOT create Pay or Schedule sections.
About the role: we have description "What You’ll Do:" plus maybe location and telework eligibility. That's substantive. So we can have About the role paragraph.
We must not include boilerplate like "ASEC is an Equal Opportunity Employer..." etc. Also remove "Not the right opportunity for you? Send this job posting to a friend!" etc. Also remove "Who We Are:" maybe? That is not required heading but could be considered About the role? However we already have About the role covering job description. "Who We Are:" is company description; could be considered part of About the role? But the instruction says we can use About the role heading for section headings. It didn't forbid including company info there. But we should preserve all substantive information; "Who We Are:" is substantive about the company. Should we include it? It might be considered part of About the role or maybe we could create a separate section but not in allowed headings. Since only allowed headings are those listed, we could fold company info into About the role paragraph. That would preserve it.
Similarly "Why work at ASEC?" is benefits; we already captured benefits.
Thus final HTML:
About the role
As the Training Expert - Signals Intelligence (SIGINT), you will provide support in the development and delivery of Distributed SIGINT Operations (DSO) training services. This position will be based in Jacksonville, FL and is not eligible for telework. In this role, you will develop the material required to train DSO watch floor operators providing SIGINT signals analysis and collection support to Naval Aviation operations, and you will create and deliver curriculum and courseware to accomplish training in accordance with Navy schedules. ASEC offers meaningful, mission-driven work within a culture that supports your professional and personal growth. We partner with our government customers to deliver innovative solutions across engineering, information technology, training, and logistics. Above all, we are committed to doing what’s right for the Warfighter—plain and simple. ASEC is a 100% employee-owned company with an Employee Stock Ownership Plan (ESOP).
But we need to preserve all substantive info: we must not lose any details from description. Let's extract the description exactly: "What You’ll Do: As the Training Expert - Signals Intelligence (SIGINT), you will provide support in the development and delivery of Distributed SIGINT Operations (DSO) training services. This position will be based in Jacksonville, FL and is not eligible for telework. In this role, you will develop the material required to train DSO watch floor operators providing SIGINT signals analysis and collection support to Naval Aviation operations, and you will create and deliver curriculum and courseware to accomplish training in accordance with Navy schedules." Then later: "Who We Are: ASEC offers meaningful, mission-driven work within a culture that supports your professional and personal growth. We partner with our government customers to deliver innovative solutions across engineering, information technology, training, and logistics. Above all, we are committed to doing what’s right for the Warfighter—plain and simple. Explore what makes ASEC different by visiting our website." Then "Why work at ASEC? 100% employee-owned company. Learn more about our Employee Stock Ownership Plan (ESOP) here!Comprehensive benefits package, including 11 paid holidays, medical/dental/vision coverage, HSA/FSA options, disability insurance, and more!401(k) with company matchTuition assistance for undergraduate and graduate educationVeteran-friendly employerThriving employee culture" We need to keep all that. So About the role paragraph could combine the description, Who We Are, and Why work at ASEC? but we might separate Benefits. However Benefits section will list benefits; we should not duplicate. So About the role could include the description and Who We Are (company mission). Benefits section will list the benefits. Thus About the role paragraph: combine the description and Who We Are. Let's craft:As the Training Expert - Signals Intelligence (SIGINT), you will provide support in the development and delivery of Distributed SIGINT Operations (DSO) training services. This position will be based in Jacksonville, FL and is not eligible for telework. In this role, you will develop the material required to train DSO watch floor operators providing SIGINT signals analysis and collection support to Naval Aviation operations, and you will create and deliver curriculum and courseware to accomplish training in accordance with Navy schedules. ASEC offers meaningful, mission-driven work within a culture that supports your professional and personal growth. We partner with our government customers to deliver innovative solutions across engineering, information technology, training, and logistics. Above all, we are committed to doing what’s right for the Warfighter—plain and simple.
That preserves description and Who We Are. The "Explore what makes ASEC different by visiting our website." is maybe boilerplate? It's a call to action; could be considered navigation? Might be considered boilerplate; we can drop it as it's not substantive? It's a generic invitation; but it's part of the posting. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Explore what makes ASEC different by visiting our website." is not exactly those but could be considered navigation? It's a link suggestion; maybe we can drop as it's not substantive. Safer to drop. Now Benefits section: we need to list all benefits from Why work at ASEC? plus maybe ESOP mentioned earlier. Benefits: 100% employee-owned company, Employee Stock Ownership Plan (ESOP), Comprehensive benefits package including 11 paid holidays, medical/dental/vision coverage, HSA/FSA options, disability insurance, 401(k) with company match, Tuition assistance for undergraduate and graduate education, Veteran-friendly employer, Thriving employee culture. We should keep each as list items. Now Responsibilities: list from Key Responsibilities: - Analyze and identify any potential training requirements that are not being addressed by current Navy SIGINT training with specific emphasis on the Triton program and associated DSO support provided by the regional Fleet Information Operations Centers (FIOCs). - Coordinate and organize technical and procedural information for implementation into DSO courseware. - Instruct DSO classroom lectures. - Assist with development and instruction of the SIGINT Coordinator Course and provide instructional support as needed. - Support the development of Mission Avionics System Trainer (MAST) entities and scenarios for Fleet Introduction Team (FIT) instructor and Fleet use. - Maintain relevant and current technical parametric data for training simulations. - Assist with fleet software transition teaches and simulator upgrades. - Research technical and procedural information related to Maritime Patrol & Reconnaissance Aircraft (MPRA) Intelligence Surveillance and Reconnaissance (ISR) related missions, testing and training. - Research and analyze intelligence sources for courseware development and fleet integration. - Offer recommendations and solutions to solve potential training gaps. We should keep them as - . Now Requirements: we have Required Qualifications, Preferred Qualifications, Equally Important (soft skills), Security Clearance Requirement. We could split into Qualifications and Skills. Qualifications: Required Qualifications + Preferred Qualifications + Security Clearance. Skills: Equally Important (soft skills). Let's list Required Qualifications: - Training Analyst requires a minimum of 5 years related technical experience. - SIGINT SME with 5 years of SIGINT collection and operational watch floor experience. - MPTOD, IO Aperture, Point Guard, and One Roof operational experience. Preferred Qualifications: - Military SIGINT Signals Analyst program graduates. - VQ Special Evaluator (SPECEVAL) or Supervisor (SPECSUP) instructor. - MQ-4C SC instructor. - Training material development and instructional experience. Security Clearance Requirement: - This position requires U.S. citizenship and an active DoD Top Secret/SCI clearance. - Selected candidate will be subject to a government security investigation and must meet eligibility requirements for access to classified information. We could combine as list items. Now Skills (Equally Important): - Ability to build positive, collaborative relationships across teams and with external partners. - Effective communicator with strong verbal and written skills. - Proactive, self-directed work style with the ability to operate independently. - Analytical thinker with proven problem-solving capabilities. - Highly organized, with the ability to balance competing priorities in a fast-paced environment. Now we need to ensure we don
- .
Pay and Schedule: Not mentioned. So we should NOT create Pay or Schedule sections.
About the role: we have description "What You’ll Do:" plus maybe location and telework eligibility. That's substantive. So we can have About the role paragraph.
We must not include boilerplate like "ASEC is an Equal Opportunity Employer..." etc. Also remove "Not the right opportunity for you? Send this job posting to a friend!" etc. Also remove "Who We Are:" maybe? That is not required heading but could be considered About the role? However we already have About the role covering job description. "Who We Are:" is company description; could be considered part of About the role? But the instruction says we can use About the role heading for section headings. It didn't forbid including company info there. But we should preserve all substantive information; "Who We Are:" is substantive about the company. Should we include it? It might be considered part of About the role or maybe we could create a separate section but not in allowed headings. Since only allowed headings are those listed, we could fold company info into About the role paragraph. That would preserve it.
Similarly "Why work at ASEC?" is benefits; we already captured benefits.
Thus final HTML:
- . We must not invent headings not listed. So we can put all under Requirements.
Alternatively we could split into Qualifications and Skills. The Equally Important are skills. So we could have