Lead Knowledge Information Manager
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not create sections with filler like "commensurate with experience". Pay and Benefits: we have pay range and benefits list. So we can have a Benefits section with pay and benefits.
Schedule: we have work schedule full-time, may be required to work additional hours, travel none, driving requirements. So schedule section.
We need to ensure we only include sections when posting has real specific content. All sections have content.
We must not include markdown fences.
Let's extract content.
Summary: "Design, develop, and sustain the AFSFC SharePoint environment, SMARTNet, and the public and private websites that serve Security Forces personnel and AFSFC Action Officers worldwide. Carry the AFSFC records and content lifecycle from creation through retention, disposition, and historical preservation. Build low-code automation and electronic forms inside the Government-furnished Microsoft 365 environment, run testing and quality control on every product before publication, and coordinate content with Air Force Installation and Mission Support Center (AFIMSC) Public Affairs, the Security Forces Museum, and the AFIMSC Historian. Develop the AFSFC artificial intelligence strategy for Center senior leadership, from opportunity identification through implementation roadmaps."
That's the summary paragraph.
Essential Duties & Responsibilities: list many bullet points. We'll convert each line starting with a verb into
- . Need to preserve all.
Let's list them:
- Design, develop, and sustain the AFSFC SharePoint environment, SMARTNet, and the public and private websites that serve Security Forces personnel and AFSFC Action Officers worldwide
- Perform daily onsite maintenance of AFSFC information repositories and communication channels, and publish Government-approved content to the appropriate channels within the contractual timeframe following approval
- Develop and publish a minimum of five new strategic and tactical communication products each quarter that align to AFSFC leadership's stated goals
- Manage the complete AFSFC information lifecycle, covering creation, collection, use, dissemination, maintenance, retention, disposition, and historical preservation, in compliance with governing Air Force and AFSFC records directives
- Coordinate content updates, revisions, and the preservation of historical information with AFSFC leadership, AFIMSC Public Affairs, the Security Forces Museum, and the AFIMSC Historian, retaining coordination evidence for every product
- Execute a comprehensive testing and quality control process across the content lifecycle, analyzing rejections and returning root causes to the pre-submission checklist
- Design graphical workflow maps, electronic forms with secure role-based routing, and forms linked to enterprise databases, and deploy automated processes within the Government-furnished Microsoft 365 environment
- Monitor, simulate, and test contractor-managed application behavior, and maintain the availability records required for Government reporting
- Create and install physical and digital media products required by the Director of Staff, and maintain change-control records for all software configuration, installation, and maintenance
- Develop and maintain the AFSFC artificial intelligence strategy, delivering an AI Strategy Plan within 90 days of tasking by AFSFC senior leadership that identifies at least three actionable opportunities, each supported by an implementation roadmap, cost-benefit analysis, risk assessment, timeline, and resource requirements
- Contribute workstream metrics, activity narrative, and deliverable schedule to the Monthly Status Report
- Serve as a fully qualified backup to the Enterprise Workflow Manager and the Administrative and Strategic Support Specialist, sustaining full performance thresholds on all critical tasks during any absence, and cross-train on all three contract functional areas on a scheduled basis
- Build and maintain the continuity library for this workstream, including standard operating procedures, portal design rules, content standards, and critical contact lists, throughout the period of performance
- Review all work products for Controlled Unclassified Information prior to dissemination, and safeguard all Government-furnished property and equipment issued for performance
- Complete and maintain all Government-required training, including Controlled Unclassified Information, cyber awareness, operations security, insider threat, annual security refresher, timekeeping, code of ethics, constructive communications, and ethical leadership
- Maintains regular and punctual attendance
- Performs other duties as assigned
Also "Supervisory Responsibilities None." Not needed as heading? Could be omitted as not substantive? Might be considered minor metadata; we can drop.
Requirements: Minimum Qualifications list:
- Bachelor's degree in Information Systems, Information Management, Computer Science, Communications, or a related field, or an equivalent combination of post-secondary education and directly related professional experience
- Minimum of three (3) years of experience working at Headquarters Air Force, a MAJCOM, or an equivalent staff agency
- Comprehensive knowledge and understanding of the relationships between Headquarters Air Force, MAJCOMs, AFIMSC, other DoD agencies, Government agencies, and AFSFC
- Demonstrated knowledge and ability to conduct complex analysis, studies, and other staff activities and to translate that work into senior leader and executive level briefs, summaries, and briefings
- Demonstrated hands-on administration and development experience with Microsoft SharePoint and Microsoft 365, including site structure, permissions, content types, and information architecture
- Demonstrated experience building solutions with the Microsoft Power Platform (Power Automate, Power Apps, Power Fx) and/or with HTML, JavaScript, and web or content management system administration
- Demonstrated experience managing a records and content lifecycle against Government records guidance, including retention and disposition
- Demonstrated experience performing content quality control and coordinating approvals through a public affairs or communications authority
- Active DoD Secret security clearance, or the demonstrated ability to obtain and maintain one (generally, U.S. citizenship required)
- Must obtain and maintain any necessary security access and/or background checks
Desired Qualifications & Skills list:
- Strong written and verbal communication skills, including the ability to work directly with senior leaders, Action Officers, and mission partners to translate a stated need into a delivered solution
- Willingness and demonstrated ability to cross-train on all three contract functional areas and to serve as a fully qualified backup to the other positions on the contract, with that coverage exercised on a scheduled basis
- Experience with the AFSFC SMARTNet environment or an equivalent enterprise Air Force portal
- Experience developing an artificial intelligence or automation strategy, roadmap, or business case for a Government customer
- Database administration, SQL, or application development background
- Section 508 and accessibility experience for public-facing content
- Experience coordinating with Public Affairs, museum, or historian functions on historical and brand-sensitive content
We can combine Minimum Qualifications and Desired Qualifications into a Requirements section with two sublists? But spec says use
- for any list of duties/requirements/benefits. Could have separate headings? Not required. Could just list all as one list. But better to separate maybe with headings? Not required but we could include subheadings? Not allowed to create extra headings unless they correspond to sections like Requirements. Could have a
Requirements
then inside we could have two maybe with preceding describing? But spec says use
- for any list. It doesn't forbid having multiple lists. We'll just put one list combining both minimum and desired, but we might lose distinction. However we can keep them as separate lists with a
intro. That's fine.
Benefits: Pay: $120,000 - $135,000 annually. Eligible Benefits: Medical, Dental, Vision, Life & AD&D Insurance, Long-Term & Short-Term Disability Insurance, 401(k) Savings Plan, Employee Assistance Program (EAP), Vacation & Paid Personal Time, 11 Paid Federal Holidays, and Leave of Absence.
We'll create a Benefits section with a
for pay and then a
for benefits.
Schedule: Work Schedule Full-time. May be required to work additional hours as needed to complete assignment or project. TRAVEL None. Driving Requirements Must have or be able to attain a valid state driver's license and be insurable on the company's automobile insurance policy. Driving, with or without accommodation, may be required when traveling for training and/or short occasional amounts of local driving. The expected driving time is less than 15%.
We'll create a Schedule section with a containing that info.
We must not include boilerplate: EEO, legal, application instructions, preference statements, etc. Also remove "Contractor personnel identify themselves..." etc. That's boilerplate? It's work environment details maybe considered substantive? It's about work environment; but we already have schedule and maybe we could include work environment? Not required to have a section. The instruction: include a section ONLY when posting has real, specific content for it. Work environment details are present but not a standard heading; we could incorporate into Schedule or maybe a separate section? Not among allowed headings list (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not create extra headings. We can fold work environment details into Schedule or maybe into Responsibilities? Probably better to fold into Schedule as it's about work schedule/environment. But schedule already includes work schedule; we can add a sentence about work environment. That's okay.
Also "PHYSICAL DEMANDS" etc. Could be folded into Schedule as well? Might be considered part of work schedule? Not exactly. But we could add to Schedule as additional details. However the instruction: Prefer a few substantive sections over many thin ones. So we can include all that extra info in Schedule section as a paragraph.
We must not include "The expected driving time is less than 15%." That's fine.
We must not include "It is Katmai's business philosophy..." that's boilerplate about accommodations; could be considered EEO? Might be considered boilerplate; we can drop.
We must not include "Preference will be given to Ouzinkie Shareholders..." that's EEO preference; drop.
Now craft HTML.
Structure:
About the role
Summary paragraph.
Responsibilities
- ...
...
Requirements
Minimum qualifications:
- ...
...
Desired qualifications and skills:
- ...
...
Benefits
Pay: $120,000 - $135,000 annually.
- Medical, Dental, Vision, Life & AD&D Insurance
- Long-Term & Short-Term Disability Insurance
- 401(k) Savings Plan
- Employee Assistance Program (EAP)
- Vacation & Paid Personal Time
- 11 Paid Federal Holidays
- Leave of Absence
Schedule
Full-time. May be required to work additional hours as needed to complete assignment or project. Travel none. Must have or be able to attain a valid state driver's license and be insurable on the company's automobile insurance policy. Driving, with or without accommodation, may be required when traveling for training and/or short occasional amounts of local driving (expected driving time less than 15%). Work environment: office on a military installation with sustained daily use of a Government-furnished workstation; occasional movement across a multi-floor facility to coordinate in person with Action Officers and AFSFC staff
for prose. We must not create sections with filler like "commensurate with experience". Pay and Benefits: we have pay range and benefits list. So we can have a Benefits section with pay and benefits. Schedule: we have work schedule full-time, may be required to work additional hours, travel none, driving requirements. So schedule section. We need to ensure we only include sections when posting has real specific content. All sections have content. We must not include markdown fences. Let's extract content. Summary: "Design, develop, and sustain the AFSFC SharePoint environment, SMARTNet, and the public and private websites that serve Security Forces personnel and AFSFC Action Officers worldwide. Carry the AFSFC records and content lifecycle from creation through retention, disposition, and historical preservation. Build low-code automation and electronic forms inside the Government-furnished Microsoft 365 environment, run testing and quality control on every product before publication, and coordinate content with Air Force Installation and Mission Support Center (AFIMSC) Public Affairs, the Security Forces Museum, and the AFIMSC Historian. Develop the AFSFC artificial intelligence strategy for Center senior leadership, from opportunity identification through implementation roadmaps." That's the summary paragraph. Essential Duties & Responsibilities: list many bullet points. We'll convert each line starting with a verb into
- for any list of duties/requirements/benefits. Could have separate headings? Not required. Could just list all as one list. But better to separate maybe with headings? Not required but we could include subheadings? Not allowed to create extra headings unless they correspond to sections like Requirements. Could have a
Requirements
then inside we could have two- maybe with preceding
- for any list. It doesn't forbid having multiple lists. We'll just put one list combining both minimum and desired, but we might lose distinction. However we can keep them as separate lists with a
intro. That's fine. Benefits: Pay: $120,000 - $135,000 annually. Eligible Benefits: Medical, Dental, Vision, Life & AD&D Insurance, Long-Term & Short-Term Disability Insurance, 401(k) Savings Plan, Employee Assistance Program (EAP), Vacation & Paid Personal Time, 11 Paid Federal Holidays, and Leave of Absence. We'll create a Benefits section with a
for pay and then a
- for benefits.
Schedule: Work Schedule Full-time. May be required to work additional hours as needed to complete assignment or project. TRAVEL None. Driving Requirements Must have or be able to attain a valid state driver's license and be insurable on the company's automobile insurance policy. Driving, with or without accommodation, may be required when traveling for training and/or short occasional amounts of local driving. The expected driving time is less than 15%.
We'll create a Schedule section with a
- ... ...
- ... ...
- ... ...
- Medical, Dental, Vision, Life & AD&D Insurance
- Long-Term & Short-Term Disability Insurance
- 401(k) Savings Plan
- Employee Assistance Program (EAP)
- Vacation & Paid Personal Time
- 11 Paid Federal Holidays
- Leave of Absence
containing that info. We must not include boilerplate: EEO, legal, application instructions, preference statements, etc. Also remove "Contractor personnel identify themselves..." etc. That's boilerplate? It's work environment details maybe considered substantive? It's about work environment; but we already have schedule and maybe we could include work environment? Not required to have a section. The instruction: include a section ONLY when posting has real, specific content for it. Work environment details are present but not a standard heading; we could incorporate into Schedule or maybe a separate section? Not among allowed headings list (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not create extra headings. We can fold work environment details into Schedule or maybe into Responsibilities? Probably better to fold into Schedule as it's about work schedule/environment. But schedule already includes work schedule; we can add a sentence about work environment. That's okay. Also "PHYSICAL DEMANDS" etc. Could be folded into Schedule as well? Might be considered part of work schedule? Not exactly. But we could add to Schedule as additional details. However the instruction: Prefer a few substantive sections over many thin ones. So we can include all that extra info in Schedule section as a paragraph. We must not include "The expected driving time is less than 15%." That's fine. We must not include "It is Katmai's business philosophy..." that's boilerplate about accommodations; could be considered EEO? Might be considered boilerplate; we can drop. We must not include "Preference will be given to Ouzinkie Shareholders..." that's EEO preference; drop. Now craft HTML. Structure:
About the role
Summary paragraph.
Responsibilities
Requirements
Minimum qualifications:
Desired qualifications and skills:
Benefits
Pay: $120,000 - $135,000 annually.
Schedule
Full-time. May be required to work additional hours as needed to complete assignment or project. Travel none. Must have or be able to attain a valid state driver's license and be insurable on the company's automobile insurance policy. Driving, with or without accommodation, may be required when traveling for training and/or short occasional amounts of local driving (expected driving time less than 15%). Work environment: office on a military installation with sustained daily use of a Government-furnished workstation; occasional movement across a multi-floor facility to coordinate in person with Action Officers and AFSFC staff
describing? But spec says use
- for any list. It doesn't forbid having multiple lists. We'll just put one list combining both minimum and desired, but we might lose distinction. However we can keep them as separate lists with a