PramanikFull Stack Developer
Get in touch

Open to full-stack roles

RamkantaPramanik

TypeScript · React · Next.js · NestJS · Node.js · AWS

Full stack developer building production healthcare and e-commerce systems in TypeScript, NestJS and Next.js. I care about the parts users never see — the schema, the validation layer, the webhook that has to be right the first time.

See the workEmail me
Role
Software Developer, Full Stack
Company
InfluxIQ Tech
Based
Kalyani, West Bengal, IN
Focus
Secure APIs · Payments · Cloud
  • REST endpoints shipped
  • Admin modules built
  • Production domains
  • Engineers in team
TypeScriptReactNext.jsNestJSNode.jsExpressZodTanStack QueryTailwind CSSshadcn/uiNextAuth.jsTypeScriptReactNext.jsNestJSNode.jsExpressZodTanStack QueryTailwind CSSshadcn/uiNextAuth.js
PostgreSQLMongoDBRedisAWS LambdaCognitoS3ECSStep FunctionsDockerTerraformGitHub ActionsRazorpayPostgreSQLMongoDBRedisAWS LambdaCognitoS3ECSStep FunctionsDockerTerraformGitHub ActionsRazorpay
§ 01Approach4 principles
Ramkanta Pramanik, full stack developer at InfluxIQ Tech in Kalyani, West Bengal, India
Fig. 00Ramkanta Pramanik — Full Stack Developer

I build the layer that has to be right.

I am Ramkanta Pramanik, a full stack developer based in Kalyani, West Bengal, and a Software Developer at InfluxIQ Tech since June 2025. Healthcare records on one platform, live payments on another. Both are domains where a quiet bug is worse than a loud one — so validation, access control and reconciliation are where I spend my attention, not where I clean up afterwards.

I work across the whole stack — React and Next.js interfaces, the NestJS and Node.js APIs behind them, and the Docker and GitHub Actions pipelines that ship them. The four ideas below held on every system I have shipped, and each names the artefact it actually produces, because a principle you cannot point at in the repository is just a preference.

  1. 01

    Auth and validation come first

    JWT, role checks and Zod schemas go in before the handler exists — not bolted on after a review flags them. Every one of the 70+ endpoints I shipped carries them from its first commit.

    Guards · Zod schemas

  2. 02

    Model the data before the routes

    Schema, relationships and the shape of every payload get settled up front. On the appointment system that meant booking, cancellation and record states were designed as one model, not three features.

    Migrations · Mongoose

  3. 03

    Money needs a reconciliation path

    A payment integration is not the checkout call — it is the webhook signature check, the retry, and the reconciliation that catches the order the callback never reached. Zero payment inconsistencies post-launch.

    Razorpay webhooks · FSM

  4. 04

    Releases should be uneventful

    Build, test, migrate and roll out automated in GitHub Actions, services containerised on ECR/ECS. A deploy stops being a decision and becomes a merge.

    Docker · GitHub Actions

Based in
Kalyani, West Bengal, India
Education
B.Tech, Computer Science & Engineering
JIS College of Engineering, Kalyani · Aug 2020 — Jun 2024
Working style
Five-person team, two-week sprints
API contracts, design review, PR review
§ 02Capability58 technologies

The stack, grouped by the job it does.

Nothing here is aspirational — every line is load-bearing somewhere in the work below. Pick a layer to see what it covers.

Typed end to end — the same types travel from the database row to the button.

  • TypeScript
  • JavaScript (ES6+)
  • SQL
  • HTML5
  • CSS3
§ 03ExperienceInfluxIQ Tech · 2025 →

Shipping production systems since day one.

Two roles at the same company — a three-month structured programme, then full ownership of API contracts across two production domains.

Jun 2025 — Present

Current

Kalyani, West Bengal, India

Software Developer, Full Stack

InfluxIQ Tech

  • Architected and delivered 70+ REST endpoints in NestJS and Node.js across healthcare and e-commerce systems, applying JWT authentication, role-based access control and Zod input validation on every route from day one.

  • Built a patient appointment and management system on MongoDB, with S3 presigned-URL uploads for secure document storage and AWS Cognito handling authentication and session tokens — covering booking, cancellation and patient record workflows.

  • Integrated Razorpay across a production Next.js platform — checkout sessions, webhook signature verification, refund triggers and order-state reconciliation — with zero payment inconsistencies reported post-launch.

  • Containerised services with Docker on ECR/ECS and maintained GitHub Actions pipelines covering build, test, migration and rollout, cutting manual release steps significantly.

  • Collaborated in a five-person team on two-week Agile sprints, owning API contracts, joining design discussions and reviewing pull requests to keep the codebase consistent.

Mar 2025 — May 2025

Kalyani, West Bengal, India

Trainee Software Developer

InfluxIQ Tech

  • Completed a structured three-month programme, building and testing React/Next.js front-end features and NestJS API modules alongside senior developers, following the team’s Git and sprint workflows.

  • Gained production-grade exposure to PostgreSQL schema design, REST API conventions and cloud deployment practices before moving into a full developer role.

Environment
  • TypeScript
  • Node.js
  • NestJS
  • React
  • Next.js
  • AWS
  • Docker
  • PostgreSQL
  • MongoDB
  • Git
  • Agile/Scrum
§ 04Selected work1 case study

E-commerceCase study

Full-Stack E-Commerce Marketplace

An end-to-end storefront and operations suite — customer surface, payment rail and a 15+ module admin dashboard — built on Next.js 16 App Router with server components and server actions throughout.

  • Next.js 16
  • MongoDB
  • Razorpay
  • Redis
  • NextAuth v5
  • ImageKit
  • Brevo
Type
Personal project
Surface
Storefront + admin
Auth
NextAuth v5, role-based
Rail
Razorpay + COD
Fig. 01Order and return state machine — guarded transitions only
PlacedConfirmedPackedShippedDeliveredCancelledrefund queuedReturnedpickup raisedRefundedbank / UPI logged
01

Architecture

Next.js 16 App Router with server components as the default and server actions for mutations, so most pages ship no client JavaScript at all. NextAuth v5 provides role-based authentication across two distinct surfaces — customer and admin — from a single session model.

02

Payments and refunds

Razorpay wired with webhook signature verification, plus Cash on Delivery, GST-inclusive pricing and a manual bank/UPI refund tracking workflow that covers both order cancellations and returns. Order and return status changes run through an FSM-guarded transition table, so an order can never reach a state it has no path to.

03

Operations dashboard

A 15+ module admin suite spanning orders, returns, refunds, CMS, coupons and settings — API-driven tables with faceted filters, date-range search, paginated CSV export and KPI analytics.

04

Performance and delivery

Guest-to-database hybrid cart and wishlist sync so nothing is lost at sign-in, Redis read caching with tag-based invalidation, ImageKit for CDN-backed media, and Brevo for transactional email.

Admin surface

15 modules, one permission model

  • 01Orders
  • 02Returns
  • 03Refunds
  • 04Coupons
  • 05CMS
  • 06Catalogue
  • 07Inventory
  • 08Customers
  • 09Shipping
  • 10Taxes
  • 11Reports
  • 12Analytics
  • 13Reviews
  • 14Banners
  • 15Settings
§ 05ContactOpen to full-stack roles

Have something that needs
building properly?

I am open to full-stack roles and contract work — particularly anything with a real payment rail, a permission model, or a schema worth arguing about. Fastest reply is email.

ramkantapramanik9679@gmail.comLinkedIn
Email
ramkantapramanik9679@gmail.com
Phone
+91 96796 97440
LinkedIn
ramkanta-pramanik
GitHub
github.com/ramkanta
Facebook
ramkanta.p.2025