Availability

I am a salaried full-time Lead Engineer at BI Worldwide. Here’s what I am open to outside that role, and the conditions that make a fit.

Hiring inquiries

Open to senior to staff individual-contributor roles in Applied AI Engineering, Forward Deployed Engineering, Solutions Architecture, and AI Evangelism. Preferred locations: Minneapolis/St. Paul, San Francisco Bay Area, New York City, Seattle, or anywhere in Canada. Other areas may be possible given an ideal role fit.

The strongest fitting signal, as I see it, is whether your team’s runtime concerns map to the four pillars in my Reliability Layer manifesto: verification, calibration, adversarial robustness, and recovery. A team working that gap gets someone who has built verification infrastructure under adversarial conditions and can translate it across product, engineering, and design. For relevant evidence, see work.

A more concrete fit signal: your team is deploying AI in production and has started accumulating incidents or quality drift that benchmark eval did not predict. If your runtime concerns are verification, calibration, adversarial robustness, or recovery, and you have a senior-IC role open, we should talk.

For hiring inquiries, email shawn@nettertech.com with the subject hiring inquiry. Include the role link, level or compensation band, and a sentence on team context.

Verification: LinkedIn · GitHub · AICred: Rank 1, 10.0/10 (2026-07-21) · References available on request.

Contract Reliability reviews

I take on one to three Reliability Layer engagements per quarter. Scope: an outside read on a production AI deployment’s verification, calibration, adversarial robustness, and recovery posture. Deliverable: a written assessment with calibrated findings and a prioritized remediation list. Engagement formats: a one-week onsite intensive (eval-harness bootstrap, agent reliability audit, or calibrated-uncertainty workshop), or a two-to-four-week project-scoped review. Pricing on inquiry; senior-IC consulting rates apply.

Accessibility sits inside that scope rather than beside it. Where a deployment’s interface is the thing failing its users, the review treats that as a reliability finding on the same four concerns, for the reasons set out in Accessibility is a reliability concern. I do not sell standalone conformance audits.

Adjacent surface: short-form expert consultations via established expert networks (AlphaSights, Third Bridge, EveryExpert). Different product, different time profile. Route those engagements through the network rather than this page.

Not a fit: general AI consulting, prompt-engineering coaching, training-data work, or engagements that require exclusive availability for a multi-month period.

For contract inquiries, email shawn@nettertech.com with the subject reliability review.

What I am not available for

• Cold outreach for roles outside the list above
• Recruiter outreach without a specific role link
• General consulting outside the Reliability scope

Routing inquiries with the subject conventions above is the fastest path to a real reply.

Methodological anchors

The four-concern taxonomy in the Reliability Layer manifesto is the public-facing frame. Underneath, the work draws on established disciplines outside the typical AI-tooling stack. For prospects who want the depth read before a discovery call, the anchor list is below.