Freelance and contract
This is the default path for California clinics, Florida home-services operators, Bay Area SaaS teams, and Miami hospitality groups that need a system shipped—not a staff seat filled. You keep the numbers, the cloud, and the data. I design, build, eval, and hand off.
- Custom AI call agents (inbound/outbound, bilingual when scoped)
- Custom AI chatbots with RAG and booking actions
- Production RAG agents with citations and ACLs
- Workflow automation into CRM, PMS, or dispatch
- Architecture reviews when a local agency install failed
Full-time hiring
I am open to senior applied AI / LLM systems roles on US teams. Remote-first is the fit. I will discuss hybrid or relocation when the product, team, and immigration path are real—not when a JD says “AI magician with 15 years of GPT-5.”
- Title band: Senior AI Engineer, Applied AI, LLM / RAG platform
- Markets: California, Florida, and other US remote-friendly orgs
- Stack: Python, LangGraph/LlamaIndex, voice/telephony, Next.js
- What to send: JD, comp band, visa/remote policy, team size
Understanding how US companies hire this work
Search demand splits in two. Founders type “custom AI call agents California” or “RAG chatbot Miami” because they need a builder. Recruiters type “hire senior AI engineer remote” because they need a seat. This page exists so both intents land on one honest entity: a named engineer, production systems, California and Florida as served markets, freelance and full-time both open.
The engineering framework I actually ship
Agents fail when they cannot see the system of record, when retrieval has no evals, or when voice has no overflow. Freelance scopes start with channel, corpus, tools, and audit trail. Full-time conversations start with whether your team wants a demo theater or a production owner. I have shipped clinical-scale RAG, ops automation, and telephony-adjacent agents—those are the proof points, not a list of model logos.
Checklist before you reach out
- 1. Decide freelance project vs full-time seat. Do not mix them in one email without saying so.
- 2. Name the state and timezone you operate in (California PT / Florida ET preferred overlap).
- 3. Link the service page that matches: call agents, chatbots, RAG, or workflow automation.
- 4. If full-time: include remote policy and whether you sponsor or already expect Pakistan-based remote.