2026-0092 Support JTS/FAST Testing (NS) REMOTE - 2 Jul
Park Lane Recruitment ·www.plr.ltd
Apply direct
Deadline Date: Thursday 02 July 2026
Requirement: Support JTS/FAST testing
Location: Remote, with occasional on-site work at NCIA The Hague (NLD)
Period of Performance: As soon as possible but no later than 03 August 2026 - 31 December 2026
Cost Not to Exceed: 50,850 EUR
Required Security Clearance: NATO Secret
Please do NOT apply for any NATO contract positions unless you meet ALL the following criteria:
Statement of Work
Introduction:
The list below defines the overarching objectives of the engagement and establishes the intended outcomes that the Contractor is expected to achieve through the delivery of the different work packages described in this document. These objectives serve as the guiding principles against which all deliverables shall be measured. The Contractor is expected to align their approach, methodology, and resource planning with these objectives throughout the duration of the engagement.
Under the direction and guidance of the Solution Architect, Service Delivery Manager, Test Manager, and Project Manager, the services to be provided are related to the testing, validation, verification, quality assurance, and test automation of JTS/FAST software modules. It is envisioned that these services shall be provided by one experienced software test engineer.
The Contractor shall provide the following deliverables classified per service:
Output: Updated, maintained, and improved JTS/FAST test cases covering agreed functional, technical, regression, integration and release-related test scenarios. The deliverable includes the development and maintenance of manual and automated test cases required to support JTS/FAST baseline development, defect verification, regression testing, release preparation, User Acceptance Testing, and operational validation activities. Test cases shall be developed or updated in accordance with agreed requirements, user stories, defects, change requests, release priorities, and project planning. The test case baseline shall include, where applicable, test cases for agreed JTS/FAST capabilities such as interface behaviour, configuration changes, interoperability scenarios, and other functionality included in the agreed release scope.
Outcome: JTS/FAST testing remains structured, repeatable, traceable, auditable, and aligned with the agreed requirements, work items, release priorities, and operational use cases. The maintained test case baseline supports consistent verification of JTS/FAST functionality across development, integration, regression, acceptance, and release preparation activities. It also reduces testing ambiguity by ensuring that test cases clearly define the required preconditions, test steps, expected results, pass/fail criteria, assumptions, and dependencies.
Acceptance Criteria A1: Assigned test cases are created, reviewed, updated, or maintained in accordance with agreed requirements, priorities, release scope, or work package timeframe; test cases clearly define preconditions, test steps, expected results, pass/fail criteria, assumptions, and dependencies where applicable; test cases are stored and maintained in the agreed test management, issue tracking, configuration management, or project repository environment; test cases are traceable to relevant requirements, user stories, defects, change requests, release objectives, or operational scenarios where applicable; obsolete, duplicated, incomplete, or no longer applicable test cases are identified and updated or proposed for removal; test cases are reviewed and updated where required following software, configuration, interface, or requirement changes; test cases are suitable for execution in the agreed development, integration, test, release, or acceptance environment; test cases support manual, automated, regression, integration, interface, interoperability, or release-related testing where applicable; test case updates are made available for review within the agreed timeframe; test case limitations, blocked areas, or missing dependencies are documented and communicated when required.
KPIs:
Deliverable B1: Updated JTS/FAST automated test suite
Output: Automated tests developed, updated, maintained, refactored, and executed to support repeatable verification of JTS/FAST functionality, regression testing, integration testing, interface testing, deployment verification, non-functional testing where applicable, and release validation. The deliverable includes the development and maintenance of automated test scripts, automated test data, test assertions, execution configurations, and supporting automation assets using the agreed tools, frameworks, repositories, and environments. Automated testing shall support the continued evolution and sustainment of the JTS/FAST software baseline and shall contribute to earlier defect detection, regression stability, and improved release confidence. Where technically applicable, the automated test suite shall be expanded to cover agreed functionality included in JTS/FAST baseline or release scope, including areas such as interface configuration, database replication, and other assigned functional or regression scenarios.
Outcome: Improved software quality and delivery confidence through repeatable automated testing, earlier defect detection, reduced manual testing effort, and strengthened regression coverage. The automated test suite supports more efficient verification of JTS/FAST changes across development, integration, release preparation, and sustainment activities. It also improves the ability to identify regressions and provides reusable test evidence for release readiness and governance decisions.
Acceptance Criteria B1: Automated tests are developed, updated, maintained, or refactored for assigned functionality where technically applicable; automated tests are executable in the agreed development, build, test, integration, or CI/CD environment; automated tests include clear assertions, expected results, and pass/fail logic; automated tests are committed, reviewed, and maintained in the agreed configuration management environment; automated test failures are analysed and either corrected, reported, linked to known defects, or documented for follow-up; automated tests do not introduce unacceptable instability into the automated test suite; automated tests are updated where required following software, interface, configuration, data model, or environment changes; automated tests are aligned with agreed coding, scripting, testing, and configuration management practices; automation limitations, dependencies, unstable tests, or blocked scenarios are documented and communicated where applicable; automated test execution results are made available to support defect analysis, regression testing, and release readiness decisions.
KPIs:
Qualifications
Each contractor personnel must meet the following requirements:
Requirement: Support JTS/FAST testing
Location: Remote, with occasional on-site work at NCIA The Hague (NLD)
Period of Performance: As soon as possible but no later than 03 August 2026 - 31 December 2026
Cost Not to Exceed: 50,850 EUR
Required Security Clearance: NATO Secret
Please do NOT apply for any NATO contract positions unless you meet ALL the following criteria:
- Current National or NATO SECRET clearance
- Nationality of one of the NATO member countries
- Current work visa for the specific location if applying for an in-country position
Statement of Work
Introduction:
- The NATO Information and Communication Agency (NCIA) located in The Hague, The Netherlands, is the Interoperability Assurance Authority for NATO.
- In light of this responsibility, the C2 Service Centre is looking for a service contract which can provide NCIA with testing and quality assurance support for the continued maintenance, validation and evolution of the Joint Targeting System / Functional Area Service for dynamic and time sensitive Targeting (JTS/FAST) software.
The list below defines the overarching objectives of the engagement and establishes the intended outcomes that the Contractor is expected to achieve through the delivery of the different work packages described in this document. These objectives serve as the guiding principles against which all deliverables shall be measured. The Contractor is expected to align their approach, methodology, and resource planning with these objectives throughout the duration of the engagement.
Under the direction and guidance of the Solution Architect, Service Delivery Manager, Test Manager, and Project Manager, the services to be provided are related to the testing, validation, verification, quality assurance, and test automation of JTS/FAST software modules. It is envisioned that these services shall be provided by one experienced software test engineer.
- Develop, update, and maintain JTS/FAST test cases, test scenarios, test scripts, and test data in accordance with agreed requirements, priorities, technical direction, release planning, and project objectives.
- Perform manual, automated, functional, regression, integration, and system testing to support the continued maintenance, validation, and evolution of the JTS/FAST software baseline.
- Support the full software testing lifecycle of JTS/FAST, including test analysis, test design, test implementation, test execution, defect reporting, retesting, regression testing, and test documentation.
- Develop, update, and maintain automated test scripts and test automation assets to improve test coverage, repeatability, maintainability, and regression testing capability.
- Support integration and verification activities to ensure that developed, updated, or maintained JTS/FAST software components operate correctly within the wider JTS/FAST system and in line with agreed interface, interoperability, and operational requirements.
- Analyse, investigate, document, and report software defects, test failures, anomalies, and quality issues identified during testing, integration, verification, release preparation, or operational support activities.
- Support the verification of defect fixes and software changes by performing retesting, regression testing, and validation against agreed acceptance criteria and requirements.
- Develop, update, and maintain test documentation, including test plans, test cases, test execution reports, defect reports, regression test evidence, automation documentation, and other project deliverables as required.
- Contribute to virtual and in-person meetings, reviews, planning sessions, technical discussions, test coordination activities, and release readiness reviews with NCIA stakeholders and project team members.
- Ensure that all testing activities, test artefacts, automated scripts, defect reports, and associated deliverables comply with applicable NCIA testing standards, quality requirements, configuration management practices, and agreed project procedures.
- Update and expand the produced test assets, automated test scripts, test data, and documentation as necessary to accommodate new, revised, or emerging requirements throughout the duration of the engagement.
- Support the improvement of JTS/FAST software quality, reliability, maintainability, interoperability, and operational readiness by providing structured testing, clear test evidence, and timely feedback to the project team.
The Contractor shall provide the following deliverables classified per service:
- Service: JTS/FAST test case development, maintenance and test baseline management
Output: Updated, maintained, and improved JTS/FAST test cases covering agreed functional, technical, regression, integration and release-related test scenarios. The deliverable includes the development and maintenance of manual and automated test cases required to support JTS/FAST baseline development, defect verification, regression testing, release preparation, User Acceptance Testing, and operational validation activities. Test cases shall be developed or updated in accordance with agreed requirements, user stories, defects, change requests, release priorities, and project planning. The test case baseline shall include, where applicable, test cases for agreed JTS/FAST capabilities such as interface behaviour, configuration changes, interoperability scenarios, and other functionality included in the agreed release scope.
Outcome: JTS/FAST testing remains structured, repeatable, traceable, auditable, and aligned with the agreed requirements, work items, release priorities, and operational use cases. The maintained test case baseline supports consistent verification of JTS/FAST functionality across development, integration, regression, acceptance, and release preparation activities. It also reduces testing ambiguity by ensuring that test cases clearly define the required preconditions, test steps, expected results, pass/fail criteria, assumptions, and dependencies.
Acceptance Criteria A1: Assigned test cases are created, reviewed, updated, or maintained in accordance with agreed requirements, priorities, release scope, or work package timeframe; test cases clearly define preconditions, test steps, expected results, pass/fail criteria, assumptions, and dependencies where applicable; test cases are stored and maintained in the agreed test management, issue tracking, configuration management, or project repository environment; test cases are traceable to relevant requirements, user stories, defects, change requests, release objectives, or operational scenarios where applicable; obsolete, duplicated, incomplete, or no longer applicable test cases are identified and updated or proposed for removal; test cases are reviewed and updated where required following software, configuration, interface, or requirement changes; test cases are suitable for execution in the agreed development, integration, test, release, or acceptance environment; test cases support manual, automated, regression, integration, interface, interoperability, or release-related testing where applicable; test case updates are made available for review within the agreed timeframe; test case limitations, blocked areas, or missing dependencies are documented and communicated when required.
KPIs:
- Test Case Completion Rate (%): Percentage of assigned test cases created or updated within the agreed release or work package timeframe. Target: ≥ 90%.
- Test Case Review Acceptance Rate (%): Percentage of submitted test cases accepted without major rework. Target: ≥ 90%.
Deliverable B1: Updated JTS/FAST automated test suite
Output: Automated tests developed, updated, maintained, refactored, and executed to support repeatable verification of JTS/FAST functionality, regression testing, integration testing, interface testing, deployment verification, non-functional testing where applicable, and release validation. The deliverable includes the development and maintenance of automated test scripts, automated test data, test assertions, execution configurations, and supporting automation assets using the agreed tools, frameworks, repositories, and environments. Automated testing shall support the continued evolution and sustainment of the JTS/FAST software baseline and shall contribute to earlier defect detection, regression stability, and improved release confidence. Where technically applicable, the automated test suite shall be expanded to cover agreed functionality included in JTS/FAST baseline or release scope, including areas such as interface configuration, database replication, and other assigned functional or regression scenarios.
Outcome: Improved software quality and delivery confidence through repeatable automated testing, earlier defect detection, reduced manual testing effort, and strengthened regression coverage. The automated test suite supports more efficient verification of JTS/FAST changes across development, integration, release preparation, and sustainment activities. It also improves the ability to identify regressions and provides reusable test evidence for release readiness and governance decisions.
Acceptance Criteria B1: Automated tests are developed, updated, maintained, or refactored for assigned functionality where technically applicable; automated tests are executable in the agreed development, build, test, integration, or CI/CD environment; automated tests include clear assertions, expected results, and pass/fail logic; automated tests are committed, reviewed, and maintained in the agreed configuration management environment; automated test failures are analysed and either corrected, reported, linked to known defects, or documented for follow-up; automated tests do not introduce unacceptable instability into the automated test suite; automated tests are updated where required following software, interface, configuration, data model, or environment changes; automated tests are aligned with agreed coding, scripting, testing, and configuration management practices; automation limitations, dependencies, unstable tests, or blocked scenarios are documented and communicated where applicable; automated test execution results are made available to support defect analysis, regression testing, and release readiness decisions.
KPIs:
- Automated Test Delivery Rate (%): Percentage of assigned automated test tasks completed within the agreed release or work package timeframe. Target: ≥ 90%.
- Automated Test Execution Success Rate (%): Percentage of automated tests executed successfully in the agreed environment, excluding failures caused by known product defects, unavailable external dependencies, or agreed environmental limitations. Target: ≥ 90%.
Qualifications
Each contractor personnel must meet the following requirements:
- At least 5 years of professional experience in software testing and quality assurance, with a focus on complex software systems, networked applications, or distributed environments.
- Proven ability to communicate effectively in English, both orally and in writing, in a clear, structured, and professional manner.
- Demonstrated experience in working within Agile/Scrum environments, including participation in sprint planning, test planning, sprint execution, defect triage, sprint reviews, and release preparation activities.
- At least 3 years of professional experience in designing, writing, executing, and maintaining manual test cases, including functional, regression, integration, interface, and release-related test scenarios.
- At least 3 years of experience in defect identification, defect reporting, retesting, regression testing, and defect verification using issue tracking and test management tools.
- At least 2 years of experience testing APIs or data exchange interfaces, including verification of request/response behaviour, data processing, data filtering, and error handling.
- At least 2 years of experience working with interoperability testing, including testing of data exchange, message handling, configuration, integration with external systems, or multi-system test environments.
- At least 2 years of professional experience working with test automation frameworks, such as Robot Framework, Gauge, Cucumber, Selenium, Playwright, Cypress, or similar.
- At least 1 year of professional experience with scripting or programming languages used to support test automation, test execution, troubleshooting, or environment configuration, such as Java, Python, Linux Bash, Ansible, or similar.
- At least 1 year of professional experience working with containerized or virtualized test environments, including Docker or equivalent technologies.
- Demonstrated experience using development, testing, and configuration management tools such as Jira, Zephyr, GitLab, CI/CD pipelines, artifact repositories, or equivalent tools.
- Demonstrable experience in preparing and maintaining test documentation, including test plans, test cases, test execution reports, defect reports, verification evidence, regression reports, and release readiness inputs.
- Experience in defining test scenarios, acceptance criteria, validation approaches, or verification evidence for software deliverables.
- Experience working with distributed systems and multi-component architectures, including integration and testing across multiple data sources, services, interfaces, or external systems.
- Familiarity with secure testing practices, controlled test environments, information handling requirements, and working within regulated or accredited environments.
- Possession of relevant technical or testing certifications, including ISTQB, TMap, Microsoft, Red Hat, CompTIA, Cisco, or equivalent certifications.
- The contractor personnel must be a national of a NATO member nation.
Frequently asked questions
Who is hiring for the 2026-0092 Support JTS/FAST Testing (NS) REMOTE - 2 Jul role?
Park Lane Recruitment is hiring for the 2026-0092 Support JTS/FAST Testing (NS) REMOTE - 2 Jul position, a Shazamme client. Apply directly on the employer's career site.
Where is the 2026-0092 Support JTS/FAST Testing (NS) REMOTE - 2 Jul job located?
The 2026-0092 Support JTS/FAST Testing (NS) REMOTE - 2 Jul role with Park Lane Recruitment is based in Off-Site, US. The role is remote-friendly.
Is the 2026-0092 Support JTS/FAST Testing (NS) REMOTE - 2 Jul role remote?
Yes — the 2026-0092 Support JTS/FAST Testing (NS) REMOTE - 2 Jul position at Park Lane Recruitment is remote. Candidates based in US are preferred.
Is the 2026-0092 Support JTS/FAST Testing (NS) REMOTE - 2 Jul role full-time or contract?
This is a full time position at Park Lane Recruitment.
What experience level is the 2026-0092 Support JTS/FAST Testing (NS) REMOTE - 2 Jul role?
The 2026-0092 Support JTS/FAST Testing (NS) REMOTE - 2 Jul position is aimed at mid-level candidates.
How do I apply for the 2026-0092 Support JTS/FAST Testing (NS) REMOTE - 2 Jul role at Park Lane Recruitment?
Apply directly on Park Lane Recruitment's career page via the Apply button on this listing. ZammeJobs links straight through to the employer's ATS — no third-party form, no resume database.