For recruiters and hiring managers
Michael Puodziukas, AI Evaluation Engineer, Remote (US), based in Arizona
Reach me about a remote W2 role.
Open to mid-level and senior IC roles, W2 full-time or contract-to-hire, remote (US), based in Arizona. U.S.-authorized, no sponsorship.
The button opens an email to me. I reply by email, and a technical screen follows if the role fits.

Paste the job description
The bot scores the posting against each role page on this site and returns the one to read, the requirements it matched, and the proof each one links to. It never scores you; it routes you.
Runs in your browser. Nothing is sent anywhere.
Titles I fit
- AI Evaluation Engineer
- AI Evaluation Analyst
- AI Engineer (eval, guardrails, release side)
Also open to
- Applied AI Engineer
- AI Governance / GRC Engineer
- AI Governance / GRC Analyst
- Responsible AI Specialist (eval or red-team side)
- AI Platform Engineer
- AI Platform / Operations Analyst
- QA / Test Automation Engineer
- MLOps / LLM Ops
- Solutions / Forward Deployed / Implementation Engineer
- AI Security Engineer (LLM red team, prompt-injection defense)
- AIOps Engineer (LLM monitoring, release gates)
Recruiters and agencies
W2 full-time or contract-to-hire. Remote (US), based in Arizona. Available now; start date set at offer. Submission details for agencies ->
Role fit
The top lane is open. The rest expand, and each links to its proof.
AI Evaluation Engineer
Evaluation systems that run the tests and check that each result is correct.
Proof for this role ->Responsible AI Specialist (eval or red-team side)
Automated attacks on AI systems, with a record of which ones get through.
Proof for this role ->AI Governance / GRC Engineer
I write AI governance policy as a build that fails when a control is missing, and the build generates the evidence a reviewer can re-run.
Proof for this role ->AI Platform Engineer
Release gates that block an AI deploy when its safety checks fail.
Proof for this role ->AI Engineer (eval, guardrails, release side)
AI features with the tests and release gates written first, so anyone can re-run the results.
Proof for this role ->QA / Test Automation Engineer
I write automated tests, then prove they bite: a planted failure must turn each gate red. Each public repo cited on /proof ships a fixed corpus, an evaluator and a pytest suite.
Proof for this role ->AI Evaluation Analyst
I read evaluation results, check each verdict against its evidence, and report what passed, what failed and why. The same public proofs back the engineer lane.
Proof for this role ->AI Governance / GRC Analyst
I map AI controls to NIST AI RMF, EU AI Act and ISO/IEC 42001 requirements, read the evidence behind each control and track its status. The same public proofs back the engineer lane.
Proof for this role ->AI Platform / Operations Analyst
I read release evidence, track reliability signals and report when a deploy was blocked and why. The same public proofs back the engineer lane.
Proof for this role ->Solutions / Forward Deployed / Implementation Engineer
Independent build work, shown as runnable public artifacts, demo-ready, with the written scope first. No prior employer or buyer is claimed.
Proof for this role ->How I work on a team
- I work from a written scope and ask questions early.
- Code lands in your repo. Decisions arrive as written diffs with replay commands your team can run.
- Every public-repo result is reproducible. Clone it and check.
Interview logistics
I work async first: written questions and replay exercises. I take live calls once a role is open. The core claims clone and run from public repos, and I walk through them in a technical screen.
Contact
Send the role, the team focus and the timeline.
One paragraph. I reply by email.
The more specific the note, the more useful the reply.
Objections, answered first
- AI Platform Engineer: No public pager rotation or SLO history. I would measure uptime and incident load first.
- QA / Test Automation Engineer: No public UI, browser or REST API test suite, and no TestRail work on record. I would show gate testing first; there is no public API test suite yet.
- Applied AI Engineer: No public cloud GPU or Kubernetes work. My serving record is a home-lab cluster. I would move one serving path onto your stack and measure it against the home-lab baseline.
- Solutions / Forward Deployed / Implementation Engineer: No public customer deployment or on-site work. A clone-and-run demo scoped to your problem.
- AI Evaluation Analyst: No public dashboard used by a business team. My reporting samples are case studies. I would build a report on your data and agree its fields with your team.
- AI Governance / GRC Analyst: No third-party certification and no work inside a regulated organization. I would map one of your controls to its evidence.
- AI Platform / Operations Analyst: No public pager rotation or SLO history. Reliability figures are self-reported. I would pull reliability figures from your own incident records.
Submit in sixty seconds
- Name
- Michael Puodziukas
- Titles
- AI Evaluation Engineer, AI Evaluation Analyst, AI Engineer (eval, guardrails, release side)
- Level
- Mid-level and senior IC roles. W2 full-time or contract-to-hire, Remote (US), based in Arizona.
- Location
- Remote (US), based in Arizona
- Employment type
- W2 full-time or contract-to-hire
- Work authorization
- U.S.-authorized, no sponsorship
- Availability
- Available now; start date set at offer.
- What he does
- Tests that catch AI model failures before release, published so anyone can run them.
- Proof
- https://github.com/mpuodziukas-labs/cobol-pic-probe
- Contact
- michael@puodziukas.dev
- Résumé
- PDF Plain text
Copy and paste
Name: Michael Puodziukas Titles: AI Evaluation Engineer, AI Evaluation Analyst, AI Engineer (eval, guardrails, release side) Level: Mid-level and senior IC roles. W2 full-time or contract-to-hire, Remote (US), based in Arizona. Location: Remote (US), based in Arizona Employment type: W2 full-time or contract-to-hire Work authorization: U.S.-authorized, no sponsorship Availability: Available now; start date set at offer. What he does: Tests that catch AI model failures before release, published so anyone can run them. Proof: https://github.com/mpuodziukas-labs/cobol-pic-probe Contact: michael@puodziukas.dev Résumé: /resume.pdf and /resume.txt