Aryan Saraogi
A working archive of a software engineer — customer-facing e-commerce front ends, a Java automation framework wired into CI/CD, and products built because the problem was interesting. Java, React, Selenium, and whatever the defect actually needs.
Three companies, three different definitions of the job: a customer-facing e-commerce product at enterprise scale, a government rail-institute portal serving hundreds of daily users, and a first internship spent learning what a code review is actually for.
Systems where the interesting problem is not the interface. A test framework built so a suite can be handed over and still run, model selection under real accuracy targets, and a relational schema that has to survive a multi-stage approval workflow.
Small, sharp tools built to be used rather than demoed — each one shipped to a live URL or a store listing, each one answering a problem its author actually had. A reference nobody had written, a map of places worth remembering, a desk you can rearrange, and a cleaner way to read the web.
The base layer: a computer science degree, 350+ solved problems, a stack accumulated across three jobs, and the certifications that put a name to parts of it. Languages, systems, and the concepts that decide whether the thing holds under load.
