About

More about the person behind the commits

Full-Stack & Backend Engineer in Bengaluru, India. I care about systems that stay understandable after the people who built them have moved on.

I started out building full-stack features — React on top, Node and Mongo underneath — and kept drifting toward the seam between them. At Workoi that meant rebuilding the core web architecture and the UX around it. At SwiffyLabs it became the Backend-for-Frontend layer, which I designed as an intern prototype and now own end to end.

Today that work is gRPC and HTTP microservices, payloads shaped for the screen that asked for them, Keycloak handling SSO and MFA, and Swagger contracts written before the code. Alongside it I lead delivery on a consumer durables lending product and run the unglamorous half — multi-tenant onboardings, release pipelines, and production migrations that finish without anyone noticing.

Outside of that I build things I want to exist: a calendar app with a Spring Boot backend, an incident dashboard that outgrew its brief, and a badminton scorer that works without signal — the last one is not a coincidence. I play, including a turn at the SaaSBoomi Badminton League at the Dravid-Padukone Centre. Most of the rest is on GitHub.

GitHub LinkedIn Email

Toolkit

TypeScriptJavaScriptReact.jsNext.jsReact NativeNode.jsExpress.jsgRPCREST APIsMicroservicesBFF ArchitectureJavaSpring BootPostgreSQLMongoDBKeycloakDockerTailwind CSSSwaggerC++

Facts

Based in: Bengaluru, India
Timezone: Asia/Kolkata
Status: Open to new opportunities
Email: chandan.sm.dev@gmail.com

Years shipping production systems

25%

Engagement lift from a UX rebuild

15%

Faster sprint delivery after CI/CD work

Zero

Downtime on production migrations

The experience

Roles that shaped how I build

The short history — what I owned, and what changed because of it.

Jul 2026 — Present
Jul 2026 — Present
Software Development Engineer 1
SwiffyLabsCurrent
Bengaluru, India
Own the Backend-for-Frontend layer and lead delivery on a consumer lending product.
- Architected and owned the end-to-end Backend-for-Frontend layer using gRPC and HTTP microservices, optimising payload structures and reducing latency.
- Served as engineering and product lead for the Consumer Durables Loan product, managing end-to-end feature delivery and core API integrations.
- Spearheaded multi-tenant onboardings and streamlined deployment pipelines for minor and major frontend UI releases.
- Planned and executed critical production data migrations and database schema updates with zero downtime.
Node.jsTypeScriptgRPCREST APIsPostgreSQLMicroservices
Oct 2025 — Jun 2026
Oct 2025 — Jun 2026
SDE Intern
SwiffyLabs
Bengaluru, India
Prototyped the BFF layer that later became the platform.
- Designed the initial BFF service prototypes to decouple frontend clients from core backend microservices.
- Implemented Keycloak authentication with SSO and MFA.
- Defined Swagger API contracts and optimised data-fetching latency.
Node.jsKeycloakSwaggerREST APIs
Sep 2023 — May 2025
Sep 2023 — May 2025
SDE Intern
Workoi
Remote
Full-stack feature work on a consumer web product.
- Developed and maintained scalable full-stack features using React.js, Node.js and MongoDB.
- Revamped core web architecture and UX, boosting user engagement by 25% and reducing bounce rates.
- Streamlined Git workflows and CI/CD pipelines, cutting sprint delivery timelines by 15%.
React.jsNode.jsMongoDBGitCI/CD

Education

Where the fundamentals came from

Lovely Professional University

Sep 2022 — Jul 2026

B.Tech Honours in Computer Science (Software Product Engineering)

Jalandhar, PunjabCGPA 9.07

Certifications

Create a no-code responsive website with WebflowCoursera · Jul 2024
Mathematical ThinkingCoursera · Oct 2023
Learning How To LearnCoursera · Jan 2023

How I work

Four things I keep coming back to

Contract before code

I would rather spend an afternoon on a Swagger spec than a week reconciling two teams’ assumptions. The argument is cheap on a document and expensive in a sprint review.

Migrations nobody notices

Schema changes go out in small reversible steps against live traffic. If a release needs a maintenance window, the plan was wrong a fortnight earlier.

Own it end to end

Scoping, API design, delivery, the release itself. Handing work over at the ticket boundary is how things arrive late and slightly wrong.

Keep the client light

The frontend should be presentational. Every piece of data transformation I can pull back into the BFF is one less thing three clients have to reimplement.

Open to new opportunities