Austin is the capital of Texas and is known for semiconductors and hardware, enterprise software, a dense startup scene, state government and a large public university. This page says what a company in that mix can expect from an AI engineer who is not in the city, and where the limits are.
How the work reaches Austin
Everything I build lives in your repositories and your cloud accounts, so nothing depends on where I sit. The work is reviewed on the code itself and in writing, with a call when a decision needs one. Monterrey keeps the same hour all year. Austin is on that hour from early November to mid March and one hour ahead for the rest of the year. A question asked in the morning is answered the same morning.
What companies in Austin tend to ask for
Software companies and startups usually arrive with an agent that works in a demo and misbehaves with real users. The work is to describe the process, connect the agent to the data it needs, and write the tests that decide whether the next version ships. That is the center of what I do, and the pages on AI agent development and LLM evaluation describe it.
Hardware and semiconductor companies hold their knowledge in long, controlled documents: specifications, process notes, supplier records. No case study on this site comes from a semiconductor company. What transfers is the method for answering from a controlled corpus and for giving an agent narrow, logged access to a system of record, which I describe under RAG and data platforms and MCP servers and integrations.
Agencies and the companies that sell to them care about who did what and why. No case study here comes from government either. The guide on agent auditability states what a record of an agent's action has to contain, and it is the standard I build to.
What I can show
Three pieces of work are public and specific. The first is the set of evaluation gates for a multi-agent system that serves a higher-education group with 700,000+ students, written up as a case study. The second is an MCP gateway on Cloud Run that puts many tools behind one governed entry. The third is open source: an Airtable MCP server that other developers use.
I do not list clients by city, and this page does not claim one in Austin. What it claims is narrower: the work above exists, it can be inspected, and it was done remotely.
How an engagement starts
Send the role or the problem by email. I read the process before I propose anything, and I answer in writing with three things: what I would build first, what access I would need, and what I would not promise. From there the work is a contract under my name or a full-time senior role, whichever your company prefers.
What this page does not offer
A local presence. If the work needs someone in your building, I am the wrong person, and it is better to know that now. If it needs someone who will own a system from the first description of the process to the tests that guard it, the distance does not change the result.