Skip to content

About me

I’m a backend-focused software engineer building reliable systems at the intersection of distributed backends and AI. My work centers on designing clean APIs, scalable data pipelines, and RAG systems that solve real operational problems.

Introduction

I am a senior Electronics and Instrumentation Engineering student at the National Institute of Technology, Silchar (CGPA: 8.83) building high-performance full-stack systems at the intersection of distributed backends and AI.

Alongside my academic studies, I am an active competitive programmer and a Knight on LeetCode (Peak Rating: 1888, 700+ solved). I am also passionate about open-source security, having recently patched a critical path traversal vulnerability in the file jail check of the PocketPaw project.

What I do

I focus on turning complex technical specifications into reliable, scalable digital products. That means defining clear API schemas, implementing robust event-driven message architectures, designing context-aware RAG pipelines, and integrating rich real-time frontends.

  • Full-Stack Engineering & Architecture
  • RAG pipelines & high-throughput vector search
  • API design, WebSockets, & event-driven queuing
  • System performance, concurrency, & observability

Technical Skills

Languages

TypeScriptJavaScriptPythonC++SQLGolang

Fullstack

Next.jsNode.jsExpress.jsWebSocketsReactRabbitMQDockerPrometheusGrafana

AI & RAG

LLM PromptingRAG PipelinesVector SearchEmbeddings (Gemini)Pinecone

Databases

PostgreSQL (Prisma)MongoDBRedis

Core CS

Operating SystemsComputer NetworksDBMSData Structures & Algorithms

What I believe in

Systems should be boring in production. Predictability beats cleverness, and explicit tradeoffs beat magical abstractions.

Architecture is about constraint management. Clear boundaries and data contracts reduce bugs more effectively than endless testing.

Measure reality. Logs, metrics, and traces matter more than opinions when systems start failing under load.

Who I work with

I work best with teams that value engineering discipline — founders and engineers who care about system correctness, not just shipping features fast and fixing them later.

Backend engineers
Product-focused teams
AI & platform teams

How I approach problems

  1. Understand the failure modes first — what breaks under scale, latency, or bad data.
  2. Design explicit interfaces and data models before writing code.
  3. Build async-first where blocking becomes a liability.
  4. Instrument early, iterate based on evidence, not assumptions.

Open to opportunities

I’m open to backend, platform, and AI-infrastructure roles where system design and reliability actually matter. If you’re building something non-trivial and want an engineer who thinks in systems, reach out.

Let's Connect

Always interested in new opportunities, collaborations, and conversations about technology and design.