

Naval Research Laboratory
Replaced slow physics based underwater acoustic simulators with deep learning, encoding sound speed profiles as images and using image to image translation models to predict transmission loss 20% more accurately at a fraction of the compute cost.
- Built a LangChain RAG system for classified document retrieval with vector database indexing and document chunking, running entirely on local LLaMA 2 inference with no external API access, reducing query time 65%.
The image to image insight
This was the first time I did ML research at a job, and it was incredible seeing a problem that required deep technical ML work. The problem was reconstructing transmission loss graphs from a sound speed profile of underwater acoustics. It was a novel approach because it used image to image translation models to replace physics simulators. Nowhere before had I seen such an interdisciplinary application of machine learning. Completely unrelated disciplines you would never imagine connecting, yet it found an application and actually showed improvement in computational complexity over the difficult and slow physics simulators. The biggest insight came from my technical lead: you could represent information about the acoustic space as colors in an RGB dimension, and the space itself as a two dimensional image around the instrument. That's what made the whole thing work. What I took away from watching that kind of thinking is that the best researchers are able to abstract away a problem, treating data and vectors as just numbers being mapped to each other, not images, not sound data. At their core, they're all just signals, and they can be mapped to each other and used in conjunction. It's very rare that someone transfers a whole architecture from one domain to another. Architectures travel between fields when you find the right representation. Acoustic data became a 2D RGB image, and an image to image translation model could do the work of a physics simulator.
Building RAG before RAG was mainstream
My work at NRL also included building a LangChain RAG system for classified document retrieval, and the timing mattered: LangChain had come out probably a few months before my internship started. I was using it at its very inception to build out RAG systems with vector databases and chunking strategies, before any of that became mainstream, before knowledge graphs and large context windows existed. The models available back then were quite bad. We were using LLaMA 2, which performed poorly, but it still taught me a lot about how those models work at their core. What that primitive tooling forced me to understand is the importance of context optimization. With "unlimited" token budgets now, people do basically whatever they want with as much context as possible. There are tradeoffs. It's hard to deterministically say what needs to be included in context and what doesn't, but there is real value in optimizing context injection. We experience Jevons paradox: as models get better and context windows grow, people inject more and more. When you disregard optimization, it becomes impossible to filter unnecessary information, and you leave that filtering in the hands of a nondeterministic model.
The classified hardware constraint
Building inside a classified environment meant we couldn't use any APIs. None of the state of the art models at the time were usable, and open source simply wasn't there yet. The GPUs we had were slow, so output was slow and low quality. It was a real constraint. What that experience tells me about the future: the gap between what you can run locally and what the APIs give you is closing as models become easier to run locally. Eventually, the hope is that frontier level intelligence will be able to perform on machines in every office. Every developer would have their own local model. And a lack of surveillance by third parties actually improves security rather than hurting it, especially for high stakes classified environments. The counterargument is real — democratizing frontier models locally makes it risky because bad actors could take advantage without regulation or oversight. But more freedom also means more innovation, and intelligence on demand becomes a lot cheaper and usable by the majority of the population.
For startups and founding teams
Karthik Thyagarajan is a founder-engineer studying Computer Science and Artificial Intelligence at Purdue. At Samsung Research America, he co-architected an always-on AI agent runtime for XR glasses. He is currently building Tavi, a voice teammate for engineering standups, and co-founded buildpurdue, a founder community at Purdue. His work spans agent infrastructure, on-device AI, product engineering, and evaluation.
For an early team building AI products, his strongest demonstrated fit is owning a broad technical problem from product decisions through implementation and evaluation. His current interests are live voice and video AI, AI-first wearables, and infrastructure that lets agents discover and use internet services.
Substantial ownership of agent systems
At Samsung Research America (May to August 2026), he co-architected an always-on agent orchestrator in Kotlin and owned half of a 25+ module runtime. His reported on-device router achieved 95% signal suppression and 90% intent-routing accuracy. His work also covered tool permissions, model routing, memory, and phone control, connecting model behavior to a usable device experience.
Builds teams and operating systems around a problem
As buildpurdue's co-founder and co-president, he helped turn an informal gathering into a founder community with a selective cohort, weekly co-working, funding, and founder-led problem-solving workshops. He built much of its web platform and integrated CRM, applications, events, and check-ins. His account describes data on around 500 students and a mailing list of about 1,000.
Makes technical claims testable
He built PARM, an open-source causal benchmark for when an agent should use personal memory: 157 frozen scenarios and 471 executable cases, with deterministic scoring and versioned replay artifacts. Its portfolio account explicitly distinguishes development results from held-out claims. He also built google-tools-mcp, a published MCP server exposing 169 Google Workspace tools through one OAuth flow.
Pursues difficult product problems
He is currently building Tavi, a voice teammate intended to answer codebase questions and handle small action items during engineering standups. The project tackles multi-person turn-taking, when to stay quiet, sandboxed coding, and synthetic meeting evaluations. This is ongoing work, rather than a claim of shipped adoption. His published interests explain the direction behind it.
Co-founder who ships and thinks about distribution
At Repple (November 2025 to June 2026), he co-founded a competitive fitness app released on the App Store and built the entire FastAPI, PostgreSQL, and Supabase backend, including synchronized workouts, ELO matchmaking, and weekly competition logic. His firsthand account also describes marketing before the UI existed, campus distribution, and why local community density mattered to the product.
This brief summarizes Karthik's public portfolio and firsthand accounts. Employment contributions and internal performance metrics are self-reported; linked code and artifacts provide additional evidence where available.