Strategic Senior Acquisition Support Specialist
KBR Careers · El Segundo, CA · 1 mo ago
OTHR$100k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about KBR, role description. We need to use for section headings: 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. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Why Join Us?" maybe that's part of About the role? Could be considered as Benefits? Actually "Why Join Us?" includes Innovative Projects, Collaborative Environment, Impactful Work. That's more like benefits or selling points. Could be placed under Benefits? But Benefits section should be about compensation/benefits. The posting includes "Basic Compensation: $99,700 to $164,00 in California". Also "KBR Benefits" paragraph listing benefits. So we have Pay and Benefits sections.
We also have "Work Environment Location: On-siteTravel Requirements: MinimalWorking Hours: Standard". That's Schedule? Actually schedule maybe working hours. So we can include Schedule section with location, travel, hours.
Qualifications vs Requirements: The posting lists "Qualifications Required:" and "Desired". Could treat Required as Requirements, Desired as Skills? Or Qualifications. We need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
We have Responsibilities clearly listed under "Key Responsibilities". So Responsibilities section.
Qualifications: maybe the "Qualifications Required:" list (active DOD Secret clearance, Bachelor's degree, 5+ years experience, etc.) That's qualifications.
Skills: maybe the "Desired" list (Top Secret Clearance, Master's degree, Ground systems acquisition experience, MILSATCOM experience, Systems engineering experience, Certifications, Familiarity with Agile, Jira, Confluence, cloud architecture, databases). That could be Skills.
Requirements: maybe we could combine required qualifications as Requirements? But we already used Qualifications for required. Could treat Requirements as the mandatory items (clearance, degree, experience). Qualifications as desired? But spec says we have both Requirements and Qualifications headings. We need to decide distribution. Usually Requirements are mandatory, Qualifications are preferred. But we have both Required and Desired. So we can map Required to Requirements, Desired to Qualifications. Then Skills could be something else? But we already used Qualifications for desired. Could treat Skills as technical skills (Microsoft Office, etc.) but those are also in Required. Actually Required includes "Proficient in Microsoft Office products". That's a skill. Could put that under Skills. However we need to avoid duplication.
Let's think: The posting has:
- Required: active DOD Secret clearance, Bachelor's degree, 5+ years experience in government weapon systems acquisitions and program management and/or contracts management within DoD, experience leading DoD acquisition programs through major milestone for an ACAT I program, demonstrated understanding of DoD acquisition policies and processes and ability to apply DoD policies to program plans, demonstrated knowledge of DoDI 5000.85 and DoDI 5000.87, demonstrated ability to work effectively with DoD customers, strong interpersonal skills, communication (oral and written), and presentation skills, proficient in Microsoft Office products (Word, Excel, PowerPoint).
- Desired: Top Secret Clearance, Master's degree, Ground systems acquisition experience, MILSATCOM experience, Systems engineering experience, Certifications in DoD acquisition, Certifications in Systems Engineering (INCOSE ESEP, CSEP), Familiarity with Agile development, Jira and Confluence tools, cloud architecture systems as well as relational and non-relational databases.
Thus we could map:
Requirements: the Required list (mandatory).
Qualifications: the Desired list (preferred qualifications).
Skills: maybe we could extract specific technical skills like Microsoft Office proficiency, Agile, Jira, Confluence, cloud architecture, databases. But those appear in both Required and Desired. Could put Microsoft Office under Skills, and the desired technical familiarity under Skills as well. But then Qualifications would be just education/clearance? Hmm.
Better: Use Requirements for mandatory (clearance, degree, experience, etc.). Use Qualifications for desired (advanced degree, certifications, etc.). Use Skills for specific technical proficiencies (Microsoft Office, Agile/Jira/Confluence, cloud architecture, databases). That seems reasonable.
Now About the role: Should contain the introductory paragraphs describing the role, team, mission, etc. Also maybe the "Why Join Us?" bullet points could be part of About the role or Benefits? But we have Benefits separate. The "Why Join Us?" includes Innovative Projects, Collaborative Environment, Impactful Work. Those are more like selling points, could be part of About the role. We'll include them in About the role as prose.
Responsibilities: list from "Key Responsibilities". Use
for section headings: 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. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Why Join Us?" maybe that's part of About the role? Could be considered as Benefits? Actually "Why Join Us?" includes Innovative Projects, Collaborative Environment, Impactful Work. That's more like benefits or selling points. Could be placed under Benefits? But Benefits section should be about compensation/benefits. The posting includes "Basic Compensation: $99,700 to $164,00 in California". Also "KBR Benefits" paragraph listing benefits. So we have Pay and Benefits sections.
We also have "Work Environment Location: On-siteTravel Requirements: MinimalWorking Hours: Standard". That's Schedule? Actually schedule maybe working hours. So we can include Schedule section with location, travel, hours.
Qualifications vs Requirements: The posting lists "Qualifications Required:" and "Desired". Could treat Required as Requirements, Desired as Skills? Or Qualifications. We need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
We have Responsibilities clearly listed under "Key Responsibilities". So Responsibilities section.
Qualifications: maybe the "Qualifications Required:" list (active DOD Secret clearance, Bachelor's degree, 5+ years experience, etc.) That's qualifications.
Skills: maybe the "Desired" list (Top Secret Clearance, Master's degree, Ground systems acquisition experience, MILSATCOM experience, Systems engineering experience, Certifications, Familiarity with Agile, Jira, Confluence, cloud architecture, databases). That could be Skills.
Requirements: maybe we could combine required qualifications as Requirements? But we already used Qualifications for required. Could treat Requirements as the mandatory items (clearance, degree, experience). Qualifications as desired? But spec says we have both Requirements and Qualifications headings. We need to decide distribution. Usually Requirements are mandatory, Qualifications are preferred. But we have both Required and Desired. So we can map Required to Requirements, Desired to Qualifications. Then Skills could be something else? But we already used Qualifications for desired. Could treat Skills as technical skills (Microsoft Office, etc.) but those are also in Required. Actually Required includes "Proficient in Microsoft Office products". That's a skill. Could put that under Skills. However we need to avoid duplication.
Let's think: The posting has:
- Required: active DOD Secret clearance, Bachelor's degree, 5+ years experience in government weapon systems acquisitions and program management and/or contracts management within DoD, experience leading DoD acquisition programs through major milestone for an ACAT I program, demonstrated understanding of DoD acquisition policies and processes and ability to apply DoD policies to program plans, demonstrated knowledge of DoDI 5000.85 and DoDI 5000.87, demonstrated ability to work effectively with DoD customers, strong interpersonal skills, communication (oral and written), and presentation skills, proficient in Microsoft Office products (Word, Excel, PowerPoint).
- Desired: Top Secret Clearance, Master's degree, Ground systems acquisition experience, MILSATCOM experience, Systems engineering experience, Certifications in DoD acquisition, Certifications in Systems Engineering (INCOSE ESEP, CSEP), Familiarity with Agile development, Jira and Confluence tools, cloud architecture systems as well as relational and non-relational databases.
Thus we could map:
Requirements: the Required list (mandatory).
Qualifications: the Desired list (preferred qualifications).
Skills: maybe we could extract specific technical skills like Microsoft Office proficiency, Agile, Jira, Confluence, cloud architecture, databases. But those appear in both Required and Desired. Could put Microsoft Office under Skills, and the desired technical familiarity under Skills as well. But then Qualifications would be just education/clearance? Hmm.
Better: Use Requirements for mandatory (clearance, degree, experience, etc.). Use Qualifications for desired (advanced degree, certifications, etc.). Use Skills for specific technical proficiencies (Microsoft Office, Agile/Jira/Confluence, cloud architecture, databases). That seems reasonable.
Now About the role: Should contain the introductory paragraphs describing the role, team, mission, etc. Also maybe the "Why Join Us?" bullet points could be part of About the role or Benefits? But we have Benefits separate. The "Why Join Us?" includes Innovative Projects, Collaborative Environment, Impactful Work. Those are more like selling points, could be part of About the role. We'll include them in About the role as prose.
Responsibilities: list from "Key Responsibilities". Use - .
Pay: we have "Basic Compensation: $99,700 to $164,00 in California". Also note "The offered rate will be based on the selected candidate’s knowledge, skills, abilities and/or experience and in consideration of internal parity." That's specific content for Pay. So include Pay section with that sentence.
Benefits: we have "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.
Schedule: we have "Work Environment Location: On-siteTravel Requirements: MinimalWorking Hours: Standard". Also maybe mention "On-site" location, minimal travel, standard hours. So Schedule section with those details.
We must not include boilerplate like "Belong. Connect. Grow." tagline? That's part of intro but could be kept as part of About the role. The tagline appears at start: "Title Strategic Senior Acquisition Support Specialist Belong. Connect. Grow. with KBR!" We should not repeat job title as heading, but we can keep the tagline as part of About the role prose? It's basically a slogan. Might be considered boilerplate? It's part of the posting but not navigation/legal. It's okay to keep.
We must remove duplicated lines, application instructions like "Ready to Make a Difference? If you’re excited about making a significant impact ... we encourage you to apply and join our team." That's application instruction; remove. Also remove "KBR is an equal opportunity employer..." etc. Remove EEO boilerplate. Remove "R2130324" (Job ID). Remove "Why Join Us?" heading? We'll incorporate its content but not as heading.
Now produce HTML fragment with sections in order: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
for each heading. Use
for prose,
- for lists.
Let's craft About the role prose: Combine intro paragraphs: 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. KBR (formerly LinQuest) is the prime contractor on the Military Satellite Communications (MILSATCOM) Systems Engineering, Integration and Test (MSEIT) contract. You will join a Systems Engineering team defining the next generation of space communication systems supporting Space Force Military Satellite Communications. You will support Systems Engineering & Integration activities in a multidisciplinary and collaborative environment. You will interface and collaborate with SE&I team members, contractors, government civilians and members of the USSF to provide acquisition management development and support. The MILSATCOM Systems Engineering, Integration, and Test (MSEIT) effort provides leading edge Systems Engineering & Integration (SE&I) for the Space Force’s Space Systems Command. We support the Space Force’s acquisition of state-of-the-art Military Satellite Communications systems, providing global secure protected communications for our nation’s warfighters. We seek technical individuals who will thrive in a highly collaborative work environment of small teams, using the most modern tools and methodologies to tackle the challenges of integrating complex space and ground communications systems. Why Join Us? 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.
We can keep that as prose, maybe separate sentences.
Now Responsibilities list: bullet points from "Key Responsibilities". Let's extract each sentence:
- Provide advice to Program/Project Managers regarding acquisition strategies, schedules, contracting, budgeting and execution
- Develop, draft, tailor, and coordinate overarching program planning and execution documents as prescribed by DoDI 5000.02 / Acquisition Framework, and relevant DoD Instructions (DoDI 5000.85 and DoDI 5000.87), AF, and local unit instructions and policies.
- Support the development of the ASP, RFI/Market Research, RPP, Milestone Statutory and Regulatory requirements, Statement of Work, Compliance and Reference Document, Contract Deliverable Requirements List, and Rights in Technical Data and Software
- Lead and coordinate all acquisition activities in preparing for Planning/Execution events
- Prepare periodic status reports, coordinate, and execute periodic staff meetings and technical interchange meetings, and develop acquisition plans, schedules, and executive program briefings
- Provide technical and programmatic assessments of contractor design planning/execution reviews to assess progress, risks and issues, and the ability to achieve mission requirements
- Provide program element coordination, staffing and monitoring; advise and assist government customer regarding funding commitments, obligations, and expenditures
Make each a
- .
Now Requirements list (mandatory): bullet points:
- Active DOD Secret clearance required
- Bachelor's degree
- 5+ years’ experience in government weapon systems acquisitions and program management and/or contracts management within the Department of Defense
- Experience leading DoD acquisition programs through major milestone for an ACAT I program
- Demonstrated understanding of DoD acquisition policies and processes and ability to apply DoD policies to program plans
- Demonstrated knowledge of DoDI 5000.85 and DoDI 5000.87
- Demonstrated ability to work effectively with DoD customers
- Strong interpersonal skills, communication (oral and written), and presentation skills
- Proficient in Microsoft Office products (Word, Excel, PowerPoint)
Now Qualifications list (desired): bullet points:
- Desired Top Secret Clearance
- Master's degree
- Ground systems acquisition experience
- MILSATCOM experience
- Systems engineering experience
- Certifications in DoD acquisition
- Certifications in Systems Engineering (INCOSE ESEP, CSEP)
- Familiarity with Agile development, Jira and Confluence tools, cloud architecture systems as well as relational and non-relational databases
Now Skills list: we could include technical proficiencies not covered elsewhere: maybe Microsoft Office already in Requirements; but we could still include under Skills? Might duplicate. Better to put Microsoft Office under Skills, and keep Requirements focused on clearance, degree, experience, etc. But then Requirements would lose the Microsoft Office proficiency. However the posting lists it under Required. But we can still keep it under Skills and note it's required. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we must include Microsoft Office proficiency somewhere. If we put it under Skills, it's still included. That's fine. But we must not omit it. So we can move Microsoft Office to Skills. Then Requirements will not have it. That's okay as long as we keep the info somewhere.
Thus Requirements list
for each heading. Use
for prose,
- for lists. Let's craft About the role prose: Combine intro paragraphs: 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. KBR (formerly LinQuest) is the prime contractor on the Military Satellite Communications (MILSATCOM) Systems Engineering, Integration and Test (MSEIT) contract. You will join a Systems Engineering team defining the next generation of space communication systems supporting Space Force Military Satellite Communications. You will support Systems Engineering & Integration activities in a multidisciplinary and collaborative environment. You will interface and collaborate with SE&I team members, contractors, government civilians and members of the USSF to provide acquisition management development and support. The MILSATCOM Systems Engineering, Integration, and Test (MSEIT) effort provides leading edge Systems Engineering & Integration (SE&I) for the Space Force’s Space Systems Command. We support the Space Force’s acquisition of state-of-the-art Military Satellite Communications systems, providing global secure protected communications for our nation’s warfighters. We seek technical individuals who will thrive in a highly collaborative work environment of small teams, using the most modern tools and methodologies to tackle the challenges of integrating complex space and ground communications systems. Why Join Us? 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. We can keep that as prose, maybe separate sentences. Now Responsibilities list: bullet points from "Key Responsibilities". Let's extract each sentence: - Provide advice to Program/Project Managers regarding acquisition strategies, schedules, contracting, budgeting and execution - Develop, draft, tailor, and coordinate overarching program planning and execution documents as prescribed by DoDI 5000.02 / Acquisition Framework, and relevant DoD Instructions (DoDI 5000.85 and DoDI 5000.87), AF, and local unit instructions and policies. - Support the development of the ASP, RFI/Market Research, RPP, Milestone Statutory and Regulatory requirements, Statement of Work, Compliance and Reference Document, Contract Deliverable Requirements List, and Rights in Technical Data and Software - Lead and coordinate all acquisition activities in preparing for Planning/Execution events - Prepare periodic status reports, coordinate, and execute periodic staff meetings and technical interchange meetings, and develop acquisition plans, schedules, and executive program briefings - Provide technical and programmatic assessments of contractor design planning/execution reviews to assess progress, risks and issues, and the ability to achieve mission requirements - Provide program element coordination, staffing and monitoring; advise and assist government customer regarding funding commitments, obligations, and expenditures Make each a
- . Now Requirements list (mandatory): bullet points: - Active DOD Secret clearance required - Bachelor's degree - 5+ years’ experience in government weapon systems acquisitions and program management and/or contracts management within the Department of Defense - Experience leading DoD acquisition programs through major milestone for an ACAT I program - Demonstrated understanding of DoD acquisition policies and processes and ability to apply DoD policies to program plans - Demonstrated knowledge of DoDI 5000.85 and DoDI 5000.87 - Demonstrated ability to work effectively with DoD customers - Strong interpersonal skills, communication (oral and written), and presentation skills - Proficient in Microsoft Office products (Word, Excel, PowerPoint) Now Qualifications list (desired): bullet points: - Desired Top Secret Clearance - Master's degree - Ground systems acquisition experience - MILSATCOM experience - Systems engineering experience - Certifications in DoD acquisition - Certifications in Systems Engineering (INCOSE ESEP, CSEP) - Familiarity with Agile development, Jira and Confluence tools, cloud architecture systems as well as relational and non-relational databases Now Skills list: we could include technical proficiencies not covered elsewhere: maybe Microsoft Office already in Requirements; but we could still include under Skills? Might duplicate. Better to put Microsoft Office under Skills, and keep Requirements focused on clearance, degree, experience, etc. But then Requirements would lose the Microsoft Office proficiency. However the posting lists it under Required. But we can still keep it under Skills and note it's required. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we must include Microsoft Office proficiency somewhere. If we put it under Skills, it's still included. That's fine. But we must not omit it. So we can move Microsoft Office to Skills. Then Requirements will not have it. That's okay as long as we keep the info somewhere. Thus Requirements list