Trace the cause.
I prefer systems that expose why something happened — graph edges, request flow, service boundaries, queue state or a failed constraint.
03 / ABOUT · THE BUILDER BEHIND THE SYSTEMS
I'm Akarsh — a Computer Science & Engineering student who likes turning vague problems into concrete systems, then pushing those systems until their trade-offs become visible.
I prefer systems that expose why something happened — graph edges, request flow, service boundaries, queue state or a failed constraint.
Projects are my way of learning. I reach for a working model quickly, then use real behavior to decide where complexity is actually justified.
Good engineering should be understandable. Clear interfaces, useful feedback and intentional visual hierarchy matter to me as much as implementation.
BACKEND → INTELLIGENCE → PRODUCT
I've worked through REST APIs, graph analysis, anomaly detection, microservices, Redis-backed concurrency and database-backed applications. The common thread is simple: I like seeing an idea become a mechanism.
A virtual software engineering simulation with JPMorgan Chase & Co. exposed me to enterprise-style backend workflows, REST controllers, Kafka and H2 persistence. My own projects are where I take those ideas further — shaping boundaries, testing assumptions and making the result explainable.
B.Tech in Computer Science & Engineering · Dehradun, India
Software Engineering Job Simulation — backend development, REST APIs, Kafka and H2.
Cloud Practitioner, AI Practitioner learning and Generative AI with Amazon SageMaker.
I reach for the technology that makes the system's core idea clearer, not the technology that makes the stack look bigger.