Senior Solution Architect

We need to output HTML fragment with sections: headings

for each section present. Use

• for lists. Use

  for prose. No job title heading. No Job ID. Remove boilerplate: EEO, equal opportunity, etc. Also remove navigation, cookie, legal, scam warning, duplicated lines, application instructions. Keep substantive info. We need to parse the posting. Key sections: About the role? The intro paragraphs: "KBR provides high-end engineering..." etc. Could be "About the role" or "About the position". We'll create sections: About the role, Responsibilities, Requirements (or Qualifications), Benefits, Pay, Schedule maybe. We have "Why Join Us?" bullet list: Innovative Projects, Collaborative Environment, Impactful Work. That could be under "Why Join Us?" but not required heading list; we could treat as Benefits? Actually it's selling points. Could be under "About the role" or separate "Why Join Us?" but we only include sections when there is real content. Could include "Why Join Us?" as a section with

  Why Join Us?

  and
  . That seems appropriate. Then "Key Responsibilities" list. Then "Required Qualifications" list. Then "Clearance Requirements" maybe part of Qualifications? Could be separate but we can include under Requirements. Then "Work Environment" includes location, travel, working hours. That could be Schedule? Actually schedule is standard 40 hours per week. Location and travel maybe not a section; we could include under "Work Environment" but not required heading list; we could embed in

  . The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings if applicable. If not, we can still use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we can use other headings if needed but better to stick to those. We have content for About the role, Responsibilities, Requirements/Qualifications, Benefits, Pay, Schedule. Also maybe Skills? Not explicitly. Could combine Requirements and Qualifications. We have Pay: salary ranges per location. So we need a Pay section with those details. Schedule: Standard Scheduled Weekly Hours: 40 hours per week. So we can have Schedule section. Benefits: KBR Benefits list. Location and travel maybe could be part of About the role or Work Environment but not a required heading; we could include in About the role paragraph. Clearance Requirements: could be part of Requirements. We must not include boilerplate like EEO, equal opportunity, etc. Also remove duplicated lines, navigation, cookie, legal, scam warning, application instructions (like "Ready to Make a Difference? If you’re excited...". That's more of a call to action; maybe considered application instruction? It's encouraging to apply. Might be considered boilerplate? The instruction says remove application instructions. That line is basically a call to apply; we should remove it. Also "Let's shape the future together." maybe also remove. Also the "KBR Benefits" heading is okay. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract substantive paragraphs. Intro: "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 "Why Join Us?" bullet list: Innovative Projects..., Collaborative Environment..., Impactful Work... Then paragraph: "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." Then "Key Responsibilities" heading then list of responsibilities (multiple sentences each). We'll convert each bullet to

  . Then "Required Qualifications" heading then list: "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." then bullet list of qualifications. We need to preserve all details; we can keep the first sentence as a

  maybe then

  for the rest. Then "Clearance Requirements: Active Top Secret Clearance is required, with eligibility for TS/SCI ." Could be a

  . Then "Work Environment Location: Northern Virginia; Dayton OH; Colorado Springs CO; El Segundo CA; King of Prussia PA; Huntsville AL; Charleston SC; Patuxent River, MDTravel Requirements: Minimal 0-20%Working Hours: Standard Scheduled Weekly Hours: 40 hours per week." We'll separate location and travel and schedule. We could put location and travel under About the role or a separate "Work Environment" heading but not in list; we can just put as

  . Then Pay section: list three ranges. Then Benefits section: list benefits. We must not include the EEO statement at end. Also remove duplicated lines like "Belong, Connect and Grow at KBR" etc. That's maybe fluff but could be considered substantive? It's about culture; maybe keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Belong, Connect and Grow at KBR" is a tagline; might be considered boilerplate? It's not EEO but could be considered marketing fluff. However it's part of the posting; but we might keep as part of About the role? Safer to keep? The instruction says prefer a few substantive sections over many thin ones. That tagline is not substantive detail about job; it's more branding. I'd consider it boilerplate and remove. Also "We Deliver – Together." maybe remove. Also "KBR is an equal opportunity employer..." remove. Also the job ID "R2127787" remove. Now construct HTML. We'll start with

  About the role

  then

  ...

  maybe include Why Join Us? as a
  under that? Could be separate heading Why Join Us? but we can incorporate as

  Why Join Us?

  then
  . However the instruction examples didn't list Why Join Us? but we can still use

  . It's okay. But to keep sections limited, we could merge Why Join Us? into About the role as a list. I'll do:

  About the role

  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.
  Then responsibilities:

  Responsibilities

  • Engage 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.
  Then qualifications:

  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.

  • 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 DoD 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.
  • 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.
  • Clearance Requirements: Active Top Secret Clearance is required, with eligibility for TS/SCI.
  Note: I merged clearance into qualifications list as an item. Then Work Environment location/travel/schedule maybe as

  Work Environment

  but not in examples; but we could put location and travel under About the role? Might be better to have a separate section but we can use

  Work Environment

  as it's substantive. The instruction didn't forbid other headings; just gave examples. So okay. We'll do:

  Work Environment

  Location: Northern Virginia; Dayton OH; Colorado Springs CO; El Segundo CA; King of Prussia PA; Huntsville AL; Charleston SC; Patuxent River, MD.

  Travel Requirements: Minimal 0-20%.

  Working Hours: Standard Scheduled Weekly Hours: 40 hours per week.

  Then Pay:

  Pay

  $189,000.00 - $284,000.00 (This range is for the Colorado area only).

  $198,000.00 - $298,000.00 (This range is for the Maryland area only).

  $207,000.00 - $311,000.00 (This range