The Periodic Table of Tools
Every element carefully chosen for type-safe, scalable architectures. Hover to see the half-life (years of experience).
Frontend
Backend
Data Layer
AWS Cloud
DevOps
AI Tools
Currently Exploring
Experience Breakdown
$ npm run dev
Ready in 1.2s
$ docker compose up
Container postgres started
Container redis started
$ prisma migrate deploy
3 migrations applied
Technologies in Production
// and counting. The stack never stops growing.
The Human Behind the Code
I build software for problems that actually exist. A rural learner in Tamil Nadu who needs coursework in their language. A procurement team drowning in spreadsheets while ₹100 crore moves through manual approvals. An Indian family that just wants a decent biodata without paying a designer. These aren't demo apps — they're systems with real users, real edge cases, and real consequences when they break.
My instinct is always to understand the domain before touching the keyboard. I've found that most bad code isn't caused by bad engineers — it's caused by engineers who didn't understand what they were actually building. The technical decisions I'm most proud of are the ones I talked myself out of.
This portfolio is also a system. Schema-driven, type-safe, with live telemetry and a context menu. Not because it needs to be — because I wanted to see if I could make something that shows how I think, not just what I've shipped. You're currently reading the result.
Years in production systems
Schema migrations survived
Companies shipped at scale
2AM pages this month
career.log
Professional Development · Career Break
Building QuickRecall · interview prep · Bengaluru ↗// fun_fact
I once reduced a 45-second database query to 200ms. The secret? An index. Always check your indexes.
Under the Hood
Each project is a case study in solving real problems. Toggle the architecture view to see how data flows through the system.
A personal interview-prep workspace: a searchable knowledge base of notes, machine-coding problems with a side-by-side code viewer, and quick-recall sheets for last-minute revision.
// Problem
Prepping for frontend interviews meant scattered notes across Notion, half-finished CodeSandboxes, and bookmarks I never reopened. Nothing was searchable, and there was no fast way to revise concepts the night before a round.
// Solution
Built a single Next.js app that unifies the whole prep loop: bundled notes, machine-coding problems rendered next to a live code viewer, and condensed quick-recall sheets. Stateful features like the job tracker run local-first in IndexedDB via Dexie.js — no backend to maintain. Typed end to end, deployed on Vercel.
// not responsive enough for mobile.
// please rotate your device, or better yet,// open this on a laptop like a civilized engineer.
// TODO: private repo — commit history classified until client says otherwise
// the commits exist. they are just behind a very boring NDA.// TODO: map the user journey — it exists, I just haven't drawn the boxes yet
This site. Data as API, UI as client. 6-theme engine with cron-based rotation, developer mode, and interactive architecture diagrams.
// Problem
Generic portfolio sites show screenshots. Recruiters can't tell if you actually understand systems architecture.
// Solution
Modelled the entire portfolio as a typed schema. Developer mode exposes the data layer — git graphs, live system diagrams, and a mock terminal.
// not responsive enough for mobile.
// please rotate your device, or better yet,// open this on a laptop like a civilized engineer.
feat: 6-theme cron rotation engine
feat: developer mode toggle + context menu
feat: git graph SVG visualisation
merge: theme-engine -> main
// TODO: map the user journey — it exists, I just haven't drawn the boxes yet
// first version of my developer portfolio
// built while learning React and modern web tooling
// eventually replaced by a more system-driven approach
✓ Designed and shipped first personal site
✓ Learned React fundamentals by building with them
✓ Deployed to production
✓ Realized everything could be improved
✓ Rebuilt as Portfolio v2 with proper system architecture
Production EdTech platform serving educational videos to learners across India with 8-language support, OTP-based mobile auth, and a full content management admin dashboard.
// Problem
Rural and semi-urban learners across India couldn't access educational content because it wasn't in their language — and the platforms that had it required passwords, tech literacy, and a stable enough connection to not give up halfway through signup.
// Solution
Stripped auth down to OTP-via-SMS (no password, no email required). Offloaded all video storage to YouTube — zero bandwidth cost, trusted player, works on slow connections. React-Intl + database-stored translations cover 8 Indian languages. Admin dashboard via MUI DataGrid lets non-technical staff manage the full content tree without touching code.
// not responsive enough for mobile.
// please rotate your device, or better yet,// open this on a laptop like a civilized engineer.
feat: passwordless OTP auth — SMS via Fortius gateway → JWT
feat: YouTube Data API + React-Player integration
feat: 8-language UI — React-Intl + per-language tutorial videos
feat: admin dashboard — MUI DataGrid CRUD for modules/chapters/videos
fix: OTP expiry from 5min → 10min for rural SMS latency
infra: CloudFront CDN + GitHub Actions CI/CD pipeline
merge: all features → main
// TODO: map the user journey — it exists, I just haven't drawn the boxes yet
Multi-platform vendor onboarding system (web + Flutter mobile) for NCEL's export operations. Multi-step form, email OTP verification, S3 document uploads, and an admin review dashboard.
// Problem
NCEL was collecting vendor export interest through paper forms, emails, and phone calls. Submissions got lost. Nobody knew what stage anything was at. Staff spent more time chasing documents than evaluating vendors.
// Solution
4-step web form with email OTP verification gates document uploads — no spam, only verified vendors reach S3. Admin panel gives staff full pipeline visibility: filter by status, attach internal notes, trigger SES emails, and track every state change. Flutter mobile app means vendors in the field can submit from a phone without a laptop.
// not responsive enough for mobile.
// please rotate your device, or better yet,// open this on a laptop like a civilized engineer.
feat: 4-step vendor form — personal → OTP verify → products → documents
feat: S3 presigned URL uploads — direct browser-to-S3 transfer
feat: admin panel — DataGrid filtering, status lifecycle, internal notes, SES emails
feat: Flutter iOS/Android — BLoC pattern + SQLite offline storage
fix: OTP delivery variance — UI handling for 5s–30s delivery window
fix: S3 presigned expiry — client-side validation before upload attempt
merge: all features → main
// TODO: map the user journey — it exists, I just haven't drawn the boxes yet
Full-stack enterprise procurement platform handling ₹100cr+ annual transactions across 500+ vendors. Covers the entire procure-to-pay cycle: vendor onboarding, RFQ, purchase orders, inward processing, invoice matching, and bulk payments.
// Problem
₹100 crore moving through spreadsheets, phone calls, and paper POs across 5 departments and 500+ vendors. No audit trail. No way to know if an invoice matched the delivery. Bulk payment runs done manually, line by line.
// Solution
Full procure-to-pay digitisation: 9-step vendor registration with KYC/GST/PAN verification, competitive RFQ bidding, multi-level MD approval chains, inward processing with quality test workflows, 3-way invoice matching (PO vs. invoice vs. GRN), and bulk NEFT/RTGS payment generation. Lambda microservice handles all notifications via SQS so the main app never blocks on email delivery. Flutter app gives field teams offline-capable access with idempotency keys to prevent duplicate POs on bad connections.
// not responsive enough for mobile.
// please rotate your device, or better yet,// open this on a laptop like a civilized engineer.
feat: 9-step vendor registration — GST/PAN validation, KYC docs, bank details
feat: RFQ system — competitive bidding, vendor comparison, L1 selection
feat: inward processing — quality testing, rejection management, GRN generation
feat: 3-way invoice matching — PO amount vs. invoice vs. GRN quantity
feat: Lambda notification microservice — SQS queue, retry with backoff
feat: Flutter mobile — offline SQLite, idempotency keys, BLoC sync
fix: invoice rounding precision — BigDecimal validation before payment
fix: NEFT/RTGS bulk payment file format — exact bank spec compliance
merge: all features → main
// TODO: map the user journey — it exists, I just haven't drawn the boxes yet
Freemium SaaS for creating professional marriage biodatas. 12 templates, Razorpay payments, PDF generation, and Hindi/English support.
// Problem
Families creating marriage biodata had two options: hire a designer or use a generic Word template that looked like a tax form. Neither worked for people who needed something professional in 10 minutes for ₹0–₹99.
// Solution
Serverless pay-per-download SaaS: 12 React-PDF templates, EXIF-corrected photo upload, Hindi/English i18next forms, Razorpay checkout through Lambda[Order], signature-verified PDF unlock through Lambda[Verify]. Free templates stay free. Premium ones cost less than a cup of chai.
// not responsive enough for mobile.
// please rotate your device, or better yet,// open this on a laptop like a civilized engineer.
feat: Serverless Framework config + Lambda handlers
feat: Razorpay order + verify Lambda endpoints
feat: @react-pdf/renderer — 12 template layouts
fix: EXIF orientation on mobile photo uploads
feat: i18next Hindi + English — forms, labels, validation
merge: all features → main
// TODO: map the user journey — it exists, I just haven't drawn the boxes yet
Enterprise payroll SaaS for global HR service providers. Covers the full payroll lifecycle — employee self-service, time & attendance, compliance, and Base HR — across multiple countries and regulatory environments.
// what i worked on
- ▸React — built and maintained UI screens within the payroll platform
- ▸Groovy — updated India payroll tax calculations — deductions, slabs, and compliance rules
- ▸PostgreSQL — wrote queries for payroll reports including earnings summaries and deduction breakdowns
// context
Enterprise healthcare portal built on a micro-frontend architecture, supporting claims processing, pricing, and pharmacy workflows at scale. Contributed across ~30 micro frontends with primary responsibility for frontend features in business-critical modules and occasional backend/API bug fixes.
// key modules
- ▸Worked on a React-based claims processing UI using React JSON Schema Form (RJSF)
- ▸Added and maintained dual view modes (Basic and Advanced) for complex hierarchical claim data
- ▸Schema-driven validation, real-time data transformations, and integration with COB, AWP pricing, and external lookup services
- ▸Contributed to a standalone React web component for drug price comparison, packaged as a framework-agnostic custom element
- ▸Pharmacy search, price comparison, theming via CSS variables, and token-based auth
- ▸Supported multiple environments (dev, qa, eval, prod) with CI-friendly builds
- ▸Contributed to frontend work on a portal supporting the US 340B Drug Pricing Program — eligibility, pricing, and claim-related views
- ▸Short-term engagement (~3 months) within the broader PDMI platform, integrated with shared auth, APIs, and UI components
// context
// TODO: find a problem worth obsessing over
// idea definitely worth $1B (source: my brain at 2am)
// README.md created · implementation pending
✓ Had a shower thought at 2am
✓ Convinced self it's the next big thing
✓ Created README.md
~ Finding a problem worth obsessing over
○ Writing any actual code
○ Shipping
The Terminal
A real CLI wired to live data. Try theme list or git log.
// ↑↓ arrow keys for command history · theme changes apply to the whole page
Let's Build Something
Complex problems are welcome.
// response.time
< 8h
Faster than a production hotfix.
// preferred.contact
kumaryogesh4c8@gmail.com// availability
// social.links
Quick Pulse
3 questions. No text boxes. Results unlock on submit.
// who is reading this?
Runtime Telemetry
Live observability for this session. Interactions, theme changes, and system events stream here in real time.