Hiring overview / Roles & contracts
About 3 minutesI’m Tianna “T” McCoy, a software engineer and systems builder. I connect user experience, application architecture, and implementation to turn complex problems into clear, usable software. I built ART and Day Shift myself as the sole contributor to both projects. With Day Shift, I build the scaffolding for coding agents to carry work across sessions while the human stays in charge of what ships.
I can connect the product conversation to the engineering decisions and stay involved through the build. My focus is software people can understand, operate, and carry forward.
Opportunity fit
Hardware direction. I’m interested in growing into hardware and projects that connect software with physical systems, drawing on my background in precision industrial mechanics.
Since leaving Atlas in October 2026, I’ve been researching how to make local AI inference infrastructure viable for small and medium-sized businesses. TNSDS Stations explores repurposing older laptops as local servers, with attention to deployment, model quantization, and serving multiple users within hardware constraints. This work is currently in research and planning.
For founders
I can help turn an ambiguous problem into a focused product, connecting what people need with what the team can deliver.
For CTOs
I bring hands-on engineering with attention to data boundaries, operational constraints, and how people recover when something fails.
Sole contributor
An ecosystem in development for reporting, regional dispatch, and training. The work connects product workflows with an architecture designed around regional data ownership.
Read the case studySole contributor
A publicly released browser GUI and CLI for carrying coding-agent work across sessions, used with Codex and GitHub Copilot. I designed the Markdown human-agent contract, JSON workflow guidance, and human approval boundaries. As of October 2026, its development records document 119 completed phases covering 1,162 tasks with implementation summaries.
Read the case studyStart with the user, the constraint, and what a useful result would look like.
Agree on scope and system boundaries, then build a focused piece that can be reviewed.
Connect decisions, code, and validation so the next step is understandable.
As an Infrastructure Automation Engineer at Atlas Networks, I used Day Shift to build the foundation of a network monitoring application, deploy development and staging environments on a virtual machine, and implement ping-based device health checks and history graphs. The application was still in development when my role ended.
My background also includes independent product development and community mutual aid, progression from Software Engineer to Software Engineer III at HOMEE, technical advising and remote engineering tutoring at Kenzie Academy, supervising millwright work, and Marine Corps service.
Professional history & résuméRemote work, planned travel, trusted ownership, and clear expectations for compensation and communication.
What I look for in a role or contractA useful first conversation
Share the role or project, what you’d want me to own, the budget range, expected time commitment, required time-zone overlap, and target start date. That gives us a useful starting point for deciding whether there’s a fit.