About

Engineering shaped by operational reality

Software earns trust when the person responsible for the outcome can understand it, correct it, and see its boundaries.

My product lens comes from work across sales, customer service, financial transactions, inventory, and small-business operations. Those environments make one thing clear: an automation is only useful when the person responsible for the outcome can understand it, correct it, and trust its boundaries.

I build focused software around that principle—Python pipelines for messy data, browser tools for repetitive research and form work, and internal applications that turn uncertainty into a review queue instead of hiding it.

AI is an optional layer, not the foundation. When a deterministic rule can handle the task, I prefer the rule. When AI can help draft or summarize, I keep the output editable, disclose what data may leave the system, and preserve human approval.

I am Texas-based and open to remote full-time, contract, and freelance opportunities where operational judgment and practical software belong together.

How I work with AI

I direct the work, verify factual claims, test behavior, debug failures, and own the result. Generated output is a draft to inspect—not evidence that a system works.

See the standard

Every claim should point to evidence.

Contact Kori