Sr Acquisitions Analyst SME
KBR Careers · Belleville, IL · 1 mo ago
SalesFull-time
We need to output HTML fragment with sections: About the role? The posting includes description. We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting: Title Sr Acquisitions Analyst SME Belong. Connect. Grow. with KBR! Then description: KBR’s National Security Solutions team provides high-end engineering... etc. Then "Why Join Us?" bullet points. Then description of role. Then "Key Responsibilities" bullet list. Then "Work Environment" with location, travel, hours. Then "Required Qualifications" bullet list. Then "Desired Qualifications". Then "Ready to Make a Difference?" etc. Then "Belong, Connect and Grow at KBR" etc. Then EEO boilerplate and Job ID.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Ready to Make a Difference?" maybe not needed? It's more marketing but could be considered part of About the role? Probably we can incorporate into About the role.
We need to preserve all substantive information. So we need sections: About the role (maybe combine the introductory paragraphs and Why Join Us?). Responsibilities (Key Responsibilities). Requirements (maybe Required Qualifications). Qualifications (maybe Desired Qualifications? Actually they said Requirements and Qualifications separate; but we can treat Required Qualifications as Requirements, Desired Qualifications as Qualifications? Or Skills? We'll decide.
Skills: maybe we can extract skills from Required/Desired: analytical, problem-solving, decision-making, communication, interpersonal, etc. But we can also put them under Skills section.
Benefits, Pay, Schedule: only include if posting states them. The posting does not mention benefits, pay, schedule specifics besides Work Environment: Location, Travel Requirements, Working Hours. So we can include Schedule? It says Working Hours: Standard. That's schedule info. So we can include a Schedule section with "Standard". Benefits and Pay not present, so omit.
We need to avoid filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /. Use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting: Title Sr Acquisitions Analyst SME Belong. Connect. Grow. with KBR! Then description: KBR’s National Security Solutions team provides high-end engineering... etc. Then "Why Join Us?" bullet points. Then description of role. Then "Key Responsibilities" bullet list. Then "Work Environment" with location, travel, hours. Then "Required Qualifications" bullet list. Then "Desired Qualifications". Then "Ready to Make a Difference?" etc. Then "Belong, Connect and Grow at KBR" etc. Then EEO boilerplate and Job ID.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Ready to Make a Difference?" maybe not needed? It's more marketing but could be considered part of About the role? Probably we can incorporate into About the role.
We need to preserve all substantive information. So we need sections: About the role (maybe combine the introductory paragraphs and Why Join Us?). Responsibilities (Key Responsibilities). Requirements (maybe Required Qualifications). Qualifications (maybe Desired Qualifications? Actually they said Requirements and Qualifications separate; but we can treat Required Qualifications as Requirements, Desired Qualifications as Qualifications? Or Skills? We'll decide.
Skills: maybe we can extract skills from Required/Desired: analytical, problem-solving, decision-making, communication, interpersonal, etc. But we can also put them under Skills section.
Benefits, Pay, Schedule: only include if posting states them. The posting does not mention benefits, pay, schedule specifics besides Work Environment: Location, Travel Requirements, Working Hours. So we can include Schedule? It says Working Hours: Standard. That's schedule info. So we can include a Schedule section with "Standard". Benefits and Pay not present, so omit.
We need to avoid filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /. Use headings, - for lists,
for prose.
We must not repeat job title as heading. So no heading for Sr Acquisitions Analyst.
We need to include metadata like Job ID? They said do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can drop Job ID or put in a short p. Probably drop.
Now craft sections:
About the role: combine introductory paragraph about KBR, National Security Solutions team, Why Join Us? bullet points, and role description (the paragraph after "KBR is seeking a highly skilled...").
Responsibilities: list from Key Responsibilities.
Requirements: Required Qualifications list.
Qualifications: Desired Qualifications list.
Skills: maybe extract from Required/Desired: Strong analytical, problem-solving, decision-making skills; Excellent communication and interpersonal skills; Ability to work effectively in a fast-paced, dynamic environment; etc. Could also include knowledge of DoD acquisition policies, etc. But those are already in Requirements. Might be redundant. Perhaps we can omit Skills section if content overlaps. But we need to follow instruction: prefer a few substantive sections over many thin ones. Could combine Skills into Responsibilities or Requirements. But we need to decide.
We have sections: About the role, Responsibilities, Requirements, Qualifications, Work Environment (maybe as Schedule? Actually Work Environment includes location, travel, hours). Could treat as Schedule? But schedule is just hours. Better to make a section "Work Environment" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map Work Environment to Schedule? Schedule is about hours; but we have location and travel. Could we put location and travel under About the role? Or we could create a Schedule section with "Standard" hours and maybe include location/travel in About the role? The instruction: only include sections when posting has real specific content for it. It didn't forbid adding other headings not in list? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we should use those headings; but maybe we can also use other headings? The examples are given, but likely they expect only those headings. Safer to stick to those.
Thus we need to fit location/travel/hours into one of those sections. Perhaps About the role can include location/travel/hours as prose. Or we can create a Schedule section with hours and mention location/travel in About the role.
Let's put location/travel in About the role paragraph. Schedule section: "Standard". Benefits and Pay omitted.
Now craft content.
About the role: include KBR description, Why Join Us? bullet points (maybe as ), role overview paragraph, location/travel/hours? We'll put location/travel/hours as a short paragraph at end.
Responsibilities: list from Key Responsibilities.
Requirements: list from Required Qualifications.
Qualifications: list from Desired Qualifications.
Skills: maybe we can omit if not needed. But we have to decide if we need Skills section. Could combine skills into Requirements or Qualifications. Since we already have those, we can omit Skills to avoid thin section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule.
Now ensure we preserve all substantive information: need to keep all bullet points from Why Join Us?, Key Responsibilities, Required Qualifications, Desired Qualifications. Also need to keep the description of role (the paragraph after "KBR is seeking a highly skilled...").
Also need to keep the sentence about "Serves as the primary KBR lead..." etc.
Let's extract.
From posting:
Intro: "KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound impact on the country’s most critical role – protecting our national security."
Why Join Us? bullet points:
- Innovative Projects: KBR’s work is at the forefront of engineering, logistics, operations, science, program management, mission IT and cybersecurity solutions.
- Collaborative Environment: Be part of a dynamic team that thrives on collaboration and innovation, fostering a supportive and intellectually stimulating workplace.
- Impactful Work: Your contributions will be pivotal in designing and optimizing defense systems that ensure national security and shape the future of space defense.
Then role description: "KBR is seeking a highly skilled and experienced Senior Acquisition Analyst to provide expert leadership to a three-man team executing operational and logistics analysis product delivery to Air Mobility Command (AMC) and Air Force Life Cycle Management Center (AFLCMC) for airlift modernization initiatives associated with the NGAL weapon system. Leads the planning, coordination, and execution of operational analysis activities focused on identifying and evaluating NGAL aircraft modernization alternatives for global mobility operations to inform Government-led requirements and acquisition development. The incumbent will develop and deliver NGAL mission need analysis products, capability models, and requirements artifacts supporting NGAL capability alternatives definition, evaluation, and ensuring compliance with DoW mission requirements. The incumbent will be directly responsible for translating Government-approved operational needs into actionable Department of War (DoW) requirements and acquisition documentation, providing specialized acquisition and knowledge into the operational analysis of potential NGAL capability solutions, requirements and options. The incumbent will develop and deliver products related to requirements identification, requirements selection and refinement, acquisition strategy development, schedule and risk management, and integration coordination across multiple stakeholders, including AMC, Air Staff, AFLCMC, Systems Program Offices (SPOs) and other stakeholders. The incumbent will play a key role in informing the Government-led process for the selection, development and delivery of advanced aircraft capabilities while ensuring compliance with applicable DoW, Air Force, AMC and AFLCMC acquisition and product delivery frameworks."
Then "Key Responsibilities" bullet list:
- Serves as the primary KBR lead for NGAL programmatic, systems engineering, and strategic planning efforts.
- Oversees/performs NGAL operational analysis ensuring NGAL compliance with Department of Defense (DoD), Air Force, AMC and AFLCMC policies and regulations
- Drives the comprehensive research, rigorous analysis, and product delivery to inform Next Generation Airlift (NGAL) Analysis of Alternatives (AoA) decisions and Joint Force Requirements Process (JFRP) documentation.
- Synchronizes Air Mobility Command (AMC) Mission Area (MA) requirements to enable precise representation and integration into core capability documents..
- Coordinates with cross-organizational teams, including Air Staff, MAJCOM headquarters, Systems Program Office and operational stakeholders to ensure program objectives are met
- Leverage extensive acquisition expertise deliver draft Analysis of Alternatives (AoA), JFRP and System Attributes and Requirements Document (SARD) documentation
- Monitor analysis progress and performance, implementing corrective actions as necessary
- Prepare and present detailed analysis results, analysis summaries and status reports as required to senior AMC leadership and stakeholders
Note some grammar issues but keep as is.
Work Environment: "Location: On-Site, Scott AFB, ILTravel Requirements: Moderate 20-50%Working Hours: Standard"
Required Qualifications bullet list:
- Active Top Secret Clearance with SCI eligibility
- Bachelor’s degree in Business Administration, Engineering, or a related field
- Experience executing and managing DoW Analysis of Alternatives (AoA) activities.
- Minimum of 15 years of experience in military acquisition requirements generation and management of DoW acquisition programs
- In-depth knowledge of DoD acquisition policies, procedures, and regulations
- Understanding of DoD Risk, Issue and Opportunity (RIO) Management Guide for Defense Acquisition Program processes and procedures
- MAJCOM experience in A5/A8 or equivalent
- Strong analytical, problem-solving, and decision-making skills
- Excellent communication and interpersonal skills
- Ability to work effectively in a fast-paced, dynamic environment
Desired Qualifications bullet list:
- Master’s degree
- 20+ years of experience in military acquisition requirements generation and management of DoW acquisition programs
- Three or more years of experience in Headquarters Air Mobility Command (AMC)
- Three or more years of experience in SAF/AQ, HAF/A5 and/or HAF/A8
- Experience working with the Joint Capabilities Integration and Development System (JCIDS) process and documentation
- Defense Acquisition Workforce Improvement Act (DAWIA) Certification in Program Management at Advanced or equivalent
- Knowledge of DoW 5000.02 and AFLCMC Policies, Processes, and Procedures
Then "Ready to Make a Difference?" paragraph: marketing, could be included in About the role? Might be considered boilerplate? It's not EEO but it's a call to action. Could be considered application instruction? It says "If you’re excited about making a significant impact ... we encourage you to apply and join our team at KBR. Let's shape the future together." That's basically application encouragement. Might be considered application instructions; we should remove per instruction: remove application instructions. So drop that.
Then "Belong, Connect and Grow at KBR" paragraph about Zero Harm culture etc. That's also marketing/boilerplate; could be considered part of About the role? It's about company culture. Might be okay to keep as part of About the role? It's not EEO. It's about culture. Could be kept. But it's somewhat generic. However it's substantive about company values. Might keep.
But we must avoid duplication. The earlier "Why Join Us?" already covered similar points. This paragraph repeats Belong, Connect and Grow. Might be considered duplicated. Safer to drop.
EEO boilerplate and Job ID: drop.
Thus final HTML:
About the role
KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound
- for lists,
for prose. We must not repeat job title as heading. So no heading for Sr Acquisitions Analyst. We need to include metadata like Job ID? They said do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can drop Job ID or put in a short p. Probably drop. Now craft sections: About the role: combine introductory paragraph about KBR, National Security Solutions team, Why Join Us? bullet points, and role description (the paragraph after "KBR is seeking a highly skilled..."). Responsibilities: list from Key Responsibilities. Requirements: Required Qualifications list. Qualifications: Desired Qualifications list. Skills: maybe extract from Required/Desired: Strong analytical, problem-solving, decision-making skills; Excellent communication and interpersonal skills; Ability to work effectively in a fast-paced, dynamic environment; etc. Could also include knowledge of DoD acquisition policies, etc. But those are already in Requirements. Might be redundant. Perhaps we can omit Skills section if content overlaps. But we need to follow instruction: prefer a few substantive sections over many thin ones. Could combine Skills into Responsibilities or Requirements. But we need to decide. We have sections: About the role, Responsibilities, Requirements, Qualifications, Work Environment (maybe as Schedule? Actually Work Environment includes location, travel, hours). Could treat as Schedule? But schedule is just hours. Better to make a section "Work Environment" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map Work Environment to Schedule? Schedule is about hours; but we have location and travel. Could we put location and travel under About the role? Or we could create a Schedule section with "Standard" hours and maybe include location/travel in About the role? The instruction: only include sections when posting has real specific content for it. It didn't forbid adding other headings not in list? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we should use those headings; but maybe we can also use other headings? The examples are given, but likely they expect only those headings. Safer to stick to those. Thus we need to fit location/travel/hours into one of those sections. Perhaps About the role can include location/travel/hours as prose. Or we can create a Schedule section with hours and mention location/travel in About the role. Let's put location/travel in About the role paragraph. Schedule section: "Standard". Benefits and Pay omitted. Now craft content. About the role: include KBR description, Why Join Us? bullet points (maybe as
- ), role overview paragraph, location/travel/hours? We'll put location/travel/hours as a short paragraph at end.
Responsibilities: list from Key Responsibilities.
Requirements: list from Required Qualifications.
Qualifications: list from Desired Qualifications.
Skills: maybe we can omit if not needed. But we have to decide if we need Skills section. Could combine skills into Requirements or Qualifications. Since we already have those, we can omit Skills to avoid thin section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule.
Now ensure we preserve all substantive information: need to keep all bullet points from Why Join Us?, Key Responsibilities, Required Qualifications, Desired Qualifications. Also need to keep the description of role (the paragraph after "KBR is seeking a highly skilled...").
Also need to keep the sentence about "Serves as the primary KBR lead..." etc.
Let's extract.
From posting:
Intro: "KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound impact on the country’s most critical role – protecting our national security."
Why Join Us? bullet points:
- Innovative Projects: KBR’s work is at the forefront of engineering, logistics, operations, science, program management, mission IT and cybersecurity solutions.
- Collaborative Environment: Be part of a dynamic team that thrives on collaboration and innovation, fostering a supportive and intellectually stimulating workplace.
- Impactful Work: Your contributions will be pivotal in designing and optimizing defense systems that ensure national security and shape the future of space defense.
Then role description: "KBR is seeking a highly skilled and experienced Senior Acquisition Analyst to provide expert leadership to a three-man team executing operational and logistics analysis product delivery to Air Mobility Command (AMC) and Air Force Life Cycle Management Center (AFLCMC) for airlift modernization initiatives associated with the NGAL weapon system. Leads the planning, coordination, and execution of operational analysis activities focused on identifying and evaluating NGAL aircraft modernization alternatives for global mobility operations to inform Government-led requirements and acquisition development. The incumbent will develop and deliver NGAL mission need analysis products, capability models, and requirements artifacts supporting NGAL capability alternatives definition, evaluation, and ensuring compliance with DoW mission requirements. The incumbent will be directly responsible for translating Government-approved operational needs into actionable Department of War (DoW) requirements and acquisition documentation, providing specialized acquisition and knowledge into the operational analysis of potential NGAL capability solutions, requirements and options. The incumbent will develop and deliver products related to requirements identification, requirements selection and refinement, acquisition strategy development, schedule and risk management, and integration coordination across multiple stakeholders, including AMC, Air Staff, AFLCMC, Systems Program Offices (SPOs) and other stakeholders. The incumbent will play a key role in informing the Government-led process for the selection, development and delivery of advanced aircraft capabilities while ensuring compliance with applicable DoW, Air Force, AMC and AFLCMC acquisition and product delivery frameworks."
Then "Key Responsibilities" bullet list:
- Serves as the primary KBR lead for NGAL programmatic, systems engineering, and strategic planning efforts.
- Oversees/performs NGAL operational analysis ensuring NGAL compliance with Department of Defense (DoD), Air Force, AMC and AFLCMC policies and regulations
- Drives the comprehensive research, rigorous analysis, and product delivery to inform Next Generation Airlift (NGAL) Analysis of Alternatives (AoA) decisions and Joint Force Requirements Process (JFRP) documentation.
- Synchronizes Air Mobility Command (AMC) Mission Area (MA) requirements to enable precise representation and integration into core capability documents..
- Coordinates with cross-organizational teams, including Air Staff, MAJCOM headquarters, Systems Program Office and operational stakeholders to ensure program objectives are met
- Leverage extensive acquisition expertise deliver draft Analysis of Alternatives (AoA), JFRP and System Attributes and Requirements Document (SARD) documentation
- Monitor analysis progress and performance, implementing corrective actions as necessary
- Prepare and present detailed analysis results, analysis summaries and status reports as required to senior AMC leadership and stakeholders
Note some grammar issues but keep as is.
Work Environment: "Location: On-Site, Scott AFB, ILTravel Requirements: Moderate 20-50%Working Hours: Standard"
Required Qualifications bullet list:
- Active Top Secret Clearance with SCI eligibility
- Bachelor’s degree in Business Administration, Engineering, or a related field
- Experience executing and managing DoW Analysis of Alternatives (AoA) activities.
- Minimum of 15 years of experience in military acquisition requirements generation and management of DoW acquisition programs
- In-depth knowledge of DoD acquisition policies, procedures, and regulations
- Understanding of DoD Risk, Issue and Opportunity (RIO) Management Guide for Defense Acquisition Program processes and procedures
- MAJCOM experience in A5/A8 or equivalent
- Strong analytical, problem-solving, and decision-making skills
- Excellent communication and interpersonal skills
- Ability to work effectively in a fast-paced, dynamic environment
Desired Qualifications bullet list:
- Master’s degree
- 20+ years of experience in military acquisition requirements generation and management of DoW acquisition programs
- Three or more years of experience in Headquarters Air Mobility Command (AMC)
- Three or more years of experience in SAF/AQ, HAF/A5 and/or HAF/A8
- Experience working with the Joint Capabilities Integration and Development System (JCIDS) process and documentation
- Defense Acquisition Workforce Improvement Act (DAWIA) Certification in Program Management at Advanced or equivalent
- Knowledge of DoW 5000.02 and AFLCMC Policies, Processes, and Procedures
Then "Ready to Make a Difference?" paragraph: marketing, could be included in About the role? Might be considered boilerplate? It's not EEO but it's a call to action. Could be considered application instruction? It says "If you’re excited about making a significant impact ... we encourage you to apply and join our team at KBR. Let's shape the future together." That's basically application encouragement. Might be considered application instructions; we should remove per instruction: remove application instructions. So drop that.
Then "Belong, Connect and Grow at KBR" paragraph about Zero Harm culture etc. That's also marketing/boilerplate; could be considered part of About the role? It's about company culture. Might be okay to keep as part of About the role? It's not EEO. It's about culture. Could be kept. But it's somewhat generic. However it's substantive about company values. Might keep.
But we must avoid duplication. The earlier "Why Join Us?" already covered similar points. This paragraph repeats Belong, Connect and Grow. Might be considered duplicated. Safer to drop.
EEO boilerplate and Job ID: drop.
Thus final HTML:
About the role
KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound