A holistic approach from beginning to end

At Amazon, I’ve been building across high-scale systems and frontier tech. I engineered a data integrity algorithm in Java and TypeScript that eliminated 165,000+ hours of manual revision—low key, one of the cleanest wins I’ve shipped. I’ve worked on distributed systems handling 25M+ messages a day, built core features for a publishing platform that pays out $50M+ to authors monthly, and led machine learning ETL pipelines across millions of rows using AWS Glue, PyTorch, and S3. Now I’m at AWS Bedrock, working on Responsible AI—helping build Bedrock Guardrails and shape how foundation models are deployed at scale. The work is fast, ambitious, and squarely at the center of where tech meets society. It’s exactly the kind of challenge I look for: real-world stakes, zero playbook, and the chance to build things that actually move the needle.

I joined Tesla as a Software Engineer working on the Energy Product Configurator—the tool customers use to design and buy solar panels and Powerwalls—rebuilding core flows in React, Next.js, Node.js, and C# for 60,000+ weekly users. Midway through, I led development of a new web app to help customers find certified installers, now live in 25+ markets and used by over 20,000 people a week. I owned it end-to-end, from backend to production launch. I also shipped features in the Tesla mobile app using React Native and Node.js to support the energy fulfillment journey—because buying a solar system is a lot more complex than adding to cart. Tesla moved fast, and so did I. I found mentors, leveled up fast, and got feedback that I was performing at a mid-level engineer standard. Six months of building, learning, leading, and proving I belonged.

The summer after my freshman year, I joined Chewy as a Software Engineer Intern, stepping into a fast-moving engineering team supporting tens of millions of customers. I worked on the frontend performance stack, implementing caching strategies with React and Next.js that improved micro-frontend load speeds by 300%. It was one of those projects where every change had real, visible impact—and it taught me how to balance speed with stability in a high-traffic environment. I also helped resolve a backend bug that had been quietly affecting over 300 internal users each week. I worked across Node.js, Jenkins, Docker, and Terraform to track it down, patch it, and push it out cleanly. That summer gave me my first look at what it means to build at scale—tight feedback loops, production ownership, and the kind of learning you only get by being in it.

I joined the interACT Lab at the University of Washington as a research assistant—just hoping to get closer to projects that meant something. I stuck around for over two years, eventually becoming the lead technologist and engineer in the lab. That time gave me the opportunity to work on Social Media Test Drive (SMTD), a large educational platform developed across multiple universities to help adolescents learn how to use social media safely. While the core platform was already established, I led the development of the international and Spanish-language version—an initiative that reached students in classrooms around the world.

Behind the scenes, I automated a data pipeline using Java to collect, store, and structure anonymized user interaction data at scale. I also developed custom AI/ML algorithms using PyTorch to help researchers analyze how young users engaged with the platform—surfacing patterns and insights that otherwise would’ve been buried. It was one of those rare projects that blended education, behavioral research, engineering, and real-world impact—and getting to lead that work as a student was something I’ll never forget.

After running JoDi Services solo for a while, I wanted to get out of my own bubble and see what it was like to build with a team. That’s when I joined CodeLabs, a nonprofit internship during the summer before college that paired a few of us scrappy high school students with a mentor from Microsoft. Our goal? Build something that made people think a little deeper about the information they consume. Over the course of eight weeks, our team of four developed an Android app that presented opposing news perspectives, helping users see both sides of a headline. I focused on both frontend and ML—writing the app in Java and XML while also designing a bias detection model using TensorFlow that reached around 80% accuracy. It wasn’t perfect, but it worked. And more importantly, it sparked conversations about bias, tech, and truth that still stick with me today. It was my first time shipping something with a shared vision, real stakes, and actual user impact. I wasn’t leading a company this time, but I was learning how to build with people, communicate under pressure, and take a backseat when it made the product better. And honestly? That was one of the most valuable lessons I could’ve learned that early on.

I started JoDi Services in high school during the early days of COVID, when small businesses around me were scrambling to stay afloat. Brick-and-mortar shops that had never touched a website suddenly needed an online presence overnight. I had no agency experience, no team, and honestly, no clue what I was doing — but I had a laptop, an eye for design, and just enough technical know-how to start helping. I built websites, ran customer support, handled emails at 1 a.m., and learned how to talk to clients like a real business owner (even if I still had math homework due the next day). It was scrappy, fast-paced, and full of Google searches — but it was also my first real taste of what it feels like to solve a problem that actually matters. What started with helping local cafés and salons quickly picked up momentum. Before I knew it, I was working with high-profile clients like COAR, a political risk and development consultancy working in conflict-affected regions, and a luxury architecture firm designing flagship spaces for brands like Apple, Louis Vuitton, and Balenciaga. That’s when it clicked: I was running a real business. Every project taught me something — how to communicate better, how to deliver when it counts, how to balance creativity with execution. JoDi Services was never about chasing clout or scale — it was about stepping up when people needed help, learning fast, and building something real from nothing. Looking back, it was my first startup. I just didn’t know to call it that yet.