Staff-level contract engineering: web and mobile technologies
Production systems, not prototypes. I take on focused builds, 10–20 hours a week, and ship code your team can own after I'm gone.
The stack I reach for
Workflow principles
Specs before code
A clear spec is what makes agents, and teammates, reliable. I write the intent down first, so the build is verifiable and the AI has something real to work against.
Verification gates
Nothing ships on trust alone. Every change walks through gates that check it against the spec, automated tests, agent and human review, and deploy verification, so speed never has to be taken on faith.
Stakeholder communication
An R&D org is only as good as what the business knows about it. I keep roadmaps tied to business outcomes and report progress in plain language, so leaders always see what is moving, what is stuck and why it matters.
Typical engagements
New service buildout
A greenfield Go service, API, data model, tests, and deploy pipeline, production-ready and documented.
IoT / cloud platform work
Device-to-cloud pipelines on IoT Core, ECS, and EventBridge, built for fleets, not just a demo device.
Architecture rescue
A system that's buckling under growth, I stabilize it, cut the worst coupling, and leave a path forward.
AI-agent tooling integration
Wiring agents into your codebase and pipeline, with the specs, evals, and guardrails to keep them honest.
Taking one new engagement starting Q3 2026, a discovery call now holds the slot.