Founding-engineer reps · NYC
TanayShah.
I'm an AI engineer. I build the systems behind production chat apps and agent platforms — backends, sandboxes, iOS clients, fast.
CS Honors + Statistics · UMD · Dec 2025
4 roles · 4 years · NYC-based
Open to: founding · early-stage · applied AI
Most recent: Founding Engineer @ Structured AI
Most recent 14-week window: 1,035 commits, 832K lines of production code at ~100% blame-ownership, 30 PRs merged. Four production roles across four years. The numbers are reproducible — charts in §03, timeline in §04.
I'm Tanay. I build production AI infrastructure — agent loops, sandboxed runtimes, durable event-sourced chat, the iOS clients that hang off them. The kind of system you'd want behind your own product.
The way I work: pick a hard problem, draw the diagram, ship the first version in days, instrument it, iterate. I think about agent systems for fun — LangGraph + Claude with on-demand tool loading; gRPC bridges between API and slim agent pods; Python sandboxes built on JSON-RPC, AST validation, and seccomp-locked bubblewrap. The diagrams in §02 are real, the numbers in §03 are measured.
// MOST RECENT CHAPTER
Fourteen weeks as Founding Engineer at Structured AI (NYC). 1,035 commits across backend, frontend, iOS, Revit, and infra. Architect of Document Agent v2 (the system in §02), the Programmatic-Tool-Calling sandbox, AEC-Bench, and the iOS app from zero. Before that: distributed systems at Intuitive Labs SF; two years of ML research at UMD's iSchool fine-tuning Llama on twenty million Wikipedia AfD comments. I started writing CNNs at sixteen.
Senior at the University of Maryland — departmental honors in CS, Statistics minor, graduating December 2025. The page below is instrumented; you can read it like a spec.
How I architect
agent systems.
Same shape every time: a thin client, an API gateway, a slim agent pod that runs LangGraph + Claude with on-demand tool loading, untrusted code in a hardened Python sandbox, retrieval over pgvector, durable state in Postgres + Redis. The diagram below is a real one I shipped — Document Agent v2 — but the pattern is portable.
- → Reference impl: Document Agent v2 · Structured AI · 2026
- → 4,350-line chat WebSocket store · 100% authored
- → 1,668-line agent loop · ~100% authored
- → Replaces a 1,448-line monolith and Anthropic's hosted PTC path
What fourteen weeks of me looks like.
1,035 commits, ~74/week median. The chart below is a single 14-week sample (Feb–May 2026, my Structured AI tenure) — picked because it's the most recent and the data is reproducible from public git. The peak was the week of April 20 (85 commits on Apr 22), when I parallelized staging deploys and replaced `git clone` with a blobless wipe-guard (3 min → 30 s).
Surface area —
instrumented.
A skill cloud lies. This grid tells the truth: which years used what, how deeply, and where things accelerated. 2026 is the steepest column on the page — that's by design.
Want to build
something serious?
Founding / early engineer roles. AI infra. Backend at scale. Big tech if the team ships hard problems. I'm in NYC, willing to relocate, and I move fast. Pick a command:
- $ open mailOpen mail client↗
- $ ssh linkedinConnect on LinkedIn↗
- $ git cloneView source on GitHub↗
- $ open devpostDevpost portfolio↗
- $ cat resume.pdfDownload resume↗