For recruiters and hiring managers hiring a AI Platform & Operations Analyst (release evidence, reliability metrics).
Role fit, with proof you can run
AI Platform & Operations Analyst (release evidence, reliability metrics)
Mid-level and senior IC roles. W2 full-time or contract-to-hire, remote US (Arizona).
I read release evidence, track reliability signals and report when a deploy was blocked and why. The same public proofs back the engineer lane.
release evidencereliability signalsblocked or passedreportreceipt
Requirements and proof
| Requirement | Proof |
|---|---|
| Read release-gate results and report which checks blocked a deploy | Release-gate case study |
| Track the reliability signals that stop a regression before release | Release-gate case study |
| Write up an incident with its root cause and the durable fix | Deterministic gate battery case study |
| Keep a reproducible record of what was deployed and verified | Artifact-lineage case study |
| Report on automated checks that replace manual operational work | Agentic fleet verification case study |
What could go wrong hiring me
Most proof here is self-built, not operations reporting on a live, always-on system.
Counter: COBOL-to-Rust migration case study
On-call and incident history here is not documented with employer pager records.
Reliability and gate figures are self-reported, not published by a third-party status-page provider.
Counter: Public adversarial-gate repo with CI
Verify in 60 seconds
- Clone the public adversarial-gate repo and check the CI-green test count against its README, https://github.com/mpuodziukas-labs/llm-adversarial-gate
- Open the release-gate case study and read what one failing assertion does to a merge, /cases/eval-release-gate