Acquisition Program Management Support Specialist
Cherokee Federal · Colorado Springs, CO · 3 wk ago
On-siteAdministrative$108k–$110k/yrFull-time
We need to output HTML fragment with sections: only those with real content. The posting includes:
- Position Summary (maybe "About the role"? The instruction says use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings.
We have:
- Position Summary: "Cherokee Strategic Edge is seeking a qualified Acquisition Program Management Support Specialist to provide Acquisition Program Management support to Space Operations Command." That's about the role. So we can put under
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings.
We have:
- Position Summary: "Cherokee Strategic Edge is seeking a qualified Acquisition Program Management Support Specialist to provide Acquisition Program Management support to Space Operations Command." That's about the role. So we can put under About the role
with that paragraph.
- Compensation & Benefits: includes Starting Salary Range and Benefits list. So we need Pay section (salary) and Benefits section. The instruction: include Pay/Schedule/Benefits sections only if posting actually states them. Yes, salary range given, benefits listed. So we create Pay
with paragraph containing salary range. And Benefits
with - list of benefits.
- Essential Functions, Duties & Responsibilities: that's Responsibilities. So
Responsibilities
with - list of duties. The list is long; we need to preserve all substantive information. We'll need to extract each bullet from the text. The text includes many sentences separated by semicolons and periods. We need to convert each duty into a list item. We must not invent or summarize away detail. We'll need to break down the paragraph into distinct duties.
Let's parse the "Essential Functions, Duties & Responsibilities: Includes The Following" paragraph.
It starts: "Provide project management expertise for acquisitions strategies and management of portfolios."
Then: "Research, evaluate, and provide technical reviews on technologies, data, programs, efforts, and capabilities; provide recommendations, reports, resolutions, advice, and assistance to improve Space ISR mission effectiveness and future acquisitions efforts."
Then: "Support SpOC Requirements and Configuration Control forums."
Then: "Draft acquisition support required documentation."
Then: "Draft, analyze, review, advise, and assist with test and evaluation program planning; provide installation, testing, and execution scheduling and timeline documentation of platforms and weapons systems and participate in tests and trials; perform coordination with site leads, development contractors, and Government program managers."
Then: "Develop COA analysis, including sourcing research, quality analysis, sustainability research, pairwise analysis of competing technologies, and Strengths-Weaknesses-Opportunities-Threats (SWOT) analysis."
Then: "Coordinate, manage, advise, and assist with intelligence requirements and tasking requirements for acquisitions organizations leading to intelligence planning, collection, processing, analysis, and dissemination activities."
Then: "Analyze technical evaluation reports and provide advice and assistance with determining key performance parameters, track and resolve milestone conflicts in line with joint capabilities integration and systems development."
Then: "Document processes, operating instructions, and standard operating procedures for inclusion into future operations and program efforts."
Then: "Develop detailed analysis and strategies supporting technologies, techniques, and/or tactics for intelligence systems, to include ongoing advanced cryptologic initiatives, and counter communications system(s) requirements."
Then: "Advise and assist with planning, organizing, and managing critical aspects of the development, production, and/or deployment of capabilities, including coordination and de-confliction with development contractors, Government site leads, and SpOC/S2 acquisition program managers and financial managers."
Then: "Participate in and provide advice and assistance with Working Groups (WGs), TEMs and PMRs, create meeting invitations and agendas, document presentations for decision-making forums, take meeting minutes and disseminate to forum participants, and follow-up on action items as directed."
Then: "Collaborate with systems engineers and intelligence requirements managers to identify intelligence needs and gaps."
Then: "Draft, analyze, and submit reports summarizing conclusions, advice, and recommendations for meeting space intelligence needs and gaps in support of stakeholder requirement generation, allocation, verification, and validation."
Then: "Develop acquisitions strategies and manage portfolios supporting SpOC/S2 and DEL 7 mission systems and provide acquisition life cycle support."
Then: "Track, advise, and assist supported organizations with creation and maintenance of the organization’s intelligence lifecycle program management processes consistent with government approved priorities, vision, and requirements."
Then: "Devise and execute Government-approved strategies for acquisition of intelligence collection capabilities and advise the Government on the movement and/or placement of collection assets to improve collection efforts."
Then: "Develop, update, sustain, and provide advice, assistance, and support toward Intelligence Architecture Plans (IAP), Information Support Plans (ISP), technical reports, and modernization efforts of the ISR operations integration."
Then: "Analyze and determine associated ISR capability requirements, gaps and shortfalls and recommend new or modified ISR system capabilities."
Then: "Create, plan, and maintain master schedules supporting all intelligence support to systems and intelligence systems acquisition efforts for the Space ISR enterprise."
Then: "Performs other job-related duties as assigned" repeated twice.
We need to list each as
- . Ensure we keep the exact phrasing? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the sentences as they appear, maybe as list items. We can keep the semicolons inside list items; that's fine.
Now Education, Experience, Knowledge, Skills and Abilities Required: (Basic Qualifications) and Preferred Qualifications. That's Requirements/Qualifications/Skills. We need to decide which heading(s) to use. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for Requirements (basic qualifications) and Preferred Qualifications (maybe also under Requirements or Qualifications). We could combine into a single
Requirements
with - for each bullet. Or we could split into Requirements and Preferred Qualifications but the instruction says prefer a few substantive sections over many thin ones. So we can combine basic and preferred into one Requirements section.
Let's extract the basic qualifications bullet points:
- In-depth knowledge and understanding of the activities required to meet mission requirements.
- Ability to work independently with minimal oversight.
- Ability to communicate understanding from information that may be incomplete, indirect, highly complex, seemingly unrelated, and / or technically advanced.
- Demonstrates ability to collaborate and work with other IC members on information sharing, driving collection, and addressing analytic disputes and conflict resolution.
- Ability to develop concise, insightful, and comprehensive products for defense intelligence.
- Must be a US Citizen.
- This position requires an active Top Secret/SCI clearance.
- Prolonged periods of sitting at a desk and working on a computer; may occasionally require standing or moving about the office for extended periods.
- Must pass pre-employment qualifications of Cherokee Federal.
Preferred Qualifications:
- Desired to have a minimum of twelve (12) years of experience performing duties and responsibilities related to the position’s responsibilities.
- Experience supporting Space Operations Command is highly desired.
We'll list them as list items.
Now we also have Company Information etc. That's boilerplate; we should remove per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company info is likely boilerplate; we should drop it. Also the legal disclaimer, EEO statement, etc. Remove.
Also we have "Work Environment" section: "Work is performed primarily in a climate-controlled environment." That's maybe not a standard heading; could be part of Responsibilities or Requirements? It's a detail about work environment. The instruction says include a section only when posting has real, specific content for it. There's no standard heading for Work Environment; we could incorporate into Responsibilities or Requirements? But it's not a duty. Could be part of Requirements? Might be considered a qualification? Probably better to include under Requirements as a bullet? But it's not a qualification; it's work condition. The instruction says we can create sections only for the predefined headings. There's no Work Environment heading. So we should either drop it or incorporate into Responsibilities? It's not a duty. Might be considered part of the job description but not a duty. The instruction says remove boilerplate; this is not boilerplate but a specific statement. However we have no heading for it. Could we create a custom heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should use those headings. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings only. So we should not create a Work Environment heading. We could incorporate that sentence into Responsibilities as a duty? It's not a duty but maybe we can add as a list item under Responsibilities? Might be okay but could be considered adding detail not originally a duty. However the instruction says preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. Perhaps we can put it under Requirements as a bullet about work environment? Or under About the role? The safest is to add a list item under Responsibilities: "Work is performed primarily in a climate-controlled environment." It's still substantive info about the job. It's not a duty but it's a condition; but we can treat it as a responsibility? Might be acceptable.
Alternatively we could create a Skills
section and put that there? Not appropriate.
Given the instruction to prefer few substantive sections, we can add it as a bullet under Responsibilities.
Now also we have "Supervisory Responsibilities No supervisory/management authority". That's a statement about supervisory responsibilities. Could be part of Responsibilities? Might be a separate bullet: "No supervisory/management authority." We'll include as a bullet under Responsibilities.
Now also we have "Position Summary" we already used.
Now we need to ensure we don't repeat the job title as a heading. Already not.
Now we need to output only HTML fragment, no /, no markdown.
Let's construct:
About the role
Cherokee Strategic Edge is seeking a qualified Acquisition Program Management Support Specialist to provide Acquisition Program Management support to Space Operations Command.
Responsibilities
- Provide project management expertise for acquisitions strategies and management of portfolios.
- Research, evaluate, and provide technical reviews on technologies, data, programs, efforts, and capabilities; provide recommendations, reports, resolutions, advice, and assistance to improve Space ISR mission effectiveness and future acquisitions efforts.
- Support SpOC Requirements and Configuration Control forums.
- Draft acquisition support required documentation.
- Draft, analyze, review, advise, and assist with test and evaluation program planning; provide installation, testing, and execution scheduling and timeline documentation of platforms and weapons systems and participate in tests and trials; perform coordination with site leads, development contractors, and Government program managers.
- Develop COA analysis, including sourcing research, quality analysis, sustainability research, pairwise analysis of competing technologies, and Strengths-Weaknesses-Opportunities-Threats (SWOT) analysis.
- Coordinate, manage, advise, and assist with intelligence requirements and tasking requirements for acquisitions organizations leading to intelligence planning, collection, processing, analysis, and dissemination activities.
- Analyze technical evaluation reports and provide advice and assistance with determining key performance parameters, track and resolve milestone conflicts in line with joint capabilities integration and systems development.
- Document processes, operating instructions, and standard operating procedures for inclusion into future operations and program efforts.
- Develop detailed analysis and strategies supporting technologies, techniques, and/or tactics for intelligence systems, to include ongoing advanced cryptologic initiatives, and counter communications system(s) requirements.
- Advise and assist with planning, organizing, and managing critical aspects of the development, production, and/or deployment of capabilities, including coordination and de-confliction with development contractors, Government site leads, and SpOC
Responsibilities
with- list of duties. The list is long; we need to preserve all substantive information. We'll need to extract each bullet from the text. The text includes many sentences separated by semicolons and periods. We need to convert each duty into a list item. We must not invent or summarize away detail. We'll need to break down the paragraph into distinct duties. Let's parse the "Essential Functions, Duties & Responsibilities: Includes The Following" paragraph. It starts: "Provide project management expertise for acquisitions strategies and management of portfolios." Then: "Research, evaluate, and provide technical reviews on technologies, data, programs, efforts, and capabilities; provide recommendations, reports, resolutions, advice, and assistance to improve Space ISR mission effectiveness and future acquisitions efforts." Then: "Support SpOC Requirements and Configuration Control forums." Then: "Draft acquisition support required documentation." Then: "Draft, analyze, review, advise, and assist with test and evaluation program planning; provide installation, testing, and execution scheduling and timeline documentation of platforms and weapons systems and participate in tests and trials; perform coordination with site leads, development contractors, and Government program managers." Then: "Develop COA analysis, including sourcing research, quality analysis, sustainability research, pairwise analysis of competing technologies, and Strengths-Weaknesses-Opportunities-Threats (SWOT) analysis." Then: "Coordinate, manage, advise, and assist with intelligence requirements and tasking requirements for acquisitions organizations leading to intelligence planning, collection, processing, analysis, and dissemination activities." Then: "Analyze technical evaluation reports and provide advice and assistance with determining key performance parameters, track and resolve milestone conflicts in line with joint capabilities integration and systems development." Then: "Document processes, operating instructions, and standard operating procedures for inclusion into future operations and program efforts." Then: "Develop detailed analysis and strategies supporting technologies, techniques, and/or tactics for intelligence systems, to include ongoing advanced cryptologic initiatives, and counter communications system(s) requirements." Then: "Advise and assist with planning, organizing, and managing critical aspects of the development, production, and/or deployment of capabilities, including coordination and de-confliction with development contractors, Government site leads, and SpOC/S2 acquisition program managers and financial managers." Then: "Participate in and provide advice and assistance with Working Groups (WGs), TEMs and PMRs, create meeting invitations and agendas, document presentations for decision-making forums, take meeting minutes and disseminate to forum participants, and follow-up on action items as directed." Then: "Collaborate with systems engineers and intelligence requirements managers to identify intelligence needs and gaps." Then: "Draft, analyze, and submit reports summarizing conclusions, advice, and recommendations for meeting space intelligence needs and gaps in support of stakeholder requirement generation, allocation, verification, and validation." Then: "Develop acquisitions strategies and manage portfolios supporting SpOC/S2 and DEL 7 mission systems and provide acquisition life cycle support." Then: "Track, advise, and assist supported organizations with creation and maintenance of the organization’s intelligence lifecycle program management processes consistent with government approved priorities, vision, and requirements." Then: "Devise and execute Government-approved strategies for acquisition of intelligence collection capabilities and advise the Government on the movement and/or placement of collection assets to improve collection efforts." Then: "Develop, update, sustain, and provide advice, assistance, and support toward Intelligence Architecture Plans (IAP), Information Support Plans (ISP), technical reports, and modernization efforts of the ISR operations integration." Then: "Analyze and determine associated ISR capability requirements, gaps and shortfalls and recommend new or modified ISR system capabilities." Then: "Create, plan, and maintain master schedules supporting all intelligence support to systems and intelligence systems acquisition efforts for the Space ISR enterprise." Then: "Performs other job-related duties as assigned" repeated twice. We need to list each as
- . Ensure we keep the exact phrasing? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the sentences as they appear, maybe as list items. We can keep the semicolons inside list items; that's fine.
Now Education, Experience, Knowledge, Skills and Abilities Required: (Basic Qualifications) and Preferred Qualifications. That's Requirements/Qualifications/Skills. We need to decide which heading(s) to use. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for Requirements (basic qualifications) and Preferred Qualifications (maybe also under Requirements or Qualifications). We could combine into a single
Requirements
with- for each bullet. Or we could split into Requirements and Preferred Qualifications but the instruction says prefer a few substantive sections over many thin ones. So we can combine basic and preferred into one Requirements section.
Let's extract the basic qualifications bullet points:
- In-depth knowledge and understanding of the activities required to meet mission requirements.
- Ability to work independently with minimal oversight.
- Ability to communicate understanding from information that may be incomplete, indirect, highly complex, seemingly unrelated, and / or technically advanced.
- Demonstrates ability to collaborate and work with other IC members on information sharing, driving collection, and addressing analytic disputes and conflict resolution.
- Ability to develop concise, insightful, and comprehensive products for defense intelligence.
- Must be a US Citizen.
- This position requires an active Top Secret/SCI clearance.
- Prolonged periods of sitting at a desk and working on a computer; may occasionally require standing or moving about the office for extended periods.
- Must pass pre-employment qualifications of Cherokee Federal.
Preferred Qualifications:
- Desired to have a minimum of twelve (12) years of experience performing duties and responsibilities related to the position’s responsibilities.
- Experience supporting Space Operations Command is highly desired.
We'll list them as list items.
Now we also have Company Information etc. That's boilerplate; we should remove per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company info is likely boilerplate; we should drop it. Also the legal disclaimer, EEO statement, etc. Remove.
Also we have "Work Environment" section: "Work is performed primarily in a climate-controlled environment." That's maybe not a standard heading; could be part of Responsibilities or Requirements? It's a detail about work environment. The instruction says include a section only when posting has real, specific content for it. There's no standard heading for Work Environment; we could incorporate into Responsibilities or Requirements? But it's not a duty. Could be part of Requirements? Might be considered a qualification? Probably better to include under Requirements as a bullet? But it's not a qualification; it's work condition. The instruction says we can create sections only for the predefined headings. There's no Work Environment heading. So we should either drop it or incorporate into Responsibilities? It's not a duty. Might be considered part of the job description but not a duty. The instruction says remove boilerplate; this is not boilerplate but a specific statement. However we have no heading for it. Could we create a custom heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should use those headings. It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings only. So we should not create a Work Environment heading. We could incorporate that sentence into Responsibilities as a duty? It's not a duty but maybe we can add as a list item under Responsibilities? Might be okay but could be considered adding detail not originally a duty. However the instruction says preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. Perhaps we can put it under Requirements as a bullet about work environment? Or under About the role? The safest is to add a list item under Responsibilities: "Work is performed primarily in a climate-controlled environment." It's still substantive info about the job. It's not a duty but it's a condition; but we can treat it as a responsibility? Might be acceptable. Alternatively we could create a
Skills
section and put that there? Not appropriate. Given the instruction to prefer few substantive sections, we can add it as a bullet under Responsibilities. Now also we have "Supervisory Responsibilities No supervisory/management authority". That's a statement about supervisory responsibilities. Could be part of Responsibilities? Might be a separate bullet: "No supervisory/management authority." We'll include as a bullet under Responsibilities. Now also we have "Position Summary" we already used. Now we need to ensure we don't repeat the job title as a heading. Already not. Now we need to output only HTML fragment, no /, no markdown. Let's construct:About the role
Cherokee Strategic Edge is seeking a qualified Acquisition Program Management Support Specialist to provide Acquisition Program Management support to Space Operations Command.
Responsibilities
- Provide project management expertise for acquisitions strategies and management of portfolios.
- Research, evaluate, and provide technical reviews on technologies, data, programs, efforts, and capabilities; provide recommendations, reports, resolutions, advice, and assistance to improve Space ISR mission effectiveness and future acquisitions efforts.
- Support SpOC Requirements and Configuration Control forums.
- Draft acquisition support required documentation.
- Draft, analyze, review, advise, and assist with test and evaluation program planning; provide installation, testing, and execution scheduling and timeline documentation of platforms and weapons systems and participate in tests and trials; perform coordination with site leads, development contractors, and Government program managers.
- Develop COA analysis, including sourcing research, quality analysis, sustainability research, pairwise analysis of competing technologies, and Strengths-Weaknesses-Opportunities-Threats (SWOT) analysis.
- Coordinate, manage, advise, and assist with intelligence requirements and tasking requirements for acquisitions organizations leading to intelligence planning, collection, processing, analysis, and dissemination activities.
- Analyze technical evaluation reports and provide advice and assistance with determining key performance parameters, track and resolve milestone conflicts in line with joint capabilities integration and systems development.
- Document processes, operating instructions, and standard operating procedures for inclusion into future operations and program efforts.
- Develop detailed analysis and strategies supporting technologies, techniques, and/or tactics for intelligence systems, to include ongoing advanced cryptologic initiatives, and counter communications system(s) requirements.
- Advise and assist with planning, organizing, and managing critical aspects of the development, production, and/or deployment of capabilities, including coordination and de-confliction with development contractors, Government site leads, and SpOC
- for each bullet. Or we could split into Requirements and Preferred Qualifications but the instruction says prefer a few substantive sections over many thin ones. So we can combine basic and preferred into one Requirements section.
Let's extract the basic qualifications bullet points:
- In-depth knowledge and understanding of the activities required to meet mission requirements.
- Ability to work independently with minimal oversight.
- Ability to communicate understanding from information that may be incomplete, indirect, highly complex, seemingly unrelated, and / or technically advanced.
- Demonstrates ability to collaborate and work with other IC members on information sharing, driving collection, and addressing analytic disputes and conflict resolution.
- Ability to develop concise, insightful, and comprehensive products for defense intelligence.
- Must be a US Citizen.
- This position requires an active Top Secret/SCI clearance.
- Prolonged periods of sitting at a desk and working on a computer; may occasionally require standing or moving about the office for extended periods.
- Must pass pre-employment qualifications of Cherokee Federal.
Preferred Qualifications:
- Desired to have a minimum of twelve (12) years of experience performing duties and responsibilities related to the position’s responsibilities.
- Experience supporting Space Operations Command is highly desired.
We'll list them as list items.
Now we also have Company Information etc. That's boilerplate; we should remove per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company info is likely boilerplate; we should drop it. Also the legal disclaimer, EEO statement, etc. Remove.
Also we have "Work Environment" section: "Work is performed primarily in a climate-controlled environment." That's maybe not a standard heading; could be part of Responsibilities or Requirements? It's a detail about work environment. The instruction says include a section only when posting has real, specific content for it. There's no standard heading for Work Environment; we could incorporate into Responsibilities or Requirements? But it's not a duty. Could be part of Requirements? Might be considered a qualification? Probably better to include under Requirements as a bullet? But it's not a qualification; it's work condition. The instruction says we can create sections only for the predefined headings. There's no Work Environment heading. So we should either drop it or incorporate into Responsibilities? It's not a duty. Might be considered part of the job description but not a duty. The instruction says remove boilerplate; this is not boilerplate but a specific statement. However we have no heading for it. Could we create a custom heading? The instruction says use