Software Engineer
Started in Surat. Owned the front-end of FUOTA — a SaaS for remote IoT firmware updates, with an Electron client to match.
Frontend engineer, AI-native by default. I take high-fidelity Figma files and render them into pixel-perfect, performant, animated web — now with Claude and OpenAI living in the UI layer, without losing the soul of the design.

For 4+ years I've been building the user-facing layer of products that have to actually work — from a self-funded PaaS dashboard to a Contentful platform powering six brands to a jewellery storefront with realtime variant selection. I obsess over the seam between design intent and shipped UI.
I work in TypeScript, Next.js, React, Redux/Zustand. I write motion in GSAP and Framer Motion. I've shipped Strapi, Contentful, and Algolia integrations end-to-end, instrumented funnels with GA4 / GTM / Meta CAPI, and built an Electron client UI for secure IoT firmware uploads. I'm most useful to teams that take both design and engineering seriously.
Each role earned the next. The camera holds on each chapter for a beat — scroll to advance.
Started in Surat. Owned the front-end of FUOTA — a SaaS for remote IoT firmware updates, with an Electron client to match.
Self-funded PaaS. Took the front-end from idea to production-grade — dashboard, billing UI, and internal-monitoring views.
A Next.js mono-repo + Contentful platform powering 6+ brands from a single codebase, with custom CMS apps powering the editorial workflow.
Shipping a full-scale jewellery e-commerce — PDPs with realtime variants, optimistic cart + wishlist, admin lifecycle.
Tech stacks tell you what someone has touched. The bars below tell you what they can actually do.
Vertical scroll moves the panel horizontally — the page is the camera, the work is the scene.

PDPs with metal / size / purity variants, optimistic cart + wishlist, admin dashboard for the full product lifecycle, GA4 + Meta CAPI tracking.

Centralised mono-repo + Contentful CMS, dynamic page variants for GA4 A/B tests via middleware, custom Contentful apps that cut publishing delays by 70%.

GitHub-connected dashboard, project/service collaboration UI, resource-control views for servers / DBs / Redis / workers, billing + partner-program flows, internal-monitoring views.

Web portal for device registration, real-time transfer-log UI, Electron client for secure uploads, scheduled-update flow.

Step-by-step wizards, mandatory field validation, real-time previews — all inside a Next.js host environment.
Drag the handle. The Figma file on the left, the shipped page on the right. Same composition, same easing curves, same eyes.
Existing PaaS tools threw every knob at the user up-front — server type, runtime, env vars, secrets, scaling — so first deploys took hours, not minutes.
I rebuilt the front-end as a multi-step deploy flow: connect GitHub → pick a repo → confirm runtime → allocate resources → ship. Every step has a single primary action; everything else lives behind progressive disclosure.
User effort dropped 95% on common deploy paths. Billing + partner-program flows brought deployment cost down 90%. The internal-monitoring dashboard made oncall meaningfully calmer.


Four steps. Same shape every time, different details every project.
I read the file like a spec — every spacing token, every easing curve. I write down the questions before I write code.
Component graph, state ownership, motion plan. I'd rather spend a day here than three days untangling later.
Motion is the carrier wave for meaning. Every transition has a job: hierarchy, continuity, or delight — never decoration.
Lighthouse green on every commercial route. INP under 200ms. Image budgets enforced in CI. The fast version is the only version.
Move your cursor. Eighteen-by-ten lines, each pointing toward you, weighted by distance. Sixty lines of canvas, ~120 lines of math, zero dependencies.
Every section on this page has at least one of these — a small interaction that earns its place.
Sourced from teammates across four companies — names redacted as placeholders until I have written permission to publish.
He has the eye of a designer and the discipline of a senior engineer. The launch we ran in Q1 hit every milestone two weeks early.
I sent Abhishek Figma files and he sent back live URLs that looked like the file. That's the value. He fixed our brand site in three weeks.
Ships fast, ships clean, and the engineers we have in-house come away from every collab having learned something.
Selective collaborations. Two-week minimum, three-month sweet spot. I reply within a working day.
abhi1234kumbhani@gmail.com[ click to copy ]