You reproduce before you conclude
A number that cannot be run twice is not a finding. We would rather ship one defensible result than four suggestive ones.
The work is unglamorous and consequential: benchmark fleets, failure taxonomies, action surfaces, and regulated journeys that have to hold up for both an agent and the person who sent it. Small team, long horizon.
Write to team@webzero.ai with the role in the subject line, plus something you built and the part of it you would do differently now. No cover letter.
Roles are filled as they close, not batched. Nothing here fits: write anyway and say what you would own.
Most of what we do is measured, so most of what we hire for is the habit of measuring. Domain experience in banking or insurance helps and is not required. The instinct to reproduce a result before believing it is.
A number that cannot be run twice is not a finding. We would rather ship one defensible result than four suggestive ones.
Most of our output is read by risk, engineering and marketing at once. Clear prose is part of the engineering, not a wrapper on it.
Regulated change processes, permitted environments and audit trails are the terrain, not friction to complain about.
The last fifth of an agent journey, error recovery, receipts and edge states, is where readiness is actually won or lost.
One email, the role in the subject, and one thing you built with the part you would change. We reply to every application.