Test Engineer (Integrated Command and Control Systems) for NATO with security clearance
WLG The Hague, South Holland, Netherlands
Financial Services · 2-10 employees
About the role
The test engineer will own the quality of integrated command and control software by creating structured test plans and scenarios. They will manage the full testing lifecycle, including manual and automated testing, API validation, and issue tracking in JIRA.
What they look for
Requirements
Candidates must have hands-on experience with SQL, API testing, and issue tracking tools like JIRA. Proficiency in Linux and a strong background in command and control or air operations environments are highly valued.
Full description
The bugs that matter here are the ones nobody thought to look for.
A team in The Hague is delivering gap capability work packages on integrated command andcontrol software, and it needs a test engineer who can own the quality of what ships. On-site inThe Hague, Netherlands.
What you will be doing
- Analysing requirements and writing structured test plans, test cases and scenarios fromthem
- Deciding what deserves a manual test and what deserves an automated one, across functional,regression, performance and security testing
- Querying databases directly in SQL to prove what the application is really doing
- Testing APIs with Postman, SOAPUI or the equivalent
- Logging, managing and chasing issues through JIRA
- Hunting the edge cases — the meticulous, logical part of the job that separates a good testengineer from a checklist
What you will need
- Real experience turning requirements into structured test artefacts, not just executingsomeone else's script
- SQL you can write yourself, and hands-on API testing
- JIRA or a comparable issue tracker as daily habit
- User-level comfort on Linux
- An eye for detail and a problem-solving mindset
Nice to have
- Experience with test automation tooling such as Selenium or Playwright
- Background in command and control or air operations planning environments
Why this one is worth a look
Testing here is not a rubber stamp at the end of a sprint — the software is operationallysignificant, so the quality bar is real and your findings actually change what ships. Normaloffice environment, an established team, and work that is visibly worth doing.
