

IDEAS Lab
Built a real time SLAM pipeline in C++ and Python with RGB D sensor fusion and Kalman filtering, streaming calibrated camera data to a multi GPU server, improving 3D reconstruction accuracy 25% and reducing latency 30%.
- Implemented neural radiance fields (NeRF) for novel view synthesis, generating photorealistic 3D scene reconstructions from camera data for autonomous navigation.
- Generated real time navigation signals from incomplete 3D maps, choosing where a robot should explore next in environments it has not fully mapped.
What's actually hard about ML research
It was the model, to be honest. Trying to write a model with minimal public code out there, outdated libraries, and duct taped GitHubs that were written in languages people don't use and set up for specific GPU jobs was a pain. There needs to be a solution to the problem of being able to easily reproduce and extend ML models, beyond just downloading the weights.
Reproducibility in robotics
Robotics research has the worst version of this problem. The methods for getting a trained model running on a physical robot are barely documented, and training pipelines are rarely reproducible without rebuilding the whole rig from memory. What's different about robotics is the hardware coupling and sensor calibration. Setting up RGB D cameras is not easy, and neither is real time streaming the data to a server across multiple GPUs.
What I'm proudest of
Generating real time navigation signals from incomplete 3D maps. There's so much that goes into figuring out where to go when you're exploring. I didn't even get to work on it for long enough to produce results that I was happy with, but identifying how to optimize navigation and spatial search in unknown environments is a genuinely applicable problem.
What research lab work is really like
It's really hard. It's so hard being thrown into the deep end of having to understand papers, find code, stitch it together, try to run tests, and iterate on difficult to set up models. Having a good GPA doesn't help with that, which is what many people get wrong. You need a genuinely creative mindset, and so much grit and persistence, enough to actually start making progress, because starting out basically feels impossible.
Slowly, then all at once
The all at once moment came late. We made nearly all our progress in the last three weeks. Progress on a new project is always like this: slowly, then all at once. Once you've tried enough things, pieces just start clicking together, and progress comes quickly once the bottlenecks clear.
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.