About

The story is simple: I liked code early, then kept shipping harder things.

I am a software engineer from Kolkata with a cybersecurity background and a builder-first approach to software, from client products to code merged into Python, Node.js and Spring Boot.

Sumit Kumar Das

I first got pulled into programming in school when a teacher showed me a Java program. That moment changed how I looked at computers: they stopped being devices and became systems I could shape.

Today I work across backend, frontend, commerce, CMS, AI, cloud and security. I have handled Spring Boot, ASP.NET Core, FastAPI, Node, Nest, Next.js, Astro, React, Shopify, WordPress, October CMS, Laravel, Flutter, React Native and more.

The advantage is not just tool range. It is the ability to connect product goals with engineering choices: when to use queues, when to cache, when to split services, when to keep a system simple and when to harden it for scale.

Current direction: production-grade full-stack engineering with applied AI, cloud deployment, automation and security-minded delivery.

Profile

The professional version.

I build production-grade web, commerce, AI and security-aware systems. My work spans startup products, institutional platforms, CMS builds, ERP-style dashboards, cloud deployments and automation.

0 years building and shipping
0 brands and organisations reached
0 major open-source projects with merged code

Working style

Direct, technical and outcome-focused.

I like fast iteration, but I care about system health. The work has to survive after the handoff.

Understand the system

Start with the users, workflows, constraints and deployment reality. The first job is to remove ambiguity.

Build the narrowest working version

Ship the core path early, prove it with real data and avoid over-designing around imagined edge cases.

Harden for production

Add auth, logging, error handling, deployment automation, caching and security controls where the risk justifies it.

Iterate with evidence

Use metrics, user feedback and code health to decide the next improvement instead of guessing.