The engineer you hire is the engineer who ships.
Steven Day Dayton, Ohio Remote
I have built software for twenty-five years, starting in 2001, and I still ship production code every day. I work where product decisions, architecture, delivery and operation belong close together. On multi-year platform engagements, I have been the sole engineer. Two of those engagements have run about seven years each: one from December 2018 to its handover in July 2025, the other from 2019 and still going. Mobile, web and operational systems all ship from the same desk.
What I actually build
Three lanes, and they are not separate careers. The same person who writes the offline sync also writes the API it syncs against and answers for it in production.
Mobile in production
One Flutter and Dart codebase serves iOS and Android on Supabase Postgres. It is live in the App Store and Google Play. Riverpod, go_router and freezed structure it. A local Drift database handles offline-first work, conflict resolution and reconciliation. Swift and Kotlin modules use platform channels for video encoding and camera stabilization. I own the model, API, submissions, releases and operation. Sentry watches production.
Web without ceremony
I build with React and Next.js, and use Astro when a smaller surface is the right answer. My WordPress work includes custom themes and plugins written from scratch, plus malware remediation on compromised production sites.
Operations need software
I built a field platform for an emergency response company. Its iOS and Android apps wrap the web application and handle dispatch, GPS and scene capture. It replaced paper forms and a Microsoft Access database, and was in the App Store from 2020 until the 2025 handover. Another platform runs on iPads at a heavy-equipment company's Texas office and yard, covering parts, purchasing, rentals, transport and service. A July 2026 read of the system found its daily use had narrowed to essentially one parts manager, and its service requests could not be assigned to a crew until I fixed a defect in my build that September.
I do not manage people. I set the standard and own what ships.
I have never managed people, and I do not want to. My job is to make the technical calls, turn them into working software and stay accountable after release. I have been product owner and project manager for a six-person outsourced build, writing and prioritizing the Jira backlog and holding the standing vendor syncs. Before that, I spent twelve years running web and digital operations inside a regional academic health system, working directly with the VP of Information Technology and the Director of Marketing.
I know how to coordinate work. I want my hands on the product.
AI architecture covers how the agent fleet, the gates and the observability actually fit together.
Work covers the engagements themselves, including the one that did not go to plan, and How we work sets out the terms we now give agencies.
Insights holds the long-form papers if you want the full version rather than the summary.
The standard runs before the code ships.
Agents write most of the code. Before they write anything, they read twenty-two standards documents and a project constitution. Roughly seventy numbered pre-commit gates decide when the work is done, many of them tests of the other gates, and a gate that skips when it cannot check counts as a failure.
One of those gates is a static analyzer I built and published on PyPI. Every agent session reports to a self-hosted OpenTelemetry collector, and dozens of command-line harnesses let an agent operate the real services the work depends on. A published paper documents the system in full. Quality is checked by machinery rather than remembered in a review.
If the work needs an owner, we should talk.
I am open to staff-level mobile work, senior full-stack roles, contract engagements and fractional product engineering. The title matters less than the shape of the responsibility. If you need someone who can make the calls, write the code and remain answerable for production, send me the role, the problem and what already exists.