Integration And Test Engineer

We need to output HTML fragment with sections: h3 headings for sections present: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Must only include sections with real specific content. We have: - About the role: first paragraph describing role. That's prose. - Responsibilities: list of duties. - Requirements: includes Required Qualifications and Preferred Qualifications? Could be combined as Requirements/Qualifications. The instruction: use h3 for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have either Requirements or Qualifications. Probably combine Required and Preferred under Requirements. Or separate? The instruction says prefer few substantive sections over many thin ones. So we can have one Requirements section containing both required and preferred qualifications. - Skills: maybe we can extract skills from qualifications: Python, automation tools, etc. But we already have them in qualifications. Could create Skills section but might be redundant. Better to have Requirements covering qualifications and skills. - Benefits: we have benefits list. - Pay: we have pay range. - Schedule: we have Workplace Type (fully onsite) and maybe location. Not exactly schedule but could be considered Schedule? The instruction says include Schedule only if posting actually states them. There's no explicit schedule like hours, shift. Workplace Type is location/onsite. Not schedule. So we may omit Schedule. - About the role: we have that. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We need to use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions, Job ID etc. Also remove About TEKsystems sections (the company description) as boilerplate. Also remove Application Deadline? That's maybe metadata but could be considered minor metadata; we can fold into short

  or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Application Deadline maybe minor metadata; we could include as a short p under About the role? But better to drop as it's not substantive? It's somewhat substantive but maybe minor. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Application deadline is substantive? Might be considered metadata but still info. However they said fold minor metadata into a short

  or drop it. So we could include a short p with "Application deadline: Sep 30, 2026." That's minor metadata. We'll include maybe after About the role. Also Job Type & Location: "This is a Contract position based out of Fairfax, VA." That's substantive about job type and location. Could be included as a short p under About the role or separate? Could be part of About the role. We'll include a p after About the role. Pay And Benefits: we have pay range and benefits list. We'll separate Pay and Benefits sections. Now we need to extract responsibilities list exactly as given: - Support site hardware deployment, integration, checkout, testing, and verification activities. - Perform verification and validation of satellite ground software systems, including Command & Control (C2) and Mission Management (MM) capabilities. - Develop and execute integration and test plans, procedures, and documentation. - Create and maintain automated test scripts using Python and other automation tools. - Analyze system architecture to understand component interactions and identify integration points. - Troubleshoot and resolve complex integration issues through log analysis, debugging, and root cause identification. - Coordinate with software developers, systems engineers, and stakeholders to resolve technical challenges. - Document findings, defects, and corrective actions throughout the testing lifecycle. We'll put each as

• . Requirements: we need to include Required Qualifications and Preferred Qualifications. We'll combine maybe as two sublists? But we can just list all items as
• under Requirements. Must preserve all detail. Required Qualifications list: - Active Top Secret/SCI clearance with the ability to obtain a CI Polygraph. - Experience supporting ground software system verification activities. - Knowledge of Command & Control (C2) and Mission Management (MM) systems. - Strong experience in integration and testing, including planning, execution, and documentation. - Experience with testing tools, automation frameworks, and software verification processes. - Proficiency in Python scripting and automation. - Strong analytical, troubleshooting, and communication skills. Preferred Qualifications list: - Active TS/SCI with CI Polygraph. (Note duplicate of required? Actually same as required but maybe redundant; we keep) - Experience with programming languages such as Python, MATLAB, C, C++, or Java. - Exposure to Model-Based Systems Engineering (MBSE) tools such as Visio and Cameo. - Experience with JIRA, Confluence, Bitbucket, or similar collaboration tools. - Knowledge of Systems Tool Kit (STK) for mission simulation and analysis. - Experience working in Agile development environments. - Familiarity with Gherkin/Cucumber testing frameworks. - Hands-on experience with GitLab or other version control platforms. - Understanding of container technologies such as Docker and Kubernetes. - Experience with AWS cloud services. We'll include both. Benefits list: from "If eligible, the benefits available for this temporary role may include the following:" then list: - Medical, dental & vision - Critical Illness, Accident, and Hospital - 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available - Life Insurance (Voluntary Life & AD&D for the employee and dependents) - Short and long-term disability - Health Spending Account (HSA) - Transportation benefits - Employee Assistance Program - Time Off/Leave (PTO, Vacation or Sick Leave) We'll preserve as list. Pay: we have pay range: "$100.00 - $115.00/hr." plus note about individual compensation depending on factors. We'll keep that as prose maybe

  . Could also include note. We should not include boilerplate like "Eligibility requirements apply to some benefits..." maybe we can keep as part of Benefits section? It's somewhat boilerplate but it's about benefits eligibility. Might be considered substantive? It's generic. Might be okay to keep as a p after benefits list. We must not include sections like "About TEKsystems", "Application Deadline" maybe we can include as minor metadata p. We must output only HTML fragment, no markdown fences. Let's craft:

  About the role

  We are seeking an experienced Systems Integrator to support the integration, verification, and testing of mission-critical ground software systems. This role offers the opportunity to work on advanced space and intelligence-focused programs, collaborating with multidisciplinary engineering teams to ensure successful system deployment and operational readiness.

  Job type: Contract position. Location: Fairfax, VA.

  Application deadline: Sep 30, 2026.

  Responsibilities

  • Support site hardware deployment, integration, checkout, testing, and verification activities.
  • Perform verification and validation of satellite ground software systems, including Command & Control (C2) and Mission Management (MM) capabilities.
  • Develop and execute integration and test plans, procedures, and documentation.
  • Create and maintain automated test scripts using Python and other automation tools.
  • Analyze system architecture to understand component interactions and identify integration points.
  • Troubleshoot and resolve complex integration issues through log analysis, debugging, and root cause identification.
  • Coordinate with software developers, systems engineers, and stakeholders to resolve technical challenges.
  • Document findings, defects, and corrective actions throughout the testing lifecycle.

  Requirements

  • Active Top Secret/SCI clearance with the ability to obtain a CI Polygraph.
  • Experience supporting ground software system verification activities.
  • Knowledge of Command & Control (C2) and Mission Management (MM) systems.
  • Strong experience in integration and testing, including planning, execution, and documentation.
  • Experience with testing tools, automation frameworks, and software verification processes.
  • Proficiency in Python scripting and automation.
  • Strong analytical, troubleshooting, and communication skills.
  • Active TS/SCI with CI Polygraph.
  • Experience with programming languages such as Python, MATLAB, C, C++, or Java.
  • Exposure to Model-Based Systems Engineering (MBSE) tools such as Visio and Cameo.
  • Experience with JIRA, Confluence, Bitbucket, or similar collaboration tools.
  • Knowledge of Systems Tool Kit (STK) for mission simulation and analysis.
  • Experience working in Agile development environments.
  • Familiarity with Gherkin/Cucumber testing frameworks.
  • Hands-on experience with GitLab or other version control platforms.
  • Understanding of container technologies such as Docker and Kubernetes.
  • Experience with AWS cloud services.

  Benefits

  • Medical, dental & vision
  • Critical Illness, Accident, and Hospital
  • 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
  • Life Insurance (Voluntary Life & AD&D for the employee and dependents)
  • Short and long-term disability
  • Health Spending Account (HSA)
  • Transportation benefits
  • Employee Assistance Program
  • Time Off/Leave (PTO, Vacation or Sick Leave)

  Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms.

  Pay

  The pay range for this position is $100.00 - $115.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.

  We should not include Schedule section. Check for any duplicated lines: we have duplicate clearance line (required and preferred). It's okay to keep both as they appear in posting; but we could deduplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplicate is part of posting; we should keep it. It's fine. Check for any boilerplate we inadvertently kept: "Eligibility requirements apply to some benefits..." is from benefits section; we kept it as a p after benefits list. That's okay. Check for any mention of "Job Type & Location" we turned into a p with strong tags. That's okay. Check for any mention of "Workplace Type This is a fully onsite position in Fairfax,VA." We didn't include that; we included location in job type p but not explicit onsite. Could add "Workplace type: Fully onsite." Might be considered substantive. Let's add after location p: maybe another p: "Workplace type: Fully onsite." Or incorporate. We have location p: "Job type: Contract position. Location: Fairfax, VA." We can add "Workplace type: Fully onsite." as another sentence. Let's adjust:

  Job type: Contract position. Location: Fairfax, VA. Workplace type: Fully onsite.

  Now ensure we didn't miss any substantive info: "This is a Contract position based out of Fairfax, VA." covered. "Application Deadline This position is anticipated