Career · start here HireResumePortfolioFull CV

Zain Dana Harper

Systems Engineer | AI Evaluation, Developer Tools, and Technical Operations

Seattle, Washington Onsite, hybrid, remote, contract, or project zaindharper@gmail.com github.com/HarperZ9

Choose the relevant work

I build evaluation environments and developer tools, support technical users, write the operating record, and run work where changing conditions have real consequences.

31 engineering pull requests merged upstream 324 exhaustive terminal-state cases 936,657 product downloads as of 2026-08-14

Three hiring paths

I am open to physical and non-physical work. The strongest route is engineering, but the field and operations history is real and useful.

Route 01

Engineering and evaluation

AI evaluation, agent infrastructure, developer tools, systems programming, CI, compilers, and upstream engineering. Best fit for teams that need someone who can build a fixture, reproduce the failure, write the record, and ship the patch.

Route 02

Technical operations

This route covers troubleshooting, documentation, issue triage, release work, implementation support, customer communication, and developer operations. Best fit for teams that need careful technical translation under deadline pressure.

Route 03

Public service, safety, and field operations

This route covers parks, public works, utilities, facilities, arboriculture, grounds work, safety judgment, and public-facing service. Best fit for physical work, public-contact work, records, coordination, and field operations where judgment matters.

Five things to open

  1. Flywheel. Python and Flutter infrastructure for model routing, verification, gated agent actions, and offline-recheckable tool-call receipts.
  2. Terminal State Fixtures. Exhaustive, deterministic evaluation environments that score terminal state instead of transcript claims.
  3. BuildLang. A systems-language toolchain with typed capability effects, C FFI, native output, shader backends, a bundled CLI and LSP, and re-checkable receipts.
  4. Upstream work. The merged changes, open work, and work closed without merge stay together in one public ledger.
  5. Full portfolio. Product shipping, documentation, research, graphics, field operations, and explicit public-boundary notes.

More documents

Cover letter, dossier, and specialized resumes stay available for roles that ask for a broader packet.

Start a conversation

Send the role, problem, or project to zaindharper@gmail.com. I will respond with the most relevant evidence and a direct account of fit, gaps, and next steps.

Current public evidence as of 2026-08-25. Upstream counts are recorded in the public open-source census. Product-download figures are a dated operator reading from NexusMods. Employment and field-history statements are applicant-reported.