Assistant Facility Security Officer

We need to output HTML fragment with sections: About the role? Actually description includes "What You’ll Do:" which is responsibilities. Also "Skills" and "Additional Skills & Qualifications Required:" etc. Also "Pay And Benefits". Also "Workplace Type". Also "Job Type & Location". Also "Application Deadline". Also "About TEKsystems" etc but those are boilerplate; we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to keep substantive info: description of role, responsibilities, qualifications, skills, pay, benefits, workplace type, job type & location, maybe application deadline? The instruction says remove application instructions. Application deadline might be considered application instruction? It's not exactly instruction to apply but it's a deadline. Might be considered metadata; but they said "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Application deadline could be minor metadata; we could fold into a short p. However they also said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Application deadline is not exactly instruction but could be considered part of application instructions. Safer to drop it. Also "About TEKsystems" is boilerplate (company description) not specific to role; we should drop. Also "San Francisco Fair Chance Ordinance" etc are legal boilerplate; drop. Thus we keep: description paragraph about Bristol Bay Services, role purpose. Then "What You’ll Do:" responsibilities list. Then "Skills" maybe combine with "Additional Skills & Qualifications Required:" and "Preferred". We'll create sections: Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule? Actually schedule not given; we have Workplace Type (hybrid). Could treat as Schedule? Not exactly. They said use headings for Schedule if present. Not present. Workplace Type maybe we could put under a heading like "Workplace Type" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. "About the role" could be the introductory description. "Responsibilities" for What You’ll Do. "Requirements" or "Qualifications" for required qualifications. "Skills" for skills list. "Benefits" for benefits. "Pay" for pay range. "Schedule" maybe not present; we could omit. Workplace Type maybe could be included under About the role or Requirements? Could add a short p under About the role about location and hybrid. Or we could create a "Schedule" heading if we interpret hybrid as schedule? Not ideal. Better to omit schedule if not specified. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should not add Schedule if no content. So we omit Schedule. Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay. We need to decide between Requirements and Qualifications. The posting has "Additional Skills & Qualifications Required:" and also "Experience Level Intermediate Level". Could combine into Requirements. We'll use "Requirements" heading. Now we need to preserve all substantive information, not invent or summarize away detail. Must keep details like specific systems: DISS, NBIS, ACCS, SPOT, SWFT, STePP, DCSA, OPSEC, CUI, NCMS, etc. Also mention FCL profiles, NISS, DISS, etc. Also mention DD Form 254, etc. Also mention training: CDSE FSO Orientation for Non-Possessing Facilities IS020.CU course within last 5 years. Also mention ability to maintain US Top Secret clearance, must be US citizen, interim TS acceptable. Also mention high school diploma, 2 years experience, etc. Also mention proficiency with MS Office, etc. Also mention preferred: proficient experience with DISS/NBIS, ACCS, SPOT, SWFT, STePP account, familiarity with CDSE, detailed knowledge of 32 CFR Part 117, CUI and OPSEC policies, DCSA websites, current NCMS member. We need to keep all that. Now format: Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to avoid repeating job title as heading. The job title is Assistant Facility Security Officer; we should not put that as heading. We need to output only HTML fragment, no /, no markdown. Let's craft. First, About the role: a paragraph describing Bristol Bay Services, LLC is a Government Consulting and Contracting firm supporting missions worldwide. Seeking Assistant Facility Security Officer to join team. Role supports Security Department within corporate office across several companies and various agency contracts in San Antonio, TX. Also mention hybrid workplace? Could add location and hybrid in this paragraph. We'll include: "Bristol Bay Services, LLC is a Government Consulting and Contracting firm supporting missions throughout the world. The Assistant Facility Security Officer supports the Security Department within the corporate office across several companies and various agency contracts in San Antonio, TX. This is a hybrid position based in San Antonio, TX." Now Responsibilities: list from "What You’ll Do:" bullet points. We'll convert each sentence into

• . List: - Assist in the maintenance of FCL profiles, including submitting change condition packages and profile updates within NISS. - Receive and collect supporting data and assist with the submission, processing, and follow-through of incident reports and correspondence into the appropriate file/system within DISS. - Assist government agencies with the onboarding and offboarding of supporting contractor personnel within DISS, NBIS, ACCS, and SPOT, as well as command-specific access request letters or visit authorization letters. - Process visit requests for personnel, visits to outside agencies, and visitations from other organizations, including recurring visit requests in support of multiple contracts across several companies for the life cycle of the contract. - Coordinate within the Security Department to accurately track all training and briefing requirements for employee suitability status in accordance with contract and position requirements to properly determine, grant, and maintain access. - Conduct semi-annual self-inspections, update inspections and checklists for review by the Facility Security Officer, and support quarterly security wellness reviews alongside the Facility Security Officer. - Draft DD Form 254, source supplemental Security Classification Guides and policies, and maintain active working knowledge of systems of record and processing for solicitation Prime DD254 and flow-down subcontractor DD254. - Properly safeguard Privacy Act Protected Information, Personally Identifiable Information (PII), and Unclassified/Classified National Security Information, including Controlled Unclassified Information. - Effectively communicate with employees, hiring managers, other internal supporting departments, and external government agency personnel in support of background checks, inquiries, report generation, contract language and documentation, and maintenance of training and briefing records. Now Requirements: combine required qualifications. We need to list: - High school diploma. - Minimum of 2 years of experience in industry personnel security (government or contractor), preferably within DoD. - Demonstrated working-level experience managing personnel security IT systems and/or interpreting local personnel security agency checks, investigation status, and adjudications, as well as processing and generating DD254. - Ability to complete all necessary training in a timely fashion on a recurring basis to maintain eligibility for access to necessary government and organic systems. - Ability to maintain a U.S. Top Secret Security Clearance; must be a U.S. citizen. An interim TS is acceptable for hire. - Ability to work in a dynamic, fast-paced environment and effectively interact with numerous DoD, military/civilian personnel, and industry partners via telecommunication and written correspondence. - Working knowledge of Microsoft Office (Word, PowerPoint, and Excel), DISS/NBIS, NCAISS, NISS, ACCS, SPOT, SWFT, fingerprinting services, applicable FAR and DFAR clauses, and 32 CFR Part 117. - Detail-oriented, self-motivated, and able to work with minimal supervision. - Completion of the CDSE FSO Orientation for Non-Possessing Facilities IS020.CU course within the last 5 years. We could also include "Experience Level Intermediate Level" but that's redundant. Now Skills: combine skills list from "Skills" and "Additional Skills & Qualifications Required: Preferred". We'll list both required and preferred? The instruction: preserve ALL substantive information; we can include both required and preferred under Skills. But we already put required under Requirements. To avoid duplication, we could put required under Requirements and preferred under Skills. However the posting has a "Skills" section with list: Security clearance, Security, DISS/NBIS, Top Secret Clearance, DD254, Facility Security, NISS, personnel security, DoD Security, DISS, NBIS, ACCS, SPOT, SWFT, STePP, DCSA, OPSEC, CUI, NCMS Member Top Skills Details ... then "Additional Skills & Qualifications Required:" includes required items. Then "Preferred:" includes preferred items. Thus we could treat "Skills" heading for the skills list (both required and preferred). But we already used Requirements for required qualifications. Might be okay to have overlapping but we must not invent or summarize away detail. Duplication is okay? They said remove duplicated lines. So we should avoid duplicating same content. So we need to split: required qualifications go under Requirements; preferred skills go under Skills. Also the initial "Skills" bullet list includes many items that are also in required qualifications (like Security clearance, Top Secret Clearance, etc). Those are required; we could keep them under Requirements and not repeat under Skills. But the "Skills" list also includes items like DISS/NBIS, etc which are also in required. To avoid duplication, we could put all skill-related items under Skills and move experience/education under Requirements. However the instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications if needed. But we can just use Requirements for education/experience, and Skills for technical skills. Let's do that. Thus Requirements: education, experience, clearance, training, etc. Skills: list of systems and knowledge areas: Security clearance, Security, DISS/NBIS, Top Secret Clearance, DD254, Facility Security, NISS, personnel security, DoD Security, DISS, NBIS, ACCS, SPOT, SWFT, STePP, DCSA, OPSEC, CUI, NCMS Member, NCAISS, fingerprinting services, applicable FAR and DFAR clauses, 32 CFR Part 117, Microsoft Office (Word, PowerPoint, Excel), etc. Also mention "STePP account and familiarity with CDSE". Also "Detailed knowledge of 32 CFR Part 117, CUI and OPSEC policies, and DCSA websites." Also "Current NCMS member." Also "Proficient experience with DISS/NBIS, ACCS, SPOT, and SWFT." Also "STePP account and familiarity with CDSE." Also "Detailed knowledge of 32 CFR Part 117, CUI and OPSEC policies, and DCSA websites." Also "Current NCMS member." Also "Proficient experience with DISS/NBIS, ACCS, SPOT, and SWFT." Also "STePP account and familiarity with CDSE." Also "Detailed knowledge of 32 CFR Part 117, CUI and OPSEC policies, and DCSA websites." Also "Current NCMS member." Also "Proficient experience with DISS/NBIS, ACCS, SPOT, and SWFT." Also "STePP account and familiarity with CDSE." Also "Detailed knowledge of 32 CFR Part 117, CUI and OPSEC policies, and DCSA websites." Also "Current NCMS member." Also "