We are looking for someone to work out how quality engineering should work when a team delivers this fast, and then build it.
We make mission-critical software for unmanned systems, used in maritime search and rescue and in defence. Operators depend on it under pressure, often at the edge of a link. When it is wrong, it is wrong in front of someone who needed it to be right.
We also move quickly, and AI tooling is deeply embedded in how our engineers work. That combination is the problem this role exists to solve: verification has to scale at the same rate as delivery, and it cannot scale by adding reviewers. It has to be engineered, and most of that engineering has not been done yet, here or anywhere else.
So this is not a role with a playbook. We are less interested in how many years of a particular tool you have than in how you think about problems like this one and how you go about solving them.
What You’ll Do:
Work out what should be verified, and how. Start by understanding the platform properly: its workflows, its real-time behaviour, its failure modes. Then decide where the risk actually is, which is rarely where the existing tests are.
Test the critical things by hand. Decide what must have human eyes on it (safety, mission-critical paths, first-of-a-kind flows) and test it well, including exploratory testing nobody scripted.
Write scenario packs a persona-focused QA agent can run. Anchor each scenario in a real operator persona, make it specific en