AssuranceRemoteRef: DL-2026-002
Assurance Engineer, Formal Verification
Turn a client's operating constraints into machine-checkable properties, and prove them against agent behaviour before release, not after an incident.
What you'd do
- Translate a client's operating constraints (what an agent must never do, what authority it may never assume on its own) into formal, machine-checkable specifications.
- Build and maintain the verification tooling that checks agent behaviour against those specifications automatically, in CI, on every change, not as a one-time audit.
- Own the evidence package that lets a client's compliance, safety, or audit team sign off on a deployment: what was checked, how, and what the result was.
- Push back on designs that cannot be verified, early enough that it is a design change and not a production rewrite six weeks later.
- Work with the interpretability and red-team functions so a specification reflects how the system actually fails, not just how it is supposed to work.
What we're looking for
- Experience with formal methods (model checking, theorem proving, or runtime verification) applied to real systems in production, not only coursework or toy examples.
- Comfortable working backward from a regulatory or safety requirement, often written by a lawyer, to a property a machine can actually check.
- Solid software engineering fundamentals: this tooling has to run in CI, reliably, on someone else's schedule, not just in a notebook you maintain.
- Able to say plainly when something cannot be verified with the time and access available, rather than producing a specification that looks rigorous and is not.
- Background in safety-critical or regulated industries (finance, healthcare, aerospace, energy) is a plus, particularly if you have sat across from an auditor.
Ready to apply?
Fill in the form on the next page, CV included; one submission sends it straight to us.