Procurement Analyst, SSC/PK.
for sections present: About the role? Not present. Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real specific content.
From posting: Duties (list of duties). That's responsibilities. Also "Ideal Candidate" maybe skills/qualifications. There's "Requirements" section with conditions of employment. There's "Qualifications" section with detailed qualification standards. There's "Additional information" includes benefits mention but vague. There's no explicit Pay or Schedule specifics (though mentions remote/hybrid, telework 2-4 days a pay period, actual pay based on locality). That's schedule info (remote/hybrid) and pay (actual pay based on locality). We can include Schedule section with remote/hybrid detail. Pay section: "Actual pay will be based on locality." That's specific enough? It says actual pay will be based on locality. That's a statement about pay determination. We can include Pay section with that sentence. Benefits: there is a paragraph about benefits package but vague. It says "A career with the U.S. government provides employees with a comprehensive benefits package... Contact the hiring agency for more information on the specific benefits offered." That's not specific. According to rules, we should not create Benefits section unless posting actually states them. It mentions benefits but not specific. Likely we should not include Benefits because it's generic. However we could include a short sentence? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist but not specifics. Might be considered stating them (they say comprehensive benefits package). But they also say contact agency for specifics. I'd lean to include Benefits section with that generic statement? The rule says prefer few substantive sections over many thin ones. The benefits statement is thin. Better to omit Benefits.
Skills: maybe from Ideal Candidate list. Could be Skills section.
We need to use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. No Job ID.
We need to preserve all substantive information. So we need to capture duties list, responsibilities list (maybe same as duties). The posting has "Duties" then description paragraph, then "Position Responsibilities" list. Also "Ideal Candidate" list (skills/qualifications). Then "Requirements" list (conditions of employment). Then "Qualifications" long text (maybe we keep as prose). Also "Additional information" includes benefits paragraph and other notes (like reemployed annuitants, veteran preference, etc). Might be considered boilerplate? It's not cookie/navigation/legal/EEO etc. It's additional info about veterans, annuitants, etc. Might be considered relevant. But we need to decide.
We should include sections: Responsibilities (duties), Requirements (conditions of employment), Qualifications (the qualification standards), Skills (ideal candidate). Possibly Schedule (remote/hybrid). Pay (actual pay based on locality). We'll include those.
Now extract content.
Duties paragraph: "The United States Space Force (USSF) at Los Angeles Space Force Base is searching for a Procurement Analyst for SSC/PK (NH-1102-04, GS-14/15 Equivalent). Description Procurement Analyst in the Policy or Program Support branch of SSC/PKV, serving as a senior contracting and business advisor on complex, high-visibility acquisition actions. SSC/PKV provides acquisition and contracting subject matter expertise to the Space Service Acquisition Executive (SAF/SQ), HCA, SCO, Field Command Leadership, Portfolio Acquisition Executives, and the SSC contracting workforce. The position supports enterprise-level decision-making through acquisition strategy review, risk-based reviews, policy and process development, staff coordination, and cross-functional problem solving. Selected candidates may be assigned to either the Policy or Program Support branch based on organizational needs and applicant experience."
That's prose.
Then "Position Responsibilities" list:
- Review complex, high-value procurement actions and provide recommendations to improve acquisition strategy, documentation quality, and regulatory compliance.
- Advise Chiefs of the Contracting Office and acquisition teams on difficult business and contracting issues affecting priority programs.
- Serve as a senior staff resource in policy, program support, or business operations matters requiring sound judgment and enterprise perspective.
- Develop and refine HCA- and SCO-level processes, procedures, tools, and guidance to improve acquisition effectiveness.
- Build productive working relationships with contracting officers, specialists, program offices, legal counsel, pricing, and senior leaders.
- Represent SSC/PKV in internal and external meetings across SSC, USSF, and the Department of the Air Force.
- Respond to action items, audits, Congressional inquiries, data calls, and other senior-leader taskings.
- Support leadership initiatives to improve acquisition speed, quality, consistency, and mission outcomes.
That's a list.
"Ideal Candidate" list:
- Appropriate Acquisition Professional Development Program (APDP) Level certification
- Unlimited contracting officer warrant (current or inactive)
- Advanced degree in a business-related field (e.g., MBA, JD)
- Experience as a contracting and/or agreements officer in complex competitive and sole source acquisitions, contract administration, or other transactions
- Deep understanding and subject matter expertise in systems contracting, especially for the space portfolio
- Forward-thinking, solution-oriented team player with strong research, analytical, and problem-solving skills
- Experience working with and interfacing with senior leaders
- Ability to communicate clearly and effectively both orally and in writing
- Experience working effectively under pressure and in a dynamic environment
That's skills/qualifications.
"Requirements Conditions of employment" list (actually paragraph with bullet-like sentences). Let's extract each condition:
- Must be a U.S Citizen.
- PCS/Relocation funding is available.
- Employee must be able to obtain and maintain a Top-Secret Clearance
- Required to handle and safeguard sensitive and classified information in accordance with regulations to reduce potential compromise.
- May be required travel away from the normal duty station on military or commercial aircraft.
- May be required to work overtime on an unscheduled or emergency basis.
- This position is eligible for remote or hybrid. If hybrid, telework 2-4 days a pay period. Actual pay will be based on locality.
- Position will close after 5 business days or 75 applications.
- Subject to Temporary Duty Assignment (TDY) assignments.
- Employee must within 30-days of assuming this position and by 31 October annually thereafter, file an OGE-450.
- This position may require a Contracting Officer's warrant.
- The employee must meet the Defense Acquisition Workforce Improvement Act (DAWIA) requirements applicable to the duties of the position.
- The employee must meet the continuing acquisition education requirements IAW DoDI 5000.66 paragraph E2.2.8.
- This position requires drug testing.
- Alternative work arrangements, including establishing an alternate work location, may be considered for this position at the time of selection in accordance with mission requirements and agency policy.
We need to separate schedule and pay info: remote/hybrid and telework 2-4 days a pay period; actual pay based on locality. We'll put those in Schedule and Pay sections.
Now Qualifications section: large block about DOD QUALIFICATION STANDARD etc. We'll keep as prose (maybe multiple paragraphs). We'll keep as
with the text.
Additional information: includes Employed Annuitants, veteran preference, etc. Might be considered additional info but not boilerplate. Could include as a section "Additional Information". But heading must be from allowed list? The rules only list specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add other headings. So we must either incorporate that info into existing sections or drop it. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we should use those headings only. So we should map content to those headings. Additional info like veteran preference could go under Qualifications? Not really. Could be omitted? Might be considered boilerplate? It's not cookie/navigation/legal/EEO but it's still informational. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This additional info is not those categories. But we have no heading for it. Could we incorporate into Qualifications as a note? Might be okay to drop if not fitting. However we risk losing substantive info. But maybe it's considered "Additional information" not required to keep. The instruction says preserve ALL substantive information. So we need to keep it somewhere. Since we cannot add new headings, we could put it under Qualifications as a paragraph after the qualification standard. Or under Responsibilities? Not appropriate. Probably best to add a
under Qualifications after the standard text.
Thus Qualifications section will contain the DOD qualification standard text plus the additional information paragraph(s). We'll keep as one
maybe with line breaks.
Now Skills section: we can use the Ideal Candidate list as skills.
Now Schedule section: remote/hybrid, telework 2-4 days a pay period.
Pay section: actual pay based on locality.
Now Responsibilities section: we have the Position Responsibilities list.
Also we have the initial duties paragraph (description). Could be included in Responsibilities as prose before list, or as a separate About the role? There's no About the role heading but we could treat the description as part of Responsibilities. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we could have an About the role section for the introductory description. That seems appropriate. Let's create About the role with the introductory paragraph (the first paragraph). Then Responsibilities with the list.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule.
Now we need to output HTML fragment only.
Let's craft.
About the role:
... the paragraph ...
Responsibilities: Responsibilities
- ... each item ...
Requirements: Requirements
- ... each condition ...
but we need to separate schedule/pay items out. So we will exclude remote/hybrid and actual pay from Requirements list; they go to Schedule and Pay.
Thus Requirements list items: all except those two.
Let's list them:
- Must be a U.S Citizen.
- PCS/Relocation funding is available.
- Employee must be able to obtain and maintain a Top-Secret Clearance
- Required to handle and safeguard sensitive and classified information in accordance with regulations to reduce potential compromise.
- May be required travel away from the normal duty station on military or commercial aircraft.
- May be required to work overtime on an unscheduled or emergency basis.
- Position will close after 5 business days or 75 applications.
- Subject to Temporary Duty Assignment (TDY) assignments.
- Employee must within 30-days of assuming this position and by 31 October annually thereafter, file an OGE-450.
- This position may require a Contracting Officer's warrant.
- The employee must meet the Defense Acquisition Workforce Improvement Act (DAWIA) requirements applicable to the duties of the position.
- The employee must meet the continuing acquisition education requirements IAW DoDI 5000.66 paragraph E2.2.8.
- This position requires drug testing.
- Alternative work arrangements, including establishing an alternate work location, may be considered for this position at the time of selection in accordance with mission requirements and agency policy.
Now Schedule: remote/hybrid, telework 2-4 days
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat job title as heading. No Job ID. We need to preserve all substantive information. So we need to capture duties list, responsibilities list (maybe same as duties). The posting has "Duties" then description paragraph, then "Position Responsibilities" list. Also "Ideal Candidate" list (skills/qualifications). Then "Requirements" list (conditions of employment). Then "Qualifications" long text (maybe we keep as prose). Also "Additional information" includes benefits paragraph and other notes (like reemployed annuitants, veteran preference, etc). Might be considered boilerplate? It's not cookie/navigation/legal/EEO etc. It's additional info about veterans, annuitants, etc. Might be considered relevant. But we need to decide. We should include sections: Responsibilities (duties), Requirements (conditions of employment), Qualifications (the qualification standards), Skills (ideal candidate). Possibly Schedule (remote/hybrid). Pay (actual pay based on locality). We'll include those. Now extract content. Duties paragraph: "The United States Space Force (USSF) at Los Angeles Space Force Base is searching for a Procurement Analyst for SSC/PK (NH-1102-04, GS-14/15 Equivalent). Description Procurement Analyst in the Policy or Program Support branch of SSC/PKV, serving as a senior contracting and business advisor on complex, high-visibility acquisition actions. SSC/PKV provides acquisition and contracting subject matter expertise to the Space Service Acquisition Executive (SAF/SQ), HCA, SCO, Field Command Leadership, Portfolio Acquisition Executives, and the SSC contracting workforce. The position supports enterprise-level decision-making through acquisition strategy review, risk-based reviews, policy and process development, staff coordination, and cross-functional problem solving. Selected candidates may be assigned to either the Policy or Program Support branch based on organizational needs and applicant experience." That's prose. Then "Position Responsibilities" list: - Review complex, high-value procurement actions and provide recommendations to improve acquisition strategy, documentation quality, and regulatory compliance. - Advise Chiefs of the Contracting Office and acquisition teams on difficult business and contracting issues affecting priority programs. - Serve as a senior staff resource in policy, program support, or business operations matters requiring sound judgment and enterprise perspective. - Develop and refine HCA- and SCO-level processes, procedures, tools, and guidance to improve acquisition effectiveness. - Build productive working relationships with contracting officers, specialists, program offices, legal counsel, pricing, and senior leaders. - Represent SSC/PKV in internal and external meetings across SSC, USSF, and the Department of the Air Force. - Respond to action items, audits, Congressional inquiries, data calls, and other senior-leader taskings. - Support leadership initiatives to improve acquisition speed, quality, consistency, and mission outcomes. That's a list. "Ideal Candidate" list: - Appropriate Acquisition Professional Development Program (APDP) Level certification - Unlimited contracting officer warrant (current or inactive) - Advanced degree in a business-related field (e.g., MBA, JD) - Experience as a contracting and/or agreements officer in complex competitive and sole source acquisitions, contract administration, or other transactions - Deep understanding and subject matter expertise in systems contracting, especially for the space portfolio - Forward-thinking, solution-oriented team player with strong research, analytical, and problem-solving skills - Experience working with and interfacing with senior leaders - Ability to communicate clearly and effectively both orally and in writing - Experience working effectively under pressure and in a dynamic environment That's skills/qualifications. "Requirements Conditions of employment" list (actually paragraph with bullet-like sentences). Let's extract each condition: - Must be a U.S Citizen. - PCS/Relocation funding is available. - Employee must be able to obtain and maintain a Top-Secret Clearance - Required to handle and safeguard sensitive and classified information in accordance with regulations to reduce potential compromise. - May be required travel away from the normal duty station on military or commercial aircraft. - May be required to work overtime on an unscheduled or emergency basis. - This position is eligible for remote or hybrid. If hybrid, telework 2-4 days a pay period. Actual pay will be based on locality. - Position will close after 5 business days or 75 applications. - Subject to Temporary Duty Assignment (TDY) assignments. - Employee must within 30-days of assuming this position and by 31 October annually thereafter, file an OGE-450. - This position may require a Contracting Officer's warrant. - The employee must meet the Defense Acquisition Workforce Improvement Act (DAWIA) requirements applicable to the duties of the position. - The employee must meet the continuing acquisition education requirements IAW DoDI 5000.66 paragraph E2.2.8. - This position requires drug testing. - Alternative work arrangements, including establishing an alternate work location, may be considered for this position at the time of selection in accordance with mission requirements and agency policy. We need to separate schedule and pay info: remote/hybrid and telework 2-4 days a pay period; actual pay based on locality. We'll put those in Schedule and Pay sections. Now Qualifications section: large block about DOD QUALIFICATION STANDARD etc. We'll keep as prose (maybe multiple paragraphs). We'll keep as
with the text. Additional information: includes Employed Annuitants, veteran preference, etc. Might be considered additional info but not boilerplate. Could include as a section "Additional Information". But heading must be from allowed list? The rules only list specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add other headings. So we must either incorporate that info into existing sections or drop it. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we should use those headings only. So we should map content to those headings. Additional info like veteran preference could go under Qualifications? Not really. Could be omitted? Might be considered boilerplate? It's not cookie/navigation/legal/EEO but it's still informational. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This additional info is not those categories. But we have no heading for it. Could we incorporate into Qualifications as a note? Might be okay to drop if not fitting. However we risk losing substantive info. But maybe it's considered "Additional information" not required to keep. The instruction says preserve ALL substantive information. So we need to keep it somewhere. Since we cannot add new headings, we could put it under Qualifications as a paragraph after the qualification standard. Or under Responsibilities? Not appropriate. Probably best to add a
under Qualifications after the standard text. Thus Qualifications section will contain the DOD qualification standard text plus the additional information paragraph(s). We'll keep as one
maybe with line breaks. Now Skills section: we can use the Ideal Candidate list as skills. Now Schedule section: remote/hybrid, telework 2-4 days a pay period. Pay section: actual pay based on locality. Now Responsibilities section: we have the Position Responsibilities list. Also we have the initial duties paragraph (description). Could be included in Responsibilities as prose before list, or as a separate About the role? There's no About the role heading but we could treat the description as part of Responsibilities. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we could have an About the role section for the introductory description. That seems appropriate. Let's create About the role with the introductory paragraph (the first paragraph). Then Responsibilities with the list. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule. Now we need to output HTML fragment only. Let's craft. About the role:
... the paragraph ...
Responsibilities:Responsibilities
- ... each item ...
Requirements
- ... each condition ...