Skip to content

AI Engineer · Dallas, TX

I build AI systems that hold up in production.

Four of mine run at FieldPulse right now — drafting support email, handling payment notices, answering questions in Slack, and keeping customers updated on their tickets.

What I bring

Four things that keep a system alive

Getting a model to do something impressive takes an afternoon. These decide whether it is still trusted six months later.

Evals, not vibes

Every system I ship has a way of telling me when it gets worse. Regression suites built from cases that actually happened, and gates I deliberately try to break — a check that has never failed has not been tested.

BraintrustGolden fixturesLLM-as-judge
ProofSupport inbox agent

Fail closed, not open

When money is involved, the question is not whether the model is good — it is what happens when it is wrong. On the payments agent the model never writes the message: it picks a template and fills in the blanks.

GuardrailsPII guardsTemplate-first
ProofCustomer status pages

People can always stop it

Every draft lands somewhere a person can read it, change it, or kill it before a customer does. On the support agent, auto-send stayed off for the entire first rollout — on purpose. Automation earns trust by being interruptible.

Review dashboardsEscalationSlack
ProofInternal knowledge assistant

The integration nobody demos

Salesforce, four internal services, three different auth schemes, and an API budget with no room to spare. Plus orchestration that fails softly, so a customer is never stranded halfway through setting up their account.

SalesforceNext.jsSupabase
ProofOnboarding platform
4
Systems in production
1,000+
Questions answered
180+
Automated tests
4
Services integrated

Got something that has to work?

If you are putting an AI system in front of real users, that is the work I do. Tell me what you are building and where you think it breaks.