What's actually happening here
Most resume chatbots are a widget bolted onto a page. This one's a small system Emily built and runs herself — and like any good ITSM person, she'd rather show you the lifecycle than just tell you to trust it. Here's what happens between hitting send and seeing a reply, told the way she'd track it: as a ticket.
Ticket lifecycle
Submitted
You type a question or tap a suggested prompt. It leaves your browser as a secure request, locked down so only this site can call the backend.
Your browser, HTTPS + CORS-restrictedRouted
An edge function checks the request, enforces a per-visitor rate limit, and attaches Emily's background as context. The Anthropic API credential lives only here — it never touches your browser.
Cloudflare WorkerResolved
Claude writes a reply using only the attached background material — not whatever it might already know or guess about Emily Pham from elsewhere.
Claude, single source of truthClosed
The reply streams back word by word and lands in the chat — ready for whatever you ask next.
Service-level commitments
Stays in scope
A question outside Emily's candidacy — general homework help, unrelated trivia, anything off-script — gets politely declined rather than improvised on.
Comp questions go to Emily, not a guess
Salary and compensation questions are routed to a real conversation with Emily instead of being answered or estimated by the model.
Capped on purpose
A per-minute message limit and a length cap per reply keep the assistant available to everyone and the API cost predictable.
One document, no embellishment
Every fact traces back to a single reviewed background document. Nothing about Emily's experience is invented, inflated, or pulled in from elsewhere.