ST

Saahir Tandon

Student & Developer

Hello, I’m

Saahir Tandon.

Pronounced “saw-hair”

Computer Science student focused on AI, software engineering, and data-driven products.

I’m a student at Rutgers University–New Brunswick (Sep 2023 – Dec 2027), pursuing a Bachelor of Science (BS) in Computer Science with a double-minor in Data Science and Economics while maintaining a 3.6 GPA. My main focus is on Applied AI, Backend Engineering, and Full-Stack Development—building clean APIs, database systems, and practical software applications.

Portrait of Saahir Tandon

My why

What draws me to this work

My “WHY” for AI & Machine Learning:

Growing up, my dream was always to make gaming content on YouTube. Unfortunately, my childhood was during a time when parents were pretty pessimistic about technology usage, and nobody around me viewed content creation as a real path—so I had zero support. I used to pick up loose change off the ground in NYC to save up for basic equipment, sneak onto my dad’s laptop late at night to record, and edit video clips on school computers whenever I could squeeze in time.

Against all odds, that hustle actually worked—I managed to build an audience and saw real success with my channels. But no matter how hard I worked, I hit a massive wall: I lacked the high-end hardware and expensive software needed to push my content to the next level. I had the drive, but the technical barriers held me back from reaching my full potential.

That experience is the core reason I fell in love with AI. Tech shouldn't only belong to people who can afford thousands of dollars in gear or spend years mastering overwhelming software. AI is the ultimate equalizer—it opens doors for anyone who has a great idea and the drive to pursue it, regardless of their background or resources.

Today, that vision directly shapes my work. At Handshake AI, I help train and audit automatic speech recognition (ASR) models to convert video and audio into accurate text. Think about a deaf creator trying to edit a video of themselves: without being able to hear the audio cues, the process is nearly impossible. An AI tool that precisely transcribes and time-codes clips completely levels the playing field for them. Whether it's making content creation accessible to disabled creators or building tools that automate hours of tedious timeline assembly, my goal with AI is simple: break down technical walls so anyone with a spark can just create.

My “WHY” for Full-Stack Software Engineering:

Backend (The Engine):

Whenever a major game dropped—like Pokémon Scarlet & Violet or Zelda: Tears of the Kingdom—release week was my ultimate crunch time as a creator. I wasn't just playing for fun; I was live streaming the journey, taking notes on stream, and frantically editing guides to be among the first creators on YouTube to cover new features. My setup was a full mission control center: streaming and recording my gameplay on one screen, watching fellow creators like SmallAnt or AustinJohnPlays test strategies on a second, and tracking community datamines on a third to keep my audience informed.

It was a massive, collective effort where creators and builders worked together to break a game wide open. As streamers and video creators, we were testing mechanics live and building content for millions of viewers, relying directly on dataminers who dug into the raw files to pull out the hidden backbone—exact spawn rates, damage formulas, and secret item coordinates.

Seeing how those hidden files powered the entire community's content was my lightbulb moment: the frontend graphics are just the surface, but the real depth, logic, and magic live in the code behind the scenes. That realization is what drew me to backend engineering. I love building the underlying infrastructure—the database schemas, API pipelines, and server architectures—that quietly power complex systems and make data-rich experiences possible.

Frontend (The Experience):

There’s nothing quite like opening a piece of software for the first time, seeing a wall of a hundred confusing buttons, and feeling instantly overwhelmed (looking at you, After Effects). Early on, when I was just starting to make content and trying to edit my first video clips, software like that felt less like a creative tool and more like a puzzle I couldn't solve. I spent hours clicking through hidden menus, messing around with clunky timelines, and wondering why doing something simple had to feel so hard.

Having fought with confusing software for years as a beginner, I care deeply about building frontends that feel smooth, simple, and natural from the second you open them. A powerful backend engine doesn't mean much if the driver gets lost trying to figure out where the steering wheel is. My goal on the frontend is to take complex backend data and turn it into clean, intuitive interfaces that anyone can jump into and use without needing a manual.