Projects

Problem

Freight pricing is rarely a fixed-rate calculation. A quote can change based on origin and destination, zone mapping, actual weight, volumetric weight, chargeable weight, carrier-specific rules, fuel surcharge, GST, minimum charges, and business-specific exceptions. If those rules are not modeled clearly, the system becomes hard to test and harder to explain to users.

My Contribution

I am designing the backend architecture, quote flow, data model, service boundaries, Docker setup, Redis caching plan, and AI explanation layer. My focus is on keeping the pricing calculation deterministic and testable while using AI only to explain the calculated result.

Problem

A useful URL shortener has to do more than store a long URL and return a short one. It must generate unique short codes, support custom aliases, enforce authenticated ownership, handle redirects quickly, check expiry rules, track analytics, and stay reliable after deployment. Small mistakes in these flows can lead to broken redirects, duplicate aliases, or users seeing data they do not own.

My Contribution

I built the backend APIs, JWT authentication, PostgreSQL schema, redirect logic, analytics tracking, frontend dashboard, and deployment flow. I also handled the integration details between the React frontend and .NET API, including CORS, environment variables, and production endpoint configuration.

Problem

Enterprise logistics systems need to support real operational rules: booking flows, customer-specific configurations, duplicate tariff handling, shipment state changes, document workflows, and rate applicability checks. These systems often have legacy layers and dense SQL logic, so even small changes require careful understanding of existing behavior and edge cases.

My Contribution

I worked on backend APIs, SQL Server stored procedures, rate duplication logic, rate applicability checks, document upload workflows, shipment tracking states, and database changes. My role involved understanding existing workflows, making scoped changes, and validating behavior without exposing confidential business logic.

Problem

A resume is useful, but it compresses too much context into bullet points. I wanted a recruiter-friendly structure where someone can quickly understand my backend focus, inspect real projects, read technical writing, and contact me without searching through disconnected links.

My Contribution

I built the website structure, homepage sections, project showcase, project detail pages, blog timeline, blog detail pages, services page, contact page, and contact form integration. I also deployed it with Vercel and connected it to a custom domain.

Problem

Interview preparation can become messy when problems are solved randomly and saved without context. It becomes hard to revise patterns, compare approaches, or remember why a solution worked. A structured repository helps turn practice into a repeatable learning system.

My Contribution

I planned the repository structure, topic-wise roadmap, Java solution template, README format, progress tracker, and explanation-first approach. The focus is on building a learning system that supports revision and pattern recognition over time.