Most portfolios show the build. Almost none show the debugging.

A portfolio site is usually a highlight reel: a few screenshots, a gradient, a contact form. It shows what was built, but rarely how it was built — or what happened between the idea and the finished product.

I wanted this site to work differently.

Think of it as a folder rather than a gallery. My work is organized as cases: engineering roles, projects, experiments, technologies, and the things I have learned along the way. Open a folder, pull out a file, and there is more than just the final screenshot — you can see the thinking behind it.

I’m a Computer Science engineer who enjoys building across the stack, but I’m particularly interested in the parts of software that make systems reliable.

At Cognizant, I work across frontend development and test automation — building customer-facing e-commerce features and reusable UI components while working with TypeScript and modern frontend frameworks including React and Angular. Alongside development, I built a Java-based test automation framework using Selenium, TestNG, Maven, and the Page Object Model. I developed 100+ end-to-end test cases, identified 30+ defects, and integrated regression and smoke suites into CI/CD pipelines.

At CRIS, I worked on the IRITM admin portal with Angular, TypeScript, Bootstrap, and Spring Boot. I worked on role-based navigation, modular architecture, and REST APIs, including more than 20 endpoints supporting 500+ daily users.

At QSS Technosoft, I worked with React, contributed to responsive UI components, and helped improve internal development workflows through tooling and documentation.

The common thread is simple: build things that solve the actual problem, and build them so the problem does not have to be solved again.

That same idea shows up in my projects.

PredictCare combines machine learning with a full-stack application to assess disease likelihood using multiple classification models. IdeaTrack is a full-stack innovation management system built around idea submission, collaboration, review, approval, and analytics.

Some projects are practical. Some are experiments. Some exist because I wanted to understand how something worked.

But they all have one thing in common: they started with something I wanted to build, understand, or improve.

The technologies change — Java, Python, TypeScript, React, Angular, Flask, Spring Boot, Selenium, SQL, Docker, Jenkins — but the approach stays the same.

Learn the system.
Build the thing.
Break it.
Understand why it broke.
Make it better.

This portfolio is an archive of that process.

The folder’s open. Start anywhere.

Aryan Saraogi — Software Engineeraryansaraogi02@gmail.com  ·  LinkedIn  ·  GitHubStructure after Mosby’s Files by Tubik Studio