Method

What Vestmark's CTO + Chief AI Officer actually needs — and the proof I've already shipped

A CTO + Chief AI Officer role at Vestmark maps cleanly onto evaluation work I've already published. This page links the role's core skills to runnable, public harnesses — starting with Can you trust the model that grades your content? Measuring when an AI judge waves through broken work.

Status
Job-targeted showcase · maps a live role to real, runnable proof · auto-generated, 24h-veto reviewed

A CTO + Chief AI Officer role at Vestmark is asking for someone who can measure whether an AI system is actually doing what it claims, not just whether it runs. That is the work I have been building in public. Here is the role’s core, mapped to the harnesses I have already shipped and can run on a call.

The role, mapped to real proof

  • A runnable, public proof of the core method. Can you trust the model that grades your content? Measuring when an AI judge waves through broken work. Teams now use an LLM to QC the content another LLM wrote. The risk is that the judge passes work that’s actually broken, and it gets more lenient when it grades its own output. So I built a fully-automated instrument that measures exactly that. It breaks items in known ways, with no model anywhere near the labels, then asks four different vendors’ models to grade them blind. A single judge waved through 5 percent of the items I broke on purpose, and the rate ran higher when a model judged its own work. Making four independent vendors agree before a pass drove the miss rate to zero.
  • A runnable, public proof of the core method. Measuring feedback integrity: a blind-solver that catches AI explanations leaking the answer. When an AI writes explanatory feedback for a wrong answer, it tends to fail in three ways that are easy to miss. It teaches the right answer instead of diagnosing the error, it invents a concept not present in the original content, or it attaches to the wrong option entirely. A top-to-bottom read misses all three. So I built a measurement instrument that catches them, with a blind-solver at the center that turns ‘is this feedback bad?’ into ‘can a reader exploit it?’ Then I gave it a golden set and a graduation test, so the human running it can measure when it’s safe to stop checking by hand.
  • A runnable, public proof of the core method. Calibrating an eval-design gate against 130 candidates. Building a self-hardening gate to separate load-bearing eval designs from decorative ones, and the surprise that the gate out-discriminated the thing generating the candidates.

Every one of these is a runnable harness with saved outputs on a public substrate (synthetic, NAEP/STAAR/OER-style, or fictional content). No proprietary data, no hand-waving. If the role is about trusting what a model tells you, the proof is already on the page.