Software engineer · Product & systems
I’m Tianna “T” McCoy. I build across product design, interfaces, and full-stack software. I built ART and Day Shift as the sole contributor to both projects. I build scaffolding that lets coding agents carry real work across sessions while the human stays in charge of what ships.
Interested in product/full-stack, frontend/UI, hands-on technical leadership, agentic developer tooling, and inference infrastructure and automation.
Generally open to roles and contracts. Usually in the U.S. Pacific Northwest. Remote, with in-person visits arranged in advance.
Considering a role or contract? Read the hiring overviewProtect futures. Build with care.
01 / Selected work
Two projects. A shared commitment to
clearer, more resilient systems.
Sole contributor
Community coordination, built around local control.
A community coordination suite in development, designed to connect reporting, regional dispatch, and training around regional control of sensitive information.
Read case study
Sole contributor
A clearer handoff between people and coding agents.
Agentic developer tooling that keeps specifications, scope, and review evidence beside the code so coding agents can carry work across sessions while the human controls acceptance.
Read case study02 / About me
My path runs from the Marine Corps and precision industrial mechanics to software engineering and mutual aid.
That background shapes how I build: understand the whole system, respect the people operating it, and think about what happens when conditions change.
I work at the intersection of interfaces, infrastructure, and community care. ART brings that thinking to community coordination. Day Shift brings it to planning and reviewing software work with coding agents.
Accessibility is part of that responsibility. I aim for clear language, visible state, and workflows that help people find their place again.
I’m interested in growing into hardware and projects that connect software with physical systems, drawing on my background in precision industrial mechanics.
Professional history & résumé03 / How I build
Understand who needs the tool, what gets in their way, and what happens when their attention is interrupted.
Keep roles, data ownership, and next steps clear. People should understand what a system is doing and what remains their decision.
Treat unreliable connections, limited resources, and recovery from failure as part of the design brief.
TypeScript / React / Next.js / Supabase / PostgreSQL / Node.js / Codex / GitHub Copilot