Artem T.

I'm an AI engineer and architect on US Eastern Time. I build AI agents and chatbots on the Claude and OpenAI APIs, the retrieval layer that feeds them your own data, and the multi-tenant platforms they live inside. One of mine is an in-chat shopping agent serving 1,800+ merchant stores today. What I do: • AI agents. Tool-calling agents with a hard cap of eight steps per turn and a guard so a retried call never applies the same cart change twice. The shopping agent above runs on 13 tools. Behind it a custom MCP (Model Context Protocol) server with about 45 tools, enough for an agent to open an account, set up a shop, import a catalog and take payment. • RAG and assistants. The assistant searches your catalog, documents or knowledge base before it answers, so what it says traces back to a record you can open. Voice messages come in as text, and it replies in whichever language the customer wrote in. • Multi-tenant SaaS. Platforms where each customer's data is scoped to that customer on every query, and I audit those queries myself. Owner and admin dashboards, live notifications, analytics. • Full-stack, end to end. I build it, deploy it, and hand it off so the next developer can pick it up without me. Node/TypeScript, React/Next.js, PostgreSQL, Redis, AWS. I work with a small team of developers. I'm the architect and your only point of contact, they build under my review, and you'll know who they are. Background: Claude Certified Architect (Anthropic, 2026). Principal backend engineer at OneMain Financial, a US lender, where I shipped generative AI into nationwide loan closing. Two years as the first engineer on a US music-tipping platform, for a client who renewed me the day the first contract ended. Master's in Computer Science, 9+ years building web and mobile applications, and four live products of my own, links in the portfolio below. If you're building an AI agent, a chatbot over your own data, or a SaaS platform that needs one, or you already have one that works in demos and fails on live users, send me two or three lines on what it does and where it's stuck. I'll reply with how I'd build it, what I'd need from you, and what I'd do in the first week. If you'd rather start with a review of what you already have, I do that too.