

Quantum Racer
Quantum Racer is a simple car racing game that teaches players about quantum decoherence and noise by challenging them to navigate a quantum car through a track while avoiding obstacles. The game is designed to be fun and educational, making it suitable for players of all ages.
Choosing one concept
Instead of worrying about the accuracy versus fun tradeoff, I focused on the simplicity of the concept. For World Quantum Day, in a world where most people don't even know what quantum really means, it's important to home in on a specific concept and distill it. The aspect I focused on was quantum decoherence. It's central to why quantum computers can't function at the scale they do, because of noise. The purpose of the game was to teach people how badly noise can render quantum states unpredictable.
How the game taught it
The game put you in the driver's seat of a quantum car, and while driving you'd be placed into superposition. That superposition was kept very simple: in one state the car was stationary, and in the other state it kept moving. As you drove in the moving state, you could increase the probability of maintaining that state when wave function collapse occurred after a set amount of time. Scattered across the track were probability increasing tokens and noise tokens. Every time the car crashed into a noise token, the screen would blur into static and simultaneously reset the probability of maintaining the moving state to a random, uncontrollable value. It might happen that a player drives for 30 seconds, makes it 25% of the way through the track, then crashes into a noise token that drops their probability to 10%. On wave function collapse, the car resets to where the superposition started. That moment shows how one bad interaction can undo a carefully constructed quantum state.
What would have made it better
Ideally, the player would be dropped straight into an immersive 3D environment, something like Gran Turismo or Forza, where educational pop ups appeared in the world itself to explain what the noise tokens and probability tokens were, how they are fundamentally quantum, and why they mattered. We put all of that in the about section, but obviously no player is going to look at the about section before they start playing. The game wasn't so difficult it was impossible to beat. It had a learning curve, but once you got the hang of it you could consistently make it to the end. In the two and a half months we had, it was significant progress. With bigger reach and deeper integration between the game mechanics and the educational content, we could have taught more.
What educational games get wrong
A lot of educational games make the mistake of info dumping on the player and expecting them to read everything and learn it. You don't internalize it unless it's immersive and directly correlatable with the challenges you face in the game. The iCivics games do a great job of this. They walk you through the processes of different political and legal systems in a way that actually teaches you how they work. The mechanic is so ingrained with the real life process that it's impossible to understand the game without also understanding the process. With Quantum Racer, it's possible to understand how the game works without understanding the underlying concepts. That gap in design would have made a big difference.
Why teach quantum at all
I started a quantum computing club in high school, and I'm passionate about teaching younger people about emerging technologies because that forward thinking is what allowed me to get ahead of quantum computing, AI, and machine learning. I think that opportunity should be granted to all students, which is why I built an educational game that any student could learn from and play.
On complexity gatekeeping
Most people think quantum is too complex to engage with. The scientific community does a poor job of introducing younger people to it because they hold the opinion that you must understand everything fundamentally before you can truly understand it. While that's true in the limit, no high schooler is going to comprehend quantum physics at the level that allows them to meaningfully engage with quantum computing theory. What they can do instead is learn a simplified version that introduces the concepts and builds enough familiarity that, when they're older and have more mathematics and physics behind them, those complex ideas map back onto foundations that were already there. Obviously there is unlearning to do, but learning anything quantitative requires unlearning what you fundamentally understand about the world. Having some interest and foundation draws more people to the field, not fewer. When I first encountered AI and machine learning, I knew there was something called backpropagation and that it improved the model. I had never taken a derivative. But that interest drew me in. When I later learned about gradients in calculus, I was able to relate that back to gradient descent, and it gave me a much better mathematical foundation than I would have had if I'd never had that earlier exposure, because the familiarity was already there.
Was it worth building
It was worth building. It was the first time I put an app on the App Store. I created educational material for students, and it taught me a lot about how to design something that is both educational and fun, which matters for anyone who takes on the role of instructor, even tangentially.
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.