Team Lead & Senior React / Next.js engineer based in Kanpur, India. 4 years shipping production React at Fluid AI. Open to full-time roles and freelance engagements — say hi if you're hiring or building.
— what I build with —
I'm Tarun. I've been writing React for about four years — long enough to have strong opinions about folder structure, short enough that every new Next.js release still feels exciting.
These days I work on a platform that lets enterprises run their own AI assistants. The kind of app where one bad render costs someone's afternoon, so I've learned to care about caching, re-renders, and the small decisions that compound across a hundred screens.
The web still feels like a playground if you let it.
On the side I build with whatever new AI SDK looks interesting — recently a Interactive Avatar with HeyGen, and a Gen-AI Chat with voice in and out.
A mix of what I work on full-time and what I tinker with after hours.
An AI workspace for the enterprise crowd
The platform I spend most of my workdays in — a multi-tenant AI workspace with a knowledge base, chat, and a visual workflow editor. I owned the frontend architecture, made it on-prem-friendly, and got page loads down by roughly 80% with smarter caching.
A canvas for chaining AI actions together
A chatbot product used by 50+ teams
One-click installs inside the platform
Four years at one company, three different roles, a lot of late nights.
Owning a big chunk of the Fluid GPT frontend — performance, multitenancy, and the move to on-prem deployments. Most days are equal parts code, code review, and arguing about state-management patterns.
Got the cloud app running fully on-prem so enterprise clients can host it inside their own networks.
Replaced ConfigCat with a custom tenant-level feature-flag system that reads from env vars at boot.
Migrated to RTK Query and watched API calls drop ~85% and page loads improve ~80% on the heavy modules.
Spent way too long getting the Playwright suite to run reliably on tenant-aware fixtures. Worth it.
Four areas I keep returning to. Hover any chip for a bit of context.
Pixels, motion, and the parts users feel.
APIs, sockets, auth — the moving parts.
Code from machine to production.
Habits, not just tools.
Roles, freelance gigs, side-project collabs, or just a hello — I read everything and usually reply within a day.