Home About
About
I build backend infrastructure and the interfaces that make it legible. Currently finishing a computer science degree in Jammu while working as a software engineer intern at Opus Wealth, remote-first.
The short version
Eight roles across fintech, robotics, developer education, and distributed commerce; a three-person team led; twelve microservices co-architected; four juniors mentored; one company founded before graduation.
Most of what I know arrived after the ticket closed: read the source, rebuild the thing, write the note. The note is the proof of understanding. If I cannot explain a decision with the code closed, I probably did not make it — I watched it happen.
The dictionary version: Java full-stack engineer, React / Next.js specialist, comfortable owning a service end to end — schema, queue, deploy, dashboard, and the paragraph in the README that explains why.
At a glance
- Based
- Jammu, India · IST, remote-first
- Currently
- Software engineer intern, Opus Wealth
- Studying
- B.Tech CSE, 2023—2027
- Founder
- 100xSystems
How I work
Four rulesMake the boundary obvious before the abstraction.
A module that cannot explain what it owns will eventually own everything. I start with the contract — an interface, a schema, a documented queue — and only then earn the abstraction. On the A2B platform that meant RBAC rules written before the screens that needed them.
Write the runbook before the launch.
If it needs a dashboard, it also needs a sentence that tells the next person what a healthy version looks like. The Prometheus, Grafana, and Loki stack at A2B shipped with a doc that was half numbers, half plain language — 99.95% uptime is a claim because the definition of down was written down.
Optimise the loop, not the demo.
LocalStack instead of a shared cloud, seeded data instead of screenshots, tests that fail for a reason. A sixty percent cut in cloud test cycles came from making the feedback loop local and boring. The loop is the product; the demo is a photograph of it.
Leave the note.
Every project gets a README a stranger can follow, every strange decision gets a paragraph, and every internship ends with documentation nobody paid for. Memory is a cache, not a database. The writing you are reading is the same habit, pointed outwards.
Skills
Languages
Java · JavaScript (ES6+) · TypeScript · Python · C / C++ · SQL · Bash · Kotlin · Dart · Lua
Backend
Spring Boot · Node.js · REST APIs · Microservices · Hibernate · Flyway · JTE · Thymeleaf · OpenHtmlToPdf
Cloud & infrastructure
AWS EC2 · AWS RDS · AWS S3 · AWS SQS · AWS SNS · API Gateway · LocalStack · Docker · Nginx · Firebase Auth · Supabase
Data & monitoring
PostgreSQL · Turso (libSQL) · MySQL · Redis · Prometheus · Grafana · Loki · Axiom
Frontend & mobile
Next.js 15 · React · Tailwind CSS · Three.js · SolidJS · GSAP · React Flow · Storybook · Chromatic · Flutter
AI & automation
RAG · LLMs · OpenRouter · Groq · Mistral AI · Meta Graph API · n8n · Activepieces · Zapier
DevOps & testing
JFrog Artifactory · Jenkins · GitHub Actions · Vitest · JUnit 5 · JaCoCo · OpenAPI / Swagger · Ink · Pastel · AT Protocol
Foundations
System design · Microservices · Data structures & algorithms · Operating systems · Computer networks
Education
Mahant Bachittar Singh College of Engineering & Technology
B.Tech in Computer Science · Affiliated with the University of Jammu · CGPA 8.2 / 10.0
Competitions
Self-Balancing Robot
Built an LQR controller and automated CoppeliaSim kinematics with Bash, achieving sub-120ms balance recovery.
Python · Lua · CoppeliaSim · LQR · Bash
Dementia Detection System
Architected a Flutter mobile interface and REST telemetry APIs processing 1,000+ data points per second.
Flutter · Dart · REST APIs
Let's talk.
Free mentorship calls are open on Topmate for students and early-career engineers. For hiring or collaboration, email is the fastest route.