Amiya Krishna Chaurasiya — Software Engineer
Backend-Leaning Full Stack Engineer • REST APIs • System Design • PostgreSQL • MongoDB • Queues & Workers

Amiya Krishna Chaurasiya

🎓 B.Tech (3rd Year) 💼 Open to Internship 📍 Lucknow, India

_

I design and ship backend systems, not just UIs — relational schemas with proper indexing and constraints, JWT/cookie-based auth, queue-driven background workers, rate limiters, and fuzzy-matching pipelines. Three production-grade full-stack builds later: a Next.js platform with a weighted recommendation engine, a Socket.IO real-time forum, and a job tracker with a BullMQ/Redis worker fleet doing scraping, deduplication, and TF-IDF matching. I build things that have to actually run under load, not just demo well.

🟢 Available for Software Engineering Internship (Immediate Joining)
3
Full Stack Systems Shipped
30+
REST Endpoints Designed
2
Relational + NoSQL DB Schemas
1
Queue-Based Worker Fleet (BullMQ + Redis)
✓ JWT / Cookie Authentication ✓ Relational Schema Design (Prisma + PostgreSQL) ✓ NoSQL Modeling (MongoDB + Mongoose) ✓ Background Workers & Job Queues (BullMQ, Redis) ✓ Real-Time Systems (Socket.IO) ✓ Rate Limiting & Fuzzy Deduplication
whoami.sh

$ whoami

Amiya Krishna Chaurasiya — B.Tech CSE, 3rd Year

$ stack --backend

Node.js · Express · Next.js API routes

PostgreSQL + Prisma · MongoDB + Mongoose

BullMQ · Redis · Socket.IO

$ systems --built

✓ Weighted recommendation engine

✓ Real-time WebSocket forum

✓ Queue-based job matching pipeline

$ status

✓ Open to Backend / Full Stack Internships

$ _

Quick Overview
My Resume

Software Engineering Profile

Backend-leaning Full Stack Developer focused on APIs, data modeling & systems that scale

✔ B.Tech Engineering Student

✔ Backend-Leaning Full Stack Developer

✔ Node.js • Express • Next.js Route Handlers

✔ PostgreSQL • Prisma ORM • MongoDB • Mongoose

✔ JWT/Cookie Auth • REST API Design • Zod Validation

✔ Background Workers • BullMQ + Redis • Socket.IO

✔ 3 Production-Level Full Stack Systems

✔ Actively seeking Backend / Full Stack Internship

Download Resume
Who I am

I design the parts of an app users never see — schemas, queues, and APIs — and make sure they hold up.

My three main projects each forced a different backend problem: Collexa — College Decision Intelligence Platform needed a relational schema with cascade-safe joins and a configurable scoring engine; the discussion forum needed real-time state synced across sockets and a REST API at the same time; and the job tracker needed a queue-based worker system — BullMQ jobs, Redis rate limiting, TF-IDF + fuzzy-match deduplication — running as a separate process from the API so a scraper crash can't take the whole app down. I'm currently deepening DSA and system design so the next thing I build scales further than the last.

🎯

Focus

API design, relational modeling, background job systems

📐

Quality

Indexed schemas, validated inputs (Zod), documented APIs

🚀

Goal

Backend/full-stack roles building systems that run under real load

🧠
Backend & APIs
Node.js · Express · Next.js Route Handlers · REST design · Zod validation · JWT/cookie auth
🗄️
Data & Persistence
PostgreSQL · Prisma ORM · MongoDB · Mongoose · schema design & indexing
⚙️
Systems & Real-Time
BullMQ · Redis (queues + rate limiting) · Socket.IO · worker processes
📊
Data Engineering
Pandas · NumPy · TF-IDF & Jaro-Winkler matching
Portfolio
Selected Work

Tap any project for the full case study — problem, solution, architecture, and proof. GitHub data pulled live via the GitHub API.

Job Application Tracker dashboard Featured · Live Demo
01

Job Application Tracker — Ingestion, Matching & Analytics Engine

ProblemSpreadsheets don't scale past a handful of job applications, and manually matching listings to a profile wastes hours.

SolutionReact/Vite + Express + PostgreSQL (Prisma ORM) tracker extended with a BullMQ/Redis worker fleet: jobs arrive via manual entry, Gmail inbox scanning, a Manifest V3 browser extension, or a live discovery API, then get deduplicated (TF-IDF + Jaro-Winkler), scored by two matchers, and semi-automated through Playwright — feeding a live per-user analytics dashboard, all as a process fully separate from the API.

React 19 + Vite Express 5 PostgreSQL + Prisma BullMQ + Redis Playwright
View full Job Application Tracker case study
College Discovery search & filter page Live Demo
02

Collexa — College Decision Intelligence Platform

ProblemComparing colleges and predicting admission rank means digging through scattered PDFs and outdated sites.

SolutionNext.js 16 + Prisma/PostgreSQL platform with a weighted rank-prediction engine, filters, side-by-side comparison, and Zod-validated APIs behind HTTP-only JWT cookie auth.

Next.js 16 TypeScript Prisma PostgreSQL Zod
View full Collexa case study
Community Discussion Forum dashboard Live Demo
03

Real-Time Discussion Platform (WebSocket Architecture)

ProblemCommunities are usually forced to choose between async threaded discussion and live chat — splitting the two kills context.

SolutionMERN + Socket.IO platform merging both: persistent threads, live messaging with presence/typing indicators, @mentions, and DB-persisted notifications.

React 18 Express MongoDB Socket.IO JWT
View full Discussion Platform case study
Capabilities
Tech Stack
Frontend
React.js Next.js TypeScript JavaScript HTML5 CSS3 Tailwind CSS
Backend
Node.js Express.js REST APIs JWT Authentication Socket.IO Rate Limiting Queues & Workers
Database & Data
PostgreSQL MongoDB Prisma ORM Schema Design Indexing Deduplication TF-IDF Matching
Tools & Deployment
Git GitHub Docker Postman VS Code Vercel Render
Under the hood
Engineering Depth

The backend decisions behind the three projects above — APIs, data modeling, and systems, not just UI.

🔌 APIs

  • 30+ REST endpoints across auth, resource CRUD, search, comparison, recommendation, and analytics
  • Zod-validated request bodies on College Discovery's route handlers
  • Consistent auth pattern: JWT in HTTP-only cookies (College Discovery) vs. bearer-style token header (Forum, Tracker)
  • Server-side AI proxy route (Groq) so API keys never reach the client

🗄️ Database Design

  • Relational schema (PostgreSQL + Prisma) with indexed lookup fields, cascade-safe deletes on Course/Review, and a unique (userId, collegeId) constraint on saved colleges
  • NoSQL schema (MongoDB + Mongoose) for the forum's Users/Posts/Comments/Notifications with reference-based relations
  • Job Tracker: one Postgres instance, via Prisma, shared by the original tracker schema and the new matching-engine tables

🏗️ System Architecture

  • API and background-worker processes fully decoupled (BullMQ + Redis) in the Job Tracker for fault isolation — full reasoning in its case study
  • WebSocket layer (Socket.IO) running alongside a REST API for hybrid real-time + persistent state
  • Middleware-centralized access control in Collexa — detail in its case study

⚡ Performance & Reliability

  • Job Tracker: Redis token-bucket rate limiting plus exact-hash + fuzzy (Jaro-Winkler/TF-IDF) deduplication — detail in its case study
  • Collexa: single-use expiring password-reset tokens and global Prisma Client reuse in dev to avoid connection churn — detail in its case study
Problem solving
DSA & Competitive Programming

Actively building this up alongside project work. Numbers below are placeholders until profiles are linked.

Writing
Technical Blogs

Planned write-ups on the systems behind the projects above — placeholders until published.

🛠 Coming Soon

Building a Queue-Based Job Matching Engine with BullMQ & Redis

How the Job Tracker's worker fleet decouples scraping, deduplication, and scoring from the API — and why that matters when a Playwright scraper crashes.

Draft in progress
🛠 Coming Soon

Fuzzy Deduplication: Jaro-Winkler + TF-IDF in Practice

Why exact-hash deduplication isn't enough for scraped job listings, and how combining title similarity with description similarity cuts down false positives.

Draft in progress
🛠 Coming Soon

JWT in HTTP-Only Cookies vs. Bearer Tokens: What I'd Pick Now

Comparing the auth pattern I used in College Discovery against the header-token pattern in my other two projects, and the tradeoffs I'd reconsider.

Draft in progress
Open source footprint
GitHub Highlights

Live data pulled from the GitHub API for my top repositories.

Job Application Tracker — Ingestion, Matching & Analytics Engine

JavaScript

The most complex repo in my profile — a job tracker extended with a dedicated BullMQ/Redis worker fleet. See the Projects section above for the full breakdown.

React Express 5 PostgreSQL + Prisma BullMQ

Collexa — College Decision Intelligence Platform

TypeScript

College decision platform with a weighted rank predictor and Groq-backed AI guidance chat. See the Projects section above for the full breakdown.

Next.js 16 Prisma PostgreSQL Zod

Community-Discussion-Forum

JavaScript

MERN + Socket.IO platform merging threaded discussions with real-time chat. See the Projects section above for the full breakdown.

React 18 Express MongoDB Socket.IO

What I'm Looking For

Currently seeking internship opportunities where I can contribute, learn, and grow as a Software Engineer.

🌐

Backend / Full Stack

Node.js, Express, Next.js, PostgreSQL & MongoDB — designing APIs, data models, and background systems.

📍

Work Preference

Open to Remote, Hybrid, and On-site internships across India.

🚀

Availability

Available to join immediately, based in Lucknow, India.

Journey
My Timeline
2024
Started Web Development
2025
Built 3 Full Stack Applications
2026
Preparing for Software Engineering Internships
📚

Currently Learning

Currently improving my backend development skills with Docker, Redis, System Design, authentication, API optimization, and scalable application architecture to prepare for Software Engineering internships.

Docker Redis System Design JWT Auth REST APIs AWS Basics
Let's connect
Open to Software Engineering & Full Stack Internships

Let's Build Something Together

I am actively seeking Software Engineering and Full Stack Development internship opportunities. Feel free to reach out for internships, collaborations, or technical discussions.