Frontend
Interfaces and admin panels that stay fast and clear when the data gets busy. Server-rendered and mobile-first by default, because most people arrive on a phone.
- TypeScript
- React
- Next.js
- Redux Toolkit
- Tailwind
- Framer Motion
// manifesto
I'm one developer who can take an idea from a rough sketch to a product that's running and holding up: the screens people see, the API and data behind them, and the servers it all lives on. For you that means fewer handoffs, fewer surprises, and one person who understands how the whole thing fits together. Bring me the problem, and I'll help you shape it, build it and keep it running.
// languages & tools
Interfaces and admin panels that stay fast and clear when the data gets busy. Server-rendered and mobile-first by default, because most people arrive on a phone.
APIs, auth, queues and data that keep working as more people show up. I shape the schema and the endpoints together, so they fit each other.
I set up the servers too: reverse proxy, process manager, CI/CD and test suites, so a release is routine instead of an event.
// a typical split team vs. one fullstack developer, per feature


// the pipeline
Mind Roots
SEP 2025 – PRESENT
A software services company, which is exactly why I joined: a new kind of product every few months, each one built end to end. So far that's a mobile guessing game with its backend and admin panel, a grocery list and recipe app, a gym trainer booking app with real-time changes, and a deep linking platform with custom domains and payments. Now I'm on Bless Me, a marketplace for booking online sessions with spiritual leaders. On each one I take a requirement from a rough idea to something running in production: the interface, the API, queues, servers, pipelines and tests.
Script Space
APR 2025 – AUG 2025
Hired to keep about 56 journal websites running on OJS. The bigger problem sat inside the company: customer relations, writing and finalizing teams passed work along through Excel sheets and WhatsApp, and something got lost at every handoff. I built a single CMS for all three teams on shared data, with roles, assignment and approve or reject steps, so work moves from one person to the next with a clear trail. Once it was stable the job became mostly upkeep, so I moved on to keep learning.
Grovyo
JUL 2024 – MAR 2025
An early-stage social commerce platform for India, meant to help local workers and home-based women sell handmade goods and grow as creators. I worked across the whole product from day one: a queue system and microservices, a continuous upload service, server tuning so videos play in different qualities, the platform's own ad system for creators, and the first seller page and web-page builder. When funding stopped, the team paused the product. They are good people and we still stay in touch.
// scroll sideways →
// notes from the build

Every developer has a late-night deploy that turns into a rescue mission. Those nights are why I started Devure: a place built on the belief that code should solve problems, not create new ones.

A walkthrough of Static Site Generation and Incremental Static Regeneration in a production-ready Next.js 15 blog, with real code and the practices that keep it fast and SEO-friendly.
// 4 steps, no magic
Functional and non-functional requirements first, then what to build first.
Key entities, APIs and data flow, kept simple enough to grow.
Short demos, tests from week one, optimized where it counts.
Deploy, monitor, fix. I stay on after go-live.