DEV Community: Aadit Bhatia

Over a month at a startup: my experience

Aadit Bhatia — Wed, 08 Jul 2026 02:47:11 +0000

It's been a pretty long time since I've updated this, but to me that's better for you, the reader, because I can give you so much more information at a time about my experiences.

It's been over a month since I started at Treevah, a startup focused on providing job-seekers with an organizational system to make the application process easier, and I think I've seen big parts of how the workflow at startups works.

Firstly, the pace should be discussed. It's a job that really keeps you moving throughout the day and the week, but none of that work has really felt unsatisfactory. Tiring, yes, but not useless. The amount of work that has to be put in by all team members to get an alpha product, let alone a beta or prod scale, speaks to how much workload you get at a startup.

It's not something that I've hated; in fact, it's been some of the most fulfilling work I've done. I've gone from public speaking clubs to hackathons to semester-long projects, and the opportunities I've had this summer, progressing my skills in web development, are second to none.

I want to speak to some of the frustrations that have come with the job as well. A lot of the bugs I've worked on are bugs that don't exist because of any singular failure in logic. More often, they exist because of things like multiple definitions of the same CSS rule, or defining elements outside of the div that give them certain properties.

Some of these bugs have taken me multiple weeks to track down and fix, but that's what makes it so fulfilling to me. Working at a startup, where the pace is constant and the bugs even more so, has taught me that there'
s always a solution to be found, but it's never the first thing you think of.

My first day as an SWE Intern at a startup - The importance of QA

Aadit Bhatia — Tue, 19 May 2026 15:28:05 +0000

Hi everyone!

Yesterday was my first day of work at my first internship, and I have a few thoughts I want to get off my chest. I'm currently working at Treevah as an SWE intern, entirely remote.

The first thing I've realized after just a day is that QA work(something I thought to be entirely separate from SWE work) is very intertwined with what I'll be doing in the near future. My first task has been simply getting used to the app itself and playing around with it, seeing if I can find bugs related to coreflow blockages, UI/UX issues, and other issues I can find on a P0-P3 framework.

For the first hour or so of work, I thought it was pretty easy work, if not a little boring. But it wasn't until I got deeper into the app that I realized just how important QA work is, not just for the client but for the developers behind the product as well.

QA work is obviously important to ensure that your client is receiving a polished version of a product, but what I've come to understand in a short time is that QA work gives developers the "mindset" needed to create solid products. Specifically, it allows SWEs to understand all of the different criteria that must be checked off in order for a product to be considered "polished".

To put it in more polished terms, doing QA work, in my eyes, allows developers to create work that's able to adhere more to the design-by-contract design philosophy.

I came into this internship expecting to start off with learning the company's stack and how to use it, but the first day ended up being something even more valuable: I began to learn how to think like an engineer!

From the Ground Up: A Journey!

Aadit Bhatia — Wed, 22 Apr 2026 20:57:52 +0000

Hi! My name is Aadit Bhatia, and I'm a freshman at The Ohio State University studying Computer Engineering. As someone trying to enter a job market currently dominated by talks of either the glory of AI or the doom that it'll bring us, it becomes very tempting to rely on tools like Claude Code for everything. However, that's not how you learn, and my view is that if you replace junior developers with AI, you'll never get a senior developer.

Therefore, I'm starting a series to document my entire journey of learning software, hardware, and everything in between! You'll get to see the good, the bad, the clean, and the dirty parts of software development, all in the hopeful goal of showing that AI can't replace you if you're good enough.

I'll be documenting my journey in learning web dev tools(React.js, Node.js, Microsoft Azure), then move to other parts of software development and even hardware development in the future. See you soon!

-Aadit Bhatia