Acquisition Engineer
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Remove boilerplate like EEO, etc. Must preserve all substantive info.
We need to parse the posting.
Title: Acquisition Engineer Belong. Connect. Grow. with KBR! (but we ignore title heading). The content:
First paragraph: "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."
Then "Why Join Us? With KBR, you will be at the forefront of Innovative systems.You will join a connected network of KBR personnel that spans every aspect of designing, acquiring, and operating the Nation's most precious systems.Be prepared to make a positive, needed impact on our National Security while working with recognized experts and pioneers in the field."
That's about the role/why join us. Could be "About the role" or "Why Join Us". We'll map to "About the role". Use About the role
then
with that content. Next: "Key Responsibilities" heading. Then bullet list of responsibilities. Let's extract responsibilities: - "KBR is looking for an Acquisition Engineer with Space Systems to provide support to Government Space System acquisition efforts." (maybe part of responsibilities) - "In this role, you will bridge be the bridge between Contracts, Acquisition, and Systems Engineering." - "To be successful at this role, you'll need to have significant experience with Space Systems and DOD Acquisitions." (maybe qualification) - "You will work in a well-funded program office with multiple MSAs in multiple phases." - Then list: SOW: Writing the Statement of Work for upcoming acquisitions - RFI's and RFP's: Contribute to RFI & RFP strategy; write and prepare documents for RFI's and RFP's - Acquisition: Carrying a Major System Acquisitions and various Task Orders and other contract actions through Acquisition Processes such as ASC and CRP; Advising on best practices and guidelines for contract types and approval authorities, reviewing CDRLs, and providing innovative acquisition recommendations to solve challenging issues with the optimal courses of action. - Oversight: Overseeing contract execution including Milestone Payment Plans and Incentive Plans; Advising Contracting Officer (CO) and Contracting Officer Technical Representative (COTR) on contract and acquisition items - Technical: Identifying risks and providing unique courses of action to solve complex technical problems - Accuracy: Reviewing contractor submissions for technical accuracy and providing government personnel detailed critical analysis - Compliance: Assist with contract compliance assessments Also "Work Environment Location: On-site Chantilly, VA Travel Requirements: Once a month Working Hours: Standard" - these could be Schedule or maybe Benefits? Actually schedule: Working Hours: Standard, Travel Requirements: Once a month. Location maybe not needed. We have "Qualifications Required:" then list: - Clearance: Must possess and be able to maintain an active TS/SCI with Poly - Education & Experience: BS/BA 18+ years, or MS/MA 15+ years, or PhD and 12+ years - Specific Experience: 15+ years of experience with Space Systems acquisition - Experience with Acquisition and Contracts topics like structure of contracts, execution of task orders and fixed price contracts, the government competitive acquisition process, negotiations - At least 5 years of experience with IC group - Experience with DoD & IC acquisitions, including source selections on Major System Acquisition - Experience with Systems Engineering processes across the development life cycle - Policy: Familiarity with IC and DoD Acquisition regulations and policies - Mentor: Ability to mentor junior contractors and Government team members - Reporting: Track and report progress at multiple levels of Contractor and Government leadership Then "Ready to Make a Difference? Close with a strong call to action, encouraging potential candidates to apply and highlighting the opportunity to make a significant impact in the role." This is a call to action; we might include as part of About the role or maybe a separate section? Not needed. Then "KBR Benefits KBR offers a selection of competitive lifestyle benefits which could include 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule. We support career advancement through professional training and development." That's Benefits. Then "Belong, Connect and Grow at KBR At KBR, we are passionate about our people and our Zero Harm culture. These inform all that we do and are at the heart of our commitment to, and ongoing journey toward being a People First company. That commitment is central to our team of team’s philosophy and fosters an environment where everyone can Belong, Connect and Grow. We Deliver – Together." This is fluff but maybe part of About the role? It's generic but we could include as part of About the role? It's not specific to role but still part of posting. However we should avoid filler? It's not boilerplate EEO; it's about culture. Could be included in About the role. Then "KBR is an equal opportunity employer..." That's EEO boilerplate, should be removed. Then "R2124613" is Job ID, should be dropped. Pay and Schedule: Not explicitly given besides Working Hours: Standard, Travel Requirements: Once a month. That's schedule info. So we can create a Schedule section with that info. Pay: Not mentioned, so we should NOT create Pay section. Thus sections: About the role, Responsibilities, Requirements (maybe Qualifications?), Skills? The posting includes Qualifications and Specific Experience; we could combine into Requirements or Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which to use. We have qualifications and requirements content. Could use "Qualifications" for the clearance, education, experience. Could also have "Requirements" for specific experience? But we can combine. Better: Use "Qualifications" for the education/clearance etc. Use "Requirements" for specific experience? But we have both. However we should avoid thin sections. Maybe combine all qualification-like content under "Qualifications". Then we don't need Requirements. Skills: Not explicitly listed; maybe we could treat "Experience with Acquisition and Contracts topics" etc as skills. But we can skip Skills if not distinct. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Schedule. Check if we have any content for Skills: Not really. Now we need to preserve all substantive info, not invent or summarize away detail. Must not omit details like "multiple MSAs in multiple phases", "ASC and CRP", etc. We need to format lists with
- . Let's craft About the role paragraph: combine the initial paragraphs and maybe the Belong Connect Grow culture paragraph? Might be okay to include but ensure not too generic. We'll include the initial description and why join us. Paragraph: "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. With KBR, you will be at the forefront of innovative systems. You will join a connected network of KBR personnel that spans every aspect of designing, acquiring, and operating the Nation's most precious systems. Be prepared to make a positive, needed impact on our National Security while working with recognized experts and pioneers in the field. At KBR, we are passionate about our people and our Zero Harm culture. These inform all that we do and are at the heart of our commitment to, and ongoing journey toward being a People First company. That commitment is central to our team of team’s philosophy and fosters an environment where everyone can Belong, Connect and Grow. We Deliver – Together." We need to ensure we didn't lose any content: The phrase "Innovative systems." maybe missing a space; but okay. Now Responsibilities: list items. We need to capture each bullet as separate
- . Let's list:
- Provide support to Government Space System acquisition efforts as an Acquisition Engineer with Space Systems.
- Bridge between Contracts, Acquisition, and Systems Engineering.
- Work in a well-funded program office with multiple MSAs in multiple phases.
- Writing the Statement of Work for upcoming acquisitions.
- Contribute to RFI & RFP strategy; write and prepare documents for RFI's and RFP's.
- Carrying a Major System Acquisitions and various Task Orders and other contract actions through Acquisition Processes such as ASC and CRP; Advising on best practices and guidelines for contract types and approval authorities, reviewing CDRLs, and providing innovative acquisition recommendations to solve challenging issues with the optimal courses of action.
- Overseeing contract execution including Milestone Payment Plans and Incentive Plans; Advising Contracting Officer (CO) and Contracting Officer Technical Representative (COTR) on contract and acquisition items.
- Identifying risks and providing unique courses of action to solve complex technical problems.
- Reviewing contractor submissions for technical accuracy and providing government personnel detailed critical analysis.
- Assist with contract compliance assessments.
We should keep the exact phrasing maybe but can adjust slightly for readability but must preserve info. Avoid adding new info.
Now Qualifications: list:
- Must possess and be able to maintain an active TS/SCI with Poly.
- Education & Experience: BS/BA with 18+ years, or MS/MA with 15+ years, or PhD with 12+ years.
- 15+ years of experience with Space Systems acquisition.
- Experience with Acquisition and Contracts topics: structure of contracts, execution of task orders and fixed price contracts, government competitive acquisition process, negotiations.
- At least 5 years of experience with IC group.
- Experience with DoD & IC acquisitions, including source selections on Major System Acquisition.
- Experience with Systems Engineering processes across the development life cycle.
- Familiarity with IC and DoD Acquisition regulations and policies.
- Ability to mentor junior contractors and Government team members.
- Track and report progress at multiple levels of Contractor and Government leadership.
Now Benefits: list:
- 401K plan with company match
- medical
- dental
- vision
- life insurance
- AD&D
- flexible spending account
- disability
- paid time off
- flexible work schedule
- professional training and development (career advancement)
We could combine as list.
Schedule: includes:
- Location: On-site Chantilly, VA (maybe not schedule but we can include location in schedule? The instruction says Schedule section for schedule info. Location maybe not schedule but we could include as part of About the role? However we have location info; we could put in Schedule? Might be odd. Better to include location in About the role or maybe a separate "Work Environment" but not in allowed headings. Since we must only use allowed headings, we could put location in About the role paragraph. Or we could put in Schedule as "Work Location: On-site Chantilly, VA". But schedule is about hours/travel. We'll include location in About the role.
Schedule: Travel Requirements: Once a month; Working Hours: Standard.
Thus schedule section:
Travel Requirements: Once a month
Working Hours: Standard
maybe combine. Now ensure we didn't include boilerplate: removed EEO, Job ID, etc. Now output HTML fragment. Let's construct:About the role
...
Responsibilities
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Schedule
Travel Requirements: Once a month
Working Hours: Standard