Nakul Gupta / Founding AI Engineer

I build AI for the real world.

I design reliable systems for messy data, high-stakes workflows, and the people who depend on both.

CurrentlyTheo AISan Francisco, CA
52%lower benchmark processing cost
39%lower case-match cost
53%higher processing throughput
Measured across internal production benchmarks

Selected systems

Two bodies of work that show how I think: trace the data, control the expensive path, and design for operators.

01Production system

AI intake and case intelligence

A traceable pipeline that turns enterprise inboxes and documents into structured case intelligence.

Graph retrievalDocument AIEvent-driven systems
Read case study
Email + documentsunstructured input
01Route
02Extract
03Normalize
04Classify
05Link
06Match
Case intelligencestructured + attributed
02Open-source contribution

Beehive

Non-blocking workspace operations across a Rust terminal UI and React/Tauri desktop app.

RustTauriReactConcurrency
Read case study
feature/intakeagent 01
fix/cacheagent 02
docs/architectureagent 03
3 operations active

Experience

Theo AI

Founding AI Engineer

Production legal AI, data architecture, and customer delivery across intake, document intelligence, retrieval, and multi-tenant systems.

Kelley School of Business

Machine Learning Research Assistant

Built Python data-processing and ML analysis pipelines for logistics operations, transforming forklift maintenance data for mediation analysis and business-facing insights.

Scry AI

Software Engineer

Built Java and Spring Boot ingestion services for industrial IoT workflows, processed 1M+ NEOM data points, and designed a retention plugin that reduced storage overhead by 60% while mentoring junior engineers.

Nakul Gupta

I work where models meet systems.

I am an AI engineer who moves between architecture, implementation, and customer discovery. At Theo AI, I have worked on intake pipelines, document intelligence, graph-backed retrieval, multi-tenant data systems, and the operational controls that make AI dependable.

I care about the unglamorous parts: provenance, retries, cost accounting, migrations, access boundaries, and interfaces that make complex systems legible.

Building something difficult?

Let's talk about the system behind it.

Email me