AI Engineer — production RAG and agent systems, and the infrastructure they run on.
Most engineers can call an LLM API. Fewer can deploy, observe, secure, and evaluate what they ship. I build production RAG and agent systems — grounding, evaluation, and observability first — and the infrastructure they run on.
Open to remote AI Engineer, AI Platform, and LLMOps roles.
Agentic document Q&A that cites its sources — hybrid RAG with
inline [n] citations, database-enforced multi-tenancy,
an eval floor in CI, and honest abstention instead of hallucination.
The repo that ships this site: a hardened $6/mo VPS, GitOps plan/apply pipeline with a production review gate, and every piece of the infrastructure in code. You're looking at the artifact.
Prometheus + Grafana + a custom Python exporter watching live game servers 24/7 — Discord pushes for events that need a human, Prometheus pulls for trends.
Layered DDoS defense, live player telemetry, and Discord ops for the Halo CE servers I host — five containers on one VPS, running around the clock.
One CLI — up | harden | deploy | status | destroy —
owning the full lifecycle of a small cloud footprint across two
providers, with Terraform underneath and Ansible hardening.
This site again, deployed a second way: single-node k3s, a Helm chart, cert-manager TLS — rebuilt from nothing in ~90 seconds.
This site is the artifact, not the brochure — the repo that builds it is on the work list above.
I'm a self-taught engineer who builds production LLM systems — retrieval, agents, structured extraction — and the infrastructure they run on. The part I care about most is whether the thing actually works outside the demo: knowing when an answer is grounded versus guessed, catching the regressions before users do, watching how the whole thing degrades when something upstream breaks.
The infra work is the other half. I provision, harden, and operate real services in code — VPS, DNS, TLS, monitoring — and try to write down what I chose, what I weighed, and the parts I'd do differently next time. Most of what's on this site I run on my own boxes.
Bilingual (EN/ES), US/Mexican dual citizen, based in California on Pacific Time. I work remote, async-first. I move quickly when something clicks and I'd rather ship a small thing that works than plan a big thing that doesn't.
Let's talk.
julivnexe@gmail.comCalifornia · Pacific Time · Open to remote, anywhere