Senior Solution Architect

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Title: Senior Solution Architect Belong. Connect. Grow. with KBR! (but we ignore title heading). The posting includes: - Intro: KBR provides high-end engineering and advanced technology solutions... etc. This is about the company and role. Could be "About the role" or "About KBR". We need to decide sections. We have sections: "Why Join Us?" with bullet points (Innovative Projects, Collaborative Environment, Impactful Work). That's like Benefits? Actually it's reasons to join. Could be "Benefits"? But they also have a separate "KBR Benefits" later. So "Why Join Us?" could be considered "About the role" or "Highlights". But we need to follow allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Responsibilities: "Key Responsibilities" list. We have Required Qualifications: list. We have Clearance Requirements: Active Top Secret Clearance required, with eligibility for TS/SCI. We have Work Environment: Location list, Travel Requirements, Working Hours. We have Basic Compensation: salary ranges per location. We have Additional Compensation: mention of bonuses etc. We have KBR Benefits: list of benefits. We have "Belong, Connect and Grow at KBR" etc: fluff, maybe can be omitted as boilerplate? It's not EEO but it's cultural statement. Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Belong, Connect and Grow at KBR" is not exactly those, but could be considered fluff. However it's substantive? It's more marketing. Might be okay to keep as part of About the role? But we need to avoid filler. It's not specific job duty. Could be omitted. We also have "Ready to Make a Difference?" etc: application encouragement, maybe can be omitted as application instructions? It's not exactly instructions to apply, but it's a call to action. Might be considered application instruction? Safer to omit. We also have "KBR is an equal opportunity employer..." which is EEO boilerplate, must be removed. We also have "R2127787" at end: job ID, drop. Thus we need to produce sections with substantive content. Potential sections: - About the role: could include intro paragraph about KBR, mission, role purpose. - Responsibilities: list from Key Responsibilities. - Requirements / Qualifications: we have Required Qualifications (education, experience) plus Clearance Requirements, plus maybe "Understanding of Cybersecurity..." etc. Those could be under Qualifications or Requirements. We have both "Required Qualifications" and then a paragraph of qualifications. We could combine into a single "Qualifications" section. - Skills: maybe we could extract skills like "Technical solutioning", "Cybersecurity, System of Systems, Software, Agile Engineering, Digital Engineering, MBSE, DevSecOps, Cloud Architectures". But we have no explicit Skills heading. Could create Skills section if we have specific skills list. The posting includes "Understanding of Cybersecurity, System of Systems, Software, and Agile Engineering current and emerging processes...". That's a skill set. Could be placed under Skills. - Benefits: KBR Benefits list. - Pay: Basic Compensation ranges. - Schedule: Working Hours (Standard Scheduled Weekly Hours: 40 hours per week). Also Travel Requirements maybe part of Schedule? But schedule section is for hours; we could include travel under Schedule? Might be better to include travel under Schedule or maybe under About the role? The instruction: only create Schedule section if posting actually states them. It does state Working Hours: Standard Scheduled Weekly Hours: 40 hours per week. Travel Requirements: Minimal 0-20%. That's also schedule-ish. Could include both. We must not create sections with filler. So we need to ensure each section has real content. Let's extract content. About the role: We can combine the introductory paragraphs: "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." Also maybe include "Why Join Us?" bullet points? Those are reasons to join, could be part of About the role or Benefits. But we have separate Benefits section for KBR Benefits. The "Why Join Us?" includes Innovative Projects, Collaborative Environment, Impactful Work. Those are more about the role's attributes, could be part of About the role. We'll include them as a list under About the role? But we need to use

  • for any list of duties/requirements/benefits. So we can put those as a list. Thus About the role section:

    About the role

    then a

    with the intro sentences, then a

    • list for the three Why Join Us points. Responsibilities: list from Key Responsibilities. We'll extract each bullet. Responsibilities list: - 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'll put each as
    • . Requirements/Qualifications: We have Required Qualifications: bachelor’s degree in a technical discipline with minimum 10 years prior experience; additional experience may be accepted in lieu of degree. Also: strong team building and leadership capabilities; 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 derive customer solutions based on understanding of customer problems that meet technical objectives within cost and schedule; ability to interact with SMEs, Key Stakeholders, Technical Experts, etc.; 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 required, with eligibility for TS/SCI. We could split into Qualifications (education/experience) and Skills (technical understanding). But we have allowed headings: Requirements, Qualifications, Skills. We could use Qualifications for education/experience, Skills for technical understanding, and maybe Requirements for clearance? But clearance is also a requirement. Could combine. Better: Use "Qualifications" for education/experience and leadership etc. Use "Skills" for technical understanding (Cybersecurity, etc.). Use "Requirements" for clearance and maybe location? But location is work environment. But we need to avoid thin sections. Perhaps combine education/experience and clearance into "Qualifications". And technical understanding into "Skills". That yields two sections. Let's decide: - Qualifications: education, experience, team building/leadership, experience leading technical solutioning, ability to derive solutions, ability to interact with SMEs etc. - Skills: Understanding of Cybersecurity, System of Systems, Software, Agile Engineering, Digital Engineering, MBSE, DevSecOps, Cloud Architectures. - Requirements: Clearance Requirements (Active Top Secret Clearance required, eligibility for TS/SCI). Could also include location? But location is work environment, maybe we put under About the role or separate? Not a standard heading. Could put under About the role as part of location? But we have no heading for location. Could include in About the role as a paragraph. Alternatively, we could create a "Work Environment" section but not allowed headings. So we need to fit location/travel/hours into existing allowed sections: maybe About the role includes location, travel, hours. Or we could create a "Schedule" section for hours and travel, and maybe mention location in About the role. Thus: - About the role: includes company description, role impact, Why Join Us bullets, location list, travel requirements, working hours. - Responsibilities: list. - Qualifications: education/experience, leadership, etc. - Skills: technical understanding list. - Benefits: KBR Benefits list. - Pay: Basic Compensation ranges. - Schedule: maybe we already used hours in About the role; but we could still have Schedule section for working hours (40 hrs/week) and travel (0-20%). However we said we prefer few substantive sections over many thin ones. If we put hours and travel in About the role, we may not need Schedule section. But we need to ensure we don't omit substantive info. If we include location, travel, hours in About the role, that's fine. Thus we may not need Schedule section. But we need to check if we have any content for Benefits: yes KBR Benefits list. Pay: yes. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. Check if any of these sections would be empty/filler: each has content. Now we need to format. We must not repeat job title as heading. So no

      Senior Solution Architect

      . We must not put Job ID/requisition numbers as headings; we will drop R2127787. We must not include boilerplate EEO etc. We must not include application instructions like "Ready to Make a Difference?" etc. We must not include duplicated lines. Now craft HTML. We'll start with

      About the role

      Then a

      containing: "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." Then maybe add location list as part of same paragraph or separate

      . Could be separate

      for location: "Locations: Northern Virginia; Dayton OH; Colorado Springs CO; El Segundo CA; King of Prussia PA; Huntsville AL; Charleston SC; Patuxent River, MD." Then travel and hours: "Travel Requirements: Minimal