FAQ

I was into building things, and DSA was always second on my priority list — I didn't spend much time on it. I didn't realize until later how much weight it carries for landing a high-paying role, and I've started practicing it seriously now. As for open source, I'm new to it — nothing of mine has been merged yet, so I didn't list it. Both are things I'm actively working on, not things I'm ignoring.

No overlap. I gave AarogyalinQ two weeks' notice ahead of time, and the transition into Aude.ai was seamless.

Yes — I'm actively interviewing for full-time roles.

It reads that way from a list of names, but the work built on itself. I started with ownership of a single feature on Digichikitsak, and from there was trusted to deploy the entire project, not just my piece of it. From there I moved into real FDE work — directly connected to a client, customizing an existing project (Axion) to what they needed end to end, managing everything until it was live for them. I was then handed an incomplete version of Axion and finished and deployed it myself. After that I was given ownership of a new project, HealthyMitra, and built it from scratch through to production. It was a high-velocity startup, and each step was more ownership than the last, not less depth.

Both. I synced with the team when it was needed for the work, but not on a daily schedule — the rest of the time I worked on my own hours.

I've just finished my final semester exams and haven't received my degree yet, so I'd call myself a new grad at this point. Both internships were remote, which is what made it possible to manage college and work at the same time.

I split the day strictly: mornings before college were for college work, and evenings and nights after college were for the internship. Keeping the two separated rather than mixing them is what made it sustainable.

Mostly I just haven't had the spare time yet to take screenshots, record demos, and add or update links across every project. It's coming soon. For the work I built inside a role, the code and live links usually can't be shared publicly regardless — I'm happy to walk through any of that in an interview instead.