Senior Solution Architect

We need to output only HTML fragment, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, legal, navigation, cookie, etc. Also remove duplicated lines, application instructions. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Pay (salary ranges) and Schedule (Standard Scheduled Weekly Hours: 40 hours per week). Also includes Benefits (KBR Benefits). Also includes Location and Travel Requirements maybe under About the role? The posting includes "Why Join Us?" which could be About the role. Also includes "Key Responsibilities". Also includes "Required Qualifications". Also includes "Clearance Requirements". Also includes "Work Environment". Also includes "Location". Also includes "Travel Requirements". Also includes "Working Hours". Also includes "Basic Compensation". Also includes "Additional Compensation". Also includes "KBR Benefits". Also includes "Belong, Connect and Grow at KBR". Also includes "We Deliver – Together." etc. Also includes "Ready to Make a Difference?" etc. Also includes "If you’re excited..." etc. Also includes "KBR Benefits". Also includes "Belong, Connect and Grow at KBR". Also includes "We Deliver – Together." etc. Also includes "KBR is an equal opportunity employer." (boilerplate to remove). Also includes "R2127787" (Job ID) to drop. We need to decide sections: About the role (maybe combine Why Join Us? and overview). Responsibilities (Key Responsibilities). Requirements (maybe Required Qualifications). Qualifications (maybe Clearance Requirements? Actually "Required Qualifications" is a section; we could map to Requirements. Qualifications maybe separate? The instruction says use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have content for About the role: introductory paragraphs about KBR, mission, why join us, etc. Also maybe "Why Join Us?" bullet points. Responsibilities: list under "Key Responsibilities". We need to output as

• items. Requirements: maybe "Required Qualifications" includes bachelor's degree + 10 years experience, etc. Also maybe "Clearance Requirements" could be part of Requirements or Qualifications? The instruction separate Requirements and Qualifications. Usually Requirements are mandatory (education, experience, clearance). Qualifications could be preferred or additional qualifications like skills, knowledge. But we have "Required Qualifications" heading in posting; we could treat that as Requirements. Then Qualifications could be things like "Understanding of Cybersecurity, System of Systems, Software, and Agile Engineering..." etc. Also "Experience leading technical solutioning..." etc. Might be overlapping. We need to decide. Skills: maybe we can extract skills like "Technical solutioning", "Proposal writing", "Market research", "Leadership", "Communication", etc. But we must not invent. We need to see if posting lists specific skills. It mentions "strong team building and leadership capabilities", "ability to interact with SMEs", "understanding of Cybersecurity, System of Systems, Software, and Agile Engineering", "Digital Engineering, Model Based Systems Engineering (MBSE), DevSecOps, and Cloud Architectures". Also "proven ability to derive customer solutions". Also "experience leading technical solutioning". Also "provide responses to RFI". Also "basis of estimates". Those could be skills. But we need to avoid creating thin sections. If we have limited content for Skills, maybe we combine into Requirements or Qualifications. However instruction: Prefer a few substantive sections over many thin ones. So we could omit Skills if not enough substantive content. But we have some skill-like content; maybe we can put under Qualifications. Benefits: we have KBR Benefits paragraph listing benefits. Pay: we have Basic Compensation ranges for different locations, plus Additional Compensation note. Schedule: we have Working Hours: Standard Scheduled Weekly Hours: 40 hours per week. Also Travel Requirements: Minimal 0-20%. That could be part of Schedule? Travel is not schedule but maybe we could include under Schedule or About the role. But we have a Schedule heading; we can include working hours and travel requirements. We must not create sections with filler like "commensurate with experience". Not present. We must not repeat job title as heading. Not include Job ID. We must output only HTML fragment, no /, no markdown fences. Thus produce something like:

  About the role

  ... paragraphs ...

  Responsibilities

  • ...
  ...

  Requirements

  ... (education, experience, clearance)

  Qualifications

  ... (technical understanding, experience leading solutioning, etc.)

  Benefits

  • ...
  ...

  Pay

  ... (salary ranges)

  Schedule

  ... (working hours, travel)

  We need to ensure we preserve all substantive information. Let's extract. First, About the role: The posting starts with "Title Senior Solution Architect Belong. Connect. Grow. with KBR! KBR 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? 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. KBR's Defense & Intel team is seeking a dynamic and experienced Senior Solution Architect with a strong background in creating innovative and customer focused solutions to join our Solution Architect team. This role is pivotal in driving the technical strategy and solution design for business opportunities, ensuring alignment with customer requirements and organizational goals. The ideal candidate will have a proven track record working in Government, Defense, and Intelligence communities, providing support to capture efforts, proposal writing, and oral presentations. This is an exciting opportunity to bring your experience to deliver innovative solutions that help our customers transform, modernize, and accelerate delivery of new capabilities. If you thrive at the intersection of technology and business development, this is the role for you." We need to preserve all that. We'll combine into a few paragraphs. We must not include duplicated lines. There's some repetition maybe. Now Responsibilities: list under "Key Responsibilities". Let's extract each bullet: - engaging in customer shaping efforts, requirements gathering, and proposal support activities, leveraging understanding of industry trends and KBR capabilities to design, develop, and deliver winning proposals. - Collaborate with Business Development, Capture, and Proposal teams to craft compelling, technically sound solutions that align with customer needs and win strategies. - Act as a subject matter expert in the translation of solution requirements into proposal artifacts. - Lead the development of technical volumes for proposals, including writing, reviewing, and editing content to ensure compliance with RFP requirements. - Translate customer objectives into innovative technical solutions that address mission challenges while adhering to budget and schedule constraints. - Conduct market research, identify discriminators, and articulate value propositions that differentiate our solutions from competitors. - Develop comprehensive artifacts such as system designs, technical roadmaps, and implementation plans to support proposal efforts. - Participate in reviews to refine proposal content and ensure alignment with win themes. - Research emerging technologies and incorporate them into solution designs to enhance competitiveness. - Lead and write technical proposals, whitepapers and develop other collaterals in support of technical solutions. - Provide responses to request for information (RFI) and government market surveys or sources sought notice. - Provide basis of estimates (BOEs) for technical solutions. We need to preserve all. Now Requirements: The posting says "Required Qualifications Requires a bachelor’s degree in a technical discipline with a minimum of 10 years of prior experience. Additional experience may be accepted in lieu of degree.The candidate should possess strong team building and leadership capabilities that will engage key internal and external sources to develop clear, concise solutions to difficult problem sets across the DoW and IC. Experience leading technical solutioning in partnership with business development and capture management teams; Technical solutioning experience will be in the defense and intelligence community markets for technology-centric business units providing both services and products to US Government customers.Proven ability to successfully derive customer solutions based on understanding of customer problems that meet technical objectives within cost and schedule. From this in-depth understanding, the ideal candidate will be able to interact with Subject Matter Experts (SMEs), Key Stakeholders (internal to KBR and external), Technical Experts, and other key roles to develop a compelling Solution for strategic growth markets and opportunities aligned with the NSS growth strategy.Understanding of Cybersecurity, System of Systems, Software, and Agile Engineering current and emerging processes in use across Defense and Intelligence Customer communities such as Digital Engineering, Model Based Systems Engineering (MBSE), DevSecOps, and Cloud Architectures. Clearance Requirements: Active Top Secret Clearance is required, with eligibility for TS/SCI ." We need to separate Requirements vs Qualifications. Perhaps Requirements: education, experience, clearance. Qualifications: team building/leadership, experience leading technical solutioning, ability to interact with SMEs, understanding of cybersecurity etc. But the posting lumps them together under "Required Qualifications". However we have to follow instruction: use headings for Requirements and Qualifications separately. We need to decide what goes where. We could treat "Requirements" as the mandatory baseline: bachelor's degree + 10 years experience, active TS clearance eligibility. Then "Qualifications" as the rest: team building/leadership, experience leading technical solutioning, ability to interact with SMEs, understanding of cybersecurity etc. But we must not invent or summarize away detail. We need to preserve all substantive info. So we need to include all those details in either Requirements or Qualifications. Let's extract: Mandatory: - Bachelor’s degree in a technical discipline - Minimum 10 years prior experience (additional experience may be accepted in lieu of degree) - Active Top Secret Clearance required, with eligibility for TS/SCI Other qualifications/experience: - Strong team building and leadership capabilities to engage key internal and external sources to develop clear, concise solutions to difficult problem sets across the DoW and IC. - Experience leading technical solutioning in partnership with business development and capture management teams; technical solutioning experience in defense and intelligence community markets for technology-centric business units providing both services and products to US Government customers. - Proven ability to successfully derive customer solutions based on understanding of customer problems that meet technical objectives within cost and schedule. - Ability to interact with Subject Matter Experts (SMEs), Key Stakeholders (internal to KBR and external), Technical Experts, and other key roles to develop a compelling Solution for strategic growth markets and opportunities aligned with the NSS growth strategy. - Understanding of Cybersecurity, System of Systems, Software, and Agile Engineering current and emerging processes in use across Defense and Intelligence Customer communities such as Digital Engineering, Model Based Systems Engineering (MBSE), DevSecOps, and Cloud Architectures. We could also include "Clearance Requirements" as part of Requirements. Now Skills: Not explicitly listed as a separate section; we could omit Skills heading if not enough content. But we have some skill-like content: strong team building and leadership capabilities, ability to interact with SMEs, understanding of cybersecurity etc. Those could be considered qualifications. So we may not need a separate Skills section. Benefits: "KBR Benefits K