Cover letter
Seattle, Washingtonzaindharper@gmail.comLinkedInGitHub
Dear reviewer,
I am applying through the lane that matches your posting rather than asking you to interpret one oversized portfolio. My current technical targets are technical support, developer operations, QA, evaluation tooling, and Python developer tools. I also maintain a separate field campaign for public operations, grounds, facilities, ports, utilities, parks, fire-support, and physical-work routes.
The technical material leads with work accepted by other maintainers: Free Law Project, Hebbian Robotics, Voxwire, DeepEval, TOMLKit, and Datasette. After that, I point to owned systems such as Flywheel, Terminal State Fixtures, and BuildLang as project evidence, not as invented employment history.
My useful pattern is direct: reproduce the problem, write the smallest durable fix, document the boundary, and leave behind a check that someone else can run. That pattern applies to technical support, evaluation tooling, field operations, and public-facing service.
I am strongest in environments where reliability matters more than title shape. I can take ambiguous failures, build a small reproducible case, explain the risk in plain language, and keep the work moving without hiding uncertainty. I am also comfortable with hands-on work, outdoor conditions, public contact, and shift-based operations when the role is practical rather than purely desk-based.
The public materials are intentionally conservative. They separate accepted external work from open or closed-without-merge work, keep private details out of the website, and route sensitive security material through approved private channels. If a posting has a hard requirement, I prefer to answer it directly, name the evidence, and identify any gap before anyone wastes time.
Sincerely,
Zain Dana Harper
zaindharper@gmail.com
Updated 2026-08-28. Phone is omitted from public artifacts. Exact work-history months remain unknown in the public authority.