I'm a Full Stack Developer based in Kochi, India, focused on building real-world web applications rather than tutorials — service marketplaces, payment workflows, role-based systems, and admission/workflow tools that hold up under actual usage.
Most of my work sits at the intersection of frontend product thinking and backend architecture. On the frontend, that means React and Next.js interfaces that stay responsive under real data. On the backend, it means designing around Clean Architecture and the Repository Pattern instead of wiring routes directly to a database — so the system stays testable and easy to extend as it grows.
I like problems that force a decision: how a wallet ledger should reconcile, how a multi-role auth system should fail safely, how a modular monolith should be split before it needs to be. Outside of shipped projects, I spend time on DSA and system design, and I'm currently extending that into AI/LLM integration — RAG pipelines, MCP, and agentic tooling — as a new layer on top of the same engineering fundamentals.
Languages
Frontend
Backend
Database
Architecture
Cloud & DevOps
Tools
🛠️ Favorite Tools & Environment
Docker is a current learning target, not yet in production use.
| Project | Description | Stack | Live / Case Study | Repository | Status |
|---|---|---|---|---|---|
| QuickWork — flagship | Multi-role local service marketplace: job discovery, provider assignment, HMAC-verified Razorpay payments, wallet & debt-recovery ledger, admin monitoring | React · TypeScript · Node.js · Express · MongoDB · Redux Toolkit · Socket.IO · Razorpay · AWS | Case Study | Repo | Completed |
| AdmissionFlow | School admission workflow system — parent & admin-team roles, entrance-exam scheduling, score management, course assignment, built on Clean Architecture | Next.js · NestJS · TypeScript · MongoDB · JWT | Case Study | Repo | Completed |
| ErrorLens | AI debugging assistant that parses runtime stack traces and queries an LLM for root-cause analysis and confidence-scored fixes | React · Node.js · Express · MongoDB · AI APIs | Case Study | Repo | Completed |
| TIMZO | Watch e-commerce platform with order verification, stock tracking, and Razorpay payment checks | Node.js · Express · MongoDB · Razorpay | Case Study | Repo | Completed |
| DevShowroom | Shareable developer showcase platform for presenting technical projects with more clarity than a repo list | Next.js · TypeScript · Tailwind CSS · Mongoose | Case Study | Repo | Completed |
| Reviewer Bucket | Community SaaS for Brototype students to discover reviewers, share honest interview experiences, and request missing reviewers | Full-stack (final stack TBA) | — | Private | Completed |
| ShortLink (URL Shortener SaaS) | Authenticated URL shortener with click analytics, link management, and a NestJS backend built on the Repository Pattern | NestJS · MongoDB · React · TypeScript · Vite · Tailwind CSS · TanStack Query | — | Private | Completed |
I have several additional repositories exploring different technologies, concepts, and learning experiments — browse them all in the repositories tab.
DSA and algorithmic thinking are a constant background thread alongside project work — not as a separate track, but as the reasoning that shapes how a feature gets architected in the first place: what the access pattern is, where the bottleneck will actually be, and what the simplest correct data structure is before reaching for a clever one.
- Clean Architecture & Repository Pattern — business logic stays independent of the framework and the database driver
- Modular Monolith over premature microservices — service boundaries that are real but don't cost a network hop yet
- API design first — DTOs, validation, and consistent error shapes before the first endpoint ships
- Maintainability over cleverness — code that a teammate (or future me) can extend without a rewrite
Good software rarely announces itself as "clever." It shows up as a codebase where the next feature is easy to add and the next bug is easy to find — that's the bar I build toward.