Security Specialist (IBST)-Junior
AMEWAS · Patuxent River, MD · 4 wk ago
On-siteInformation Technology$64k–$78k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Also remove referral friend? That's maybe not boilerplate but could be considered not essential? It's not a duty/requirement/benefit; it's a referral program mention. Might be considered not essential but could be kept? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Referral friend is not those; but it's not a duty/requirement/benefit. Might be considered fluff. Safer to omit? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The referral friend is substantive? It's a perk but not part of benefits? Could be considered part of benefits? Might be okay to keep under Benefits? But we have a Benefits section already listing many benefits; referral bonus could be added there. However we must not invent content; we can include it if present. The text includes: "Refer a Friend We’re always on the lookout for top talent. If you know someone who would be a great fit for this role, please share our post with them! Here’s an added perk: If you’re a current AMEWAS employee and your referral is hired, you could earn a referral bonus!" That's a referral program. Could be considered a benefit/perk. We could include under Benefits as an item. But we must not create sections unless posting has real specific content for it. Benefits section is present: they list many benefits. So we can include Benefits
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Also remove referral friend? That's maybe not boilerplate but could be considered not essential? It's not a duty/requirement/benefit; it's a referral program mention. Might be considered not essential but could be kept? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Referral friend is not those; but it's not a duty/requirement/benefit. Might be considered fluff. Safer to omit? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The referral friend is substantive? It's a perk but not part of benefits? Could be considered part of benefits? Might be okay to keep under Benefits? But we have a Benefits section already listing many benefits; referral bonus could be added there. However we must not invent content; we can include it if present. The text includes: "Refer a Friend We’re always on the lookout for top talent. If you know someone who would be a great fit for this role, please share our post with them! Here’s an added perk: If you’re a current AMEWAS employee and your referral is hired, you could earn a referral bonus!" That's a referral program. Could be considered a benefit/perk. We could include under Benefits as an item. But we must not create sections unless posting has real specific content for it. Benefits section is present: they list many benefits. So we can include Benefits with - items.
Pay: they give salary range $64,100.00 - $78,400.00 and is commensurate with experience. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state salary range, so we can include Pay section. However they also say "commensurate with experience" which is filler? It's part of the description but we must not include filler text. We should include the salary range but maybe omit the phrase "commensurate with experience". The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", ...). That suggests we should not include that phrase as content under Pay heading. So we can put just the salary range.
Schedule: they mention remote/hybrid work arrangements subject to business etc. Also "This position is not eligible for remote work; on-site support is required." Also "Work Arrangement Remote or hybrid work arrangements are subject to business, contract, customer, and/or government requirements and may be modified or discontinued as needed. The Company reserves the right to require an employee to report to a designated Company or customer worksite when business or contractual requirements change." So we have info about work arrangement: on-site required, not eligible for remote. That's schedule/location info. We can include Schedule section with that info. Must avoid filler like "varies". We can summarize: On-site support required; remote work not eligible. That's specific.
About the role: we have a paragraph at start: "At AMEWAS, we don’t just support defense- we shape it.... Come do work that matters. Join AMEWAS." That's generic company overview. Might be considered About the role? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role heading with that descriptive paragraph. However we must not repeat job title as heading. That's fine.
Responsibilities: we have "A typical day as a Security Specialist (IBST)-Junior may include:" followed by bullet-like sentences (though not bullet list). We need to convert to - . The sentences:
- Learns how to meet the requirements of DoD 5205.07 volumes 1-4 for one or more Special Access Programs (SAP) within the Combined Security Office (CSO)
- Initiates, processes, and tracks personnel security actions such as Personnel Access Requests (PARs), nominations for employees to special programs, and foreign travel and contact reports, briefings, and debriefings
- Interfaces with customer counterparts in a tactful, diplomatic, and professional manner
- Creates needed procedures for the secure and successful execution of assigned program(s)
- Administers and controls classified material following the National Industrial Security Program Operating Manual (NISPOM)
- Plans and supervises the building and accreditation of secure facilities following Intelligence Community Directive 705
We'll put each as
- .
Requirements: They have "Must-haves" list: HS Diploma or equivalent, 1 year of relevant work experience, 1 year of experience in an administrative assistant or security operations support role, Proficiency in MS Office, Willingness to work in a Secured environment, Willingness to obtain certifications and clearances as required, Minimum clearance required to apply (candidates who do not currently hold the required clearance will not be considered): N/A, Current clearance required upon onboarding: Top Secret, Additional Accesses: The ability to obtain and maintain the DoD security clearance eligibility and/or additional security access requirements necessary to perform the duties of the position, as required by the contract.
We need to preserve all substantive info. Some items like "Minimum clearance required to apply (candidates who do not currently hold the required clearance will not be considered): N/A" includes N/A which is filler; we should not include filler. So we can omit that line. "Current clearance required upon onboarding: Top Secret" is substantive. "Additional Accesses: The ability to obtain and maintain the DoD security clearance eligibility and/or additional security access requirements necessary to perform the duties of the position, as required by the contract." That's substantive.
We also have "Desired Skills" list: Knowledge of JADE, DISS, and SAP security requirements, Experience working in a security environment as a Federal or contracted employee, Experience working in a secured environment, Thorough knowledge and demonstrated application of the U.S. Government security standards of 32 Code of Federal Regulation Part 117, NISPOM, Intelligence Community Directives, Security Executive Agent Directives, and the DoD SAP Security Manual 5205.07 (Volumes 1- 4), Extensive understanding and previous application of the ICD-705 Technical Specifications, including, but not limited to, intrusion detection systems, access control devices, TEMPEST requirements, and drawings/specifications, Understanding of advanced security principles and government special security regulations.
We could treat Desired Skills as part of Skills section. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Skills heading that includes both Must-haves and Desired Skills? Or separate Requirements and Qualifications? They have Must-haves (requirements) and Desired Skills (preferred). Could map Must-haves to Requirements, Desired Skills to Skills or Qualifications. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? But we need to follow headings list; we can include Requirements and Skills. Qualifications maybe not needed if content overlaps. Let's decide: Use Requirements for Must-haves (including education, experience, proficiency, willingness, clearance). Use Skills for Desired Skills list (knowledge of JADE etc). Also we could include Qualifications if there is distinct content; but we can skip Qualifications to avoid thin section.
Benefits: list many items: Medical, dental, vision, 401(k), Life/AD&D/STD/LTD insurance, Paid vacation, holiday and sick leave, Generous tuition and training assistance program, Relocation assistance, Sign-on bonuses, Employee longevity recognition, Community involvement and outreach, Team building events, Recognition program, Wellness program, Employee Assistance Program (EAP), Mobile service discount, Fitness reimbursement program. Also referral bonus? Could add as item.
Pay: salary range.
Schedule: on-site required, remote not eligible.
Also we have location info: "About the location: Patuxent River, MD, located in the California-Lexington Park area, is Maryland’s #1 City Hiring the Most High-Tech Workers. To learn more about the surrounding area, please visit: www.visitstmarysmd.com". This is location detail; could be part of About the role or maybe a separate section? Not in headings list. Could be included in About the role paragraph. We'll incorporate location info into About the role.
We must remove boilerplate: "Employment Eligibility and Sponsorship Disclaimer: Applicants must be currently authorized to work in the United States on a full-time basis. AMEWAS is unable to provide employment-based visa sponsorship for this position now or in the future." That's boilerplate? It's about eligibility; maybe considered legal? Might be considered boilerplate but it's substantive about eligibility. However instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is legal/eligibility disclaimer; likely to remove. Also "Security Clearance Requirement Disclaimer: This position requires the ability to obtain and maintain all security clearances, interim security determinations, and/or other access authorizations required by the applicable contract(s). Candidates who are unable to obtain the required interim clearance or access authorization within the timeframe necessary to meet business and contract requirements may no longer be considered for employment." That's also legal disclaimer; remove. Also "AMEWAS is committed to equal employment opportunity..." remove. Also "For important employment-related notices..." remove. Also "AMEWAS participates in E-Verify..." remove. Also "Please note: AMEWAS does not accept unsolicited resumes from third-party staffing agencies..." remove.
Also "Refer a Friend" we might keep as benefit? It's not a standard benefit but could be considered a perk. Might keep under Benefits as item.
Now construct HTML.
Structure:
About the role
At AMEWAS, we don’t just support defense— we shape it. For over 40 years, we’ve been a trusted partner of the Department of Defense (DoD) by providing cutting-edge engineering, testing, and evaluation for U.S. Navy weapons systems. Our people are the heart of our mission. Across our headquarters in California, Maryland, and offices in Orlando, FL, and San Diego, CA, you'll find a diverse and driven team committed to making a real impact for our Nation’s Warfighters. If you're ready to grow your skills, be challenged by meaningful work, and contribute to something bigger…this is where you belong. Come do work that matters. Join AMEWAS. The Position AMEWAS is seeking a highly motivated and talented Security Specialist (IBST)-Junior to support Advanced Aircraft Research, Development, Test & Evaluation. About the location: Patuxent River, MD, located in the California-Lexington Park area, is Maryland’s #1 City Hiring the Most High-Tech Workers. To learn more about the surrounding area, please visit: www.visitstmarysmd.com
But we need to avoid repeating job title as heading; we already have heading About the role, not job title. The paragraph includes "The Position AMEWAS is seeking a highly motivated and talented Security Specialist (IBST)-Junior to support Advanced Aircraft Research, Development, Test & Evaluation." That's okay.
Now Responsibilities:
Responsibilities
- items.
Pay: they give salary range $64,100.00 - $78,400.00 and is commensurate with experience. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state salary range, so we can include Pay section. However they also say "commensurate with experience" which is filler? It's part of the description but we must not include filler text. We should include the salary range but maybe omit the phrase "commensurate with experience". The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", ...). That suggests we should not include that phrase as content under Pay heading. So we can put just the salary range.
Schedule: they mention remote/hybrid work arrangements subject to business etc. Also "This position is not eligible for remote work; on-site support is required." Also "Work Arrangement Remote or hybrid work arrangements are subject to business, contract, customer, and/or government requirements and may be modified or discontinued as needed. The Company reserves the right to require an employee to report to a designated Company or customer worksite when business or contractual requirements change." So we have info about work arrangement: on-site required, not eligible for remote. That's schedule/location info. We can include Schedule section with that info. Must avoid filler like "varies". We can summarize: On-site support required; remote work not eligible. That's specific.
About the role: we have a paragraph at start: "At AMEWAS, we don’t just support defense- we shape it.... Come do work that matters. Join AMEWAS." That's generic company overview. Might be considered About the role? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role heading with that descriptive paragraph. However we must not repeat job title as heading. That's fine. Responsibilities: we have "A typical day as a Security Specialist (IBST)-Junior may include:" followed by bullet-like sentences (though not bullet list). We need to convert to
- . The sentences: - Learns how to meet the requirements of DoD 5205.07 volumes 1-4 for one or more Special Access Programs (SAP) within the Combined Security Office (CSO) - Initiates, processes, and tracks personnel security actions such as Personnel Access Requests (PARs), nominations for employees to special programs, and foreign travel and contact reports, briefings, and debriefings - Interfaces with customer counterparts in a tactful, diplomatic, and professional manner - Creates needed procedures for the secure and successful execution of assigned program(s) - Administers and controls classified material following the National Industrial Security Program Operating Manual (NISPOM) - Plans and supervises the building and accreditation of secure facilities following Intelligence Community Directive 705 We'll put each as
- .
Requirements: They have "Must-haves" list: HS Diploma or equivalent, 1 year of relevant work experience, 1 year of experience in an administrative assistant or security operations support role, Proficiency in MS Office, Willingness to work in a Secured environment, Willingness to obtain certifications and clearances as required, Minimum clearance required to apply (candidates who do not currently hold the required clearance will not be considered): N/A, Current clearance required upon onboarding: Top Secret, Additional Accesses: The ability to obtain and maintain the DoD security clearance eligibility and/or additional security access requirements necessary to perform the duties of the position, as required by the contract.
We need to preserve all substantive info. Some items like "Minimum clearance required to apply (candidates who do not currently hold the required clearance will not be considered): N/A" includes N/A which is filler; we should not include filler. So we can omit that line. "Current clearance required upon onboarding: Top Secret" is substantive. "Additional Accesses: The ability to obtain and maintain the DoD security clearance eligibility and/or additional security access requirements necessary to perform the duties of the position, as required by the contract." That's substantive.
We also have "Desired Skills" list: Knowledge of JADE, DISS, and SAP security requirements, Experience working in a security environment as a Federal or contracted employee, Experience working in a secured environment, Thorough knowledge and demonstrated application of the U.S. Government security standards of 32 Code of Federal Regulation Part 117, NISPOM, Intelligence Community Directives, Security Executive Agent Directives, and the DoD SAP Security Manual 5205.07 (Volumes 1- 4), Extensive understanding and previous application of the ICD-705 Technical Specifications, including, but not limited to, intrusion detection systems, access control devices, TEMPEST requirements, and drawings/specifications, Understanding of advanced security principles and government special security regulations.
We could treat Desired Skills as part of Skills section. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Skills heading that includes both Must-haves and Desired Skills? Or separate Requirements and Qualifications? They have Must-haves (requirements) and Desired Skills (preferred). Could map Must-haves to Requirements, Desired Skills to Skills or Qualifications. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? But we need to follow headings list; we can include Requirements and Skills. Qualifications maybe not needed if content overlaps. Let's decide: Use Requirements for Must-haves (including education, experience, proficiency, willingness, clearance). Use Skills for Desired Skills list (knowledge of JADE etc). Also we could include Qualifications if there is distinct content; but we can skip Qualifications to avoid thin section. Benefits: list many items: Medical, dental, vision, 401(k), Life/AD&D/STD/LTD insurance, Paid vacation, holiday and sick leave, Generous tuition and training assistance program, Relocation assistance, Sign-on bonuses, Employee longevity recognition, Community involvement and outreach, Team building events, Recognition program, Wellness program, Employee Assistance Program (EAP), Mobile service discount, Fitness reimbursement program. Also referral bonus? Could add as item. Pay: salary range. Schedule: on-site required, remote not eligible. Also we have location info: "About the location: Patuxent River, MD, located in the California-Lexington Park area, is Maryland’s #1 City Hiring the Most High-Tech Workers. To learn more about the surrounding area, please visit: www.visitstmarysmd.com". This is location detail; could be part of About the role or maybe a separate section? Not in headings list. Could be included in About the role paragraph. We'll incorporate location info into About the role. We must remove boilerplate: "Employment Eligibility and Sponsorship Disclaimer: Applicants must be currently authorized to work in the United States on a full-time basis. AMEWAS is unable to provide employment-based visa sponsorship for this position now or in the future." That's boilerplate? It's about eligibility; maybe considered legal? Might be considered boilerplate but it's substantive about eligibility. However instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is legal/eligibility disclaimer; likely to remove. Also "Security Clearance Requirement Disclaimer: This position requires the ability to obtain and maintain all security clearances, interim security determinations, and/or other access authorizations required by the applicable contract(s). Candidates who are unable to obtain the required interim clearance or access authorization within the timeframe necessary to meet business and contract requirements may no longer be considered for employment." That's also legal disclaimer; remove. Also "AMEWAS is committed to equal employment opportunity..." remove. Also "For important employment-related notices..." remove. Also "AMEWAS participates in E-Verify..." remove. Also "Please note: AMEWAS does not accept unsolicited resumes from third-party staffing agencies..." remove. Also "Refer a Friend" we might keep as benefit? It's not a standard benefit but could be considered a perk. Might keep under Benefits as item. Now construct HTML. Structure:
About the role
At AMEWAS, we don’t just support defense— we shape it. For over 40 years, we’ve been a trusted partner of the Department of Defense (DoD) by providing cutting-edge engineering, testing, and evaluation for U.S. Navy weapons systems. Our people are the heart of our mission. Across our headquarters in California, Maryland, and offices in Orlando, FL, and San Diego, CA, you'll find a diverse and driven team committed to making a real impact for our Nation’s Warfighters. If you're ready to grow your skills, be challenged by meaningful work, and contribute to something bigger…this is where you belong. Come do work that matters. Join AMEWAS. The Position AMEWAS is seeking a highly motivated and talented Security Specialist (IBST)-Junior to support Advanced Aircraft Research, Development, Test & Evaluation. About the location: Patuxent River, MD, located in the California-Lexington Park area, is Maryland’s #1 City Hiring the Most High-Tech Workers. To learn more about the surrounding area, please visit: www.visitstmarysmd.com
But we need to avoid repeating job title as heading; we already have heading About the role, not job title. The paragraph includes "The Position AMEWAS is seeking a highly motivated and talented Security Specialist (IBST)-Junior to support Advanced Aircraft Research, Development, Test & Evaluation." That's okay. Now Responsibilities:Responsibilities