Anubhab Debnath — Full-Stack Engineer

FS-2026 · Full-stack engineer · Kolkata, India

Rev 9b6d409

I design the part you see and build the part you don't — interfaces, APIs, auth, queues. One engineer, comfortable across the whole stack.

Open to full-stack roles — remote anywhere, on-site across India.

Fig. 01 — the family PC, still boots.
Clear history before shutdown.

title	Full-stack engineer
drawn by	Anubhab Debnath
checked by	Production traffic
scale	1 : 1
loc	22.57 N / 88.36 E
rev / date	9b6d409 / 2026-07-25
sheet	01 of 04

Selected work

SHT 02 – 04

SHT-02SembliaA testimonial platform for small teams — built alone, from database schema to sign-up form.Independent SaaS2026In dev SHT-03SpecordReads your NestJS source and writes the OpenAPI spec — without ever booting the app.Developer tooling2025OSS SHT-04LinkGuardFinds the dead links before your readers do — fast enough to live in CI.Async CLI2025OSS

Revision history — experience

This part gets revised

Web & mobile workflow design for the Agrishop product
Reusable interface standards across product surfaces
Mentored junior UI and graphic designers

Authentication & organization access end to end: JWT sessions, CQRS, RabbitMQ RPC and events, scoped guards, split user/org claims, membership, recovery and invitation flows
Took a VAPT report from red to green — CSP & HTTPS enforcement, input validation, session invalidation, Turnstile, dependency upgrades
Full-stack features across the Next.js frontend and NestJS services, against shared contracts
Built and Dockerized a role-based GIS land-digitization app — parcel mapping, survey capture, transfer workflows — for a national competition

B.Tech, Computer Science & Engineering — Adamas University, Kolkata, 2022–2026.

Bill of materials — capabilities

13 line items

Ref	Item	Function
U1	TypeScript	primary logic, both sides of the wire
U2	Next.js / React	the surface — server-rendered, accessible, fast
U3	NestJS / Node	APIs with contracts, guards and tests
U4	Python	tooling, automation, the occasional CLI
J1	REST / OpenAPI 3.1	the seam between systems, specified
J2	WebSockets	for when polling won't do
C1	RabbitMQ	buffered work that survives a redeploy
C2	Redis	hot state, deliberately disposable
K1	Auth / IAM	JWT, RBAC, sessions, org claims — the relay that decides
R1	Security	VAPT remediation — CSP, validation, rate limits
D1	PostgreSQL / Prisma	data that tells the truth
TP1	Testing & CI	unit, integration, GitHub Actions — 91 green in one repo alone
H1	Docker / AWS / Vercel	containers, pipelines, deploys

General notes — about

Read before assembly

01
I came in through the front door — UI design, 2023, sweating spacing and hover states. Then I wanted to know what happened after the click, and I followed the request down: past the component, past the API, into the auth checks and the message queues. I never really came back up.
02
These days I work on identity and access for an enterprise verification platform — sessions, permissions, invitation flows. The part of the product where being careful isn't a virtue, it's the job description.
03
Nights and weekends I build my own things: a SaaS, some developer tools. Owning a system end to end — schema, queues, billing, interface — is the fastest way I know to stay honest about what I actually know.
04
I've rebuilt git and a DNS server from scratch, on purpose. Understanding tools one layer down is how I stop being afraid of them.
05
Design taught me taste. Backend taught me consequences. I think good software needs an engineer who's felt both.

Interface — contact

Input expected

Let's build the whole thing.

I'm looking for full-stack work with a team that ships carefully — and I'm at my best owning a feature from the database to the interface. If that sounds like your project, my inbox is open.