Test & Validation Engineer

We need to output HTML fragment with sections: About the role? The posting includes description after title. 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 need to parse content. Title: Test & Validation Engineer Belong. Connect. Grow. with KBR! (but we don't repeat title as heading). The page already shows it. We need to include sections: - About the role: likely the introductory paragraph(s) after title: "KBR is seeking a Test & Validation Engineer to support the MSEIT contract at Space Systems Command (SSC). This role supports the program's testing and validation activities across multiple software development teams supporting U.S. Space Force mission systems. Working under the guidance of the Test & Validation Lead, this individual will execute test plans, perform integration and user acceptance testing activities, document results, manage defects, and support release readiness efforts. The position provides an excellent opportunity to develop expertise in software testing, mission validation, Agile delivery, and operational acceptance processes within a complex DoD environment. The successful candidate should be comfortable learning new systems, working directly with developers and users, and actively participating in hands-on testing activities. The program is evolving toward CI/CD-oriented software delivery, and this role will help support increasing levels of automation and continuous testing." That's about the role. - Responsibilities: list after "Responsibilities". The posting enumerates many bullet points: Test Execution – Execute functional, integration, regression, and end-to-end tests across mission applications and software systems; Integration Testing Support – Assist in developing, executing, and documenting integration tests; User Acceptance Testing Support – Support – Support planning and execution of user acceptance testing; Defect Management – Document, reproduce, track, verify software defects; Test Documentation – Develop and maintain test procedures, test cases, test reports, validation artifacts; Active Secret or higher clearance (maybe part of requirements); Release Readiness Support – Assist with test execution and validation activities supporting software releases and operational deployments; Test Environment Coordination – Support configuration, preparation, and maintenance of testing environments and test data; Automation Support – Assist in development and execution of automated testing activities and continuous testing practices where appropriate; Cross-Team Collaboration – Work closely with software developers, systems engineers, DevSecOps personnel, and operational stakeholders; Continuous Improvement – Identify opportunities to improve test procedures, test coverage, and validation workflows. We need to put these as

• . - Work Environment: includes location, travel, working hours, clearance, degree, experience, etc. This could be Requirements/Qualifications/Skills sections. We need to decide sections: Requirements, Qualifications, Skills. The posting lists: - Required Ability to obtain and maintain a DoD Secret clearance - Bachelor’s degree in engineering, computer science, math, physics, or related technical field - 2+ years of experience supporting software testing, quality assurance, system validation, or related technical activities - Familiarity with software development lifecycles and testing methodologies - Experience executing software test cases and documenting test results - Strong analytical and troubleshooting skills - Strong written and verbal communication skills - Ability to work effectively within Agile software development environments - Familiarity with Jira, Confluence, or similar collaboration and issue-tracking tools - Ability to manage multiple tasks and priorities simultaneously - Strong communication and collaboration skills across technical and non-technical teams - Proficient in Microsoft Office products (Word, Excel, Powerpoint) These could be Requirements (or Qualifications). Then Desired section includes many desired qualifications: Active Secret or higher clearance (again), Master's degree, experience supporting DoD, Space Force, mission-critical software programs, familiarity with Agile methodologies, exposure to integration testing, API testing, system-level validation, familiarity with CI/CD concepts, experience using test management tools and defect tracking systems, understanding of SATCOM systems, mission systems, operational C2 environments, familiarity with cloud-native or Kubernetes-based software environments, experience working directly with users during acceptance testing, exposure to automated testing tools such as Selenium, Playwright, Cypress, Postman, Robot Framework, Karate, or similar, experience creating test scripts or supporting test automation efforts, familiarity with REST APIs, microservices, distributed application architectures, experience supporting DevSecOps or software factory environments, exposure to performance testing, resiliency testing, or operational validation activities, familiarity with AI-enabled mission systems or data-driven applications, certifications such as INCOSE CSEP/ESEP. We could combine Requirements and Qualifications? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have clear Responsibilities. We have Requirements (mandatory) and Qualifications (desired). Could treat Requirements as mandatory, Qualifications as desired. Skills: maybe list technical skills like Jira, Confluence, Microsoft Office, etc. But many of those appear in requirements. Could separate. Better: Use Requirements for mandatory (clearance, degree, years experience, familiarity with SDLC, test execution, analytical skills, communication, Agile, Jira/Confluence, multitasking, communication across teams, MS Office). Use Qualifications for desired (Master's, DoD experience, Agile methodologies, integration/API testing, CI/CD, test management tools, SATCOM, cloud-native, user acceptance, automation tools, REST APIs, DevSecOps, performance testing, AI, certifications). Skills could be maybe a subset like "Strong analytical and troubleshooting skills, Strong written and verbal communication skills, Ability to work effectively within Agile, Familiarity with Jira/Confluence, Ability to manage multiple tasks, Strong communication across teams, Proficient in MS Office". But that overlaps with Requirements. Might be redundant. Given instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one "Requirements" section, and maybe have "Skills" separate? Or combine all into "Requirements". But we need to follow headings list; we can omit sections if no real specific content. We must include a section only when posting has real specific content for it. We have content for About the role, Responsibilities, Requirements (mandatory), Qualifications (desired), Benefits, Pay. Also maybe Schedule? Not given beyond "Working Hours: Standard". That's schedule info but it's generic "Standard". Might be considered not specific enough? It says "Working Hours: Standard". That's not specific detail; maybe we can omit Schedule because it's just "Standard". The instruction: never emit a 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 the posting actually states them. For Schedule, we have "Working Hours: Standard". That's somewhat generic but still states something. However "Standard" could be considered placeholder? Not sure. Safer to omit Schedule if not specific. The posting also mentions "Location: El Segundo, CA (Work-from-home flexibility with on-site support as required)" and "Travel Requirements: Minimal". That could be part of Work Environment but not a separate heading. Could be included in About the role or Requirements? Might be better to include in About the role? But we already have About the role covering role description. Could add a separate "Work Environment" but not in allowed headings. So we could fold location/travel into About the role or Requirements. Probably include in About the role as extra sentences. Benefits: The posting includes "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 specific enough for Benefits. Pay: "Basic Compensation: $95,000 to $147,000 in El Segundo, CA 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 pay range. So include Pay. Schedule: Not specific beyond "Working Hours: Standard". Might be considered too generic; we can omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to use

  for each section heading. Inside each section, we need

  for prose,

  • for lists. We must preserve all substantive information, not invent or summarize away detail. We must not repeat job title as heading. We must not include Job ID/requisition numbers as headings; we can drop them. We must remove boilerplate like EEO, equal opportunity, etc. Also remove "Ready to Make a Difference?" and application instructions. Also remove "Belong, Connect and Grow at KBR" etc. Also remove "We Deliver – Together." etc. Also remove "KBR is an equal opportunity employer." etc. We need to keep all substantive info: responsibilities list, requirements list, qualifications list, benefits, pay, location/travel maybe. Let's craft. About the role paragraph: combine the introductory paragraphs plus location/travel maybe. We'll write:

    About the role

    KBR is seeking a Test & Validation Engineer to support the MSEIT contract at Space Systems Command (SSC). This role supports the program's testing and validation activities across multiple software development teams supporting U.S. Space Force mission systems. Working under the guidance of the Test & Validation Lead, the individual will execute test plans, perform integration and user acceptance testing activities, document results, manage defects, and support release readiness efforts. The position provides an excellent opportunity to develop expertise in software testing, mission validation, Agile delivery, and operational acceptance processes within a complex DoD environment. The successful candidate should be comfortable learning new systems, working directly with developers and users, and actively participating in hands‑on testing activities. The program is evolving toward CI/CD‑oriented software delivery, and this role will help support increasing levels of automation and continuous testing. The role is based in El Segundo, CA with work‑from‑home flexibility and on‑site support as required; travel requirements are minimal.

    That seems to capture location/travel. Now Responsibilities:

    Responsibilities

    • Test Execution – Execute functional, integration, regression, and end‑to‑end tests across mission applications and software systems.
    • Integration Testing Support – Assist in developing, executing, and documenting integration tests validating interactions across systems, services, and mission workflows.
    • User Acceptance Testing Support – Support planning and execution of user acceptance testing activities, including coordination with operational users and stakeholder organizations.
    • Defect Management – Document, reproduce, track, and verify software defects identified during testing activities.
    • Test Documentation – Develop and maintain test procedures, test cases, test reports, and validation artifacts.
    • Release Readiness Support – Assist with test execution and validation activities supporting software releases and operational deployments.
    • Test Environment Coordination – Support configuration, preparation, and maintenance of testing environments and test data.
    • Automation Support – Assist in development and execution of automated testing activities and continuous testing practices where appropriate.
    • Cross‑Team Collaboration – Work closely with software developers, systems engineers, DevSecOps personnel, and operational stakeholders to support quality and delivery objectives.
    • Continuous Improvement – Identify opportunities to improve test procedures, test coverage, and validation workflows.
    Now Requirements (mandatory):

    Requirements

    • Ability to obtain and maintain a DoD Secret clearance.
    • Bachelor’s degree in engineering, computer science, math, physics, or a related technical field.
    • 2+ years of experience supporting software testing, quality assurance, system validation, or related technical activities.
    • Familiarity with software development lifecycles and testing methodologies.
    • Experience executing software test cases and documenting test results.
    • Strong analytical and troubleshooting skills