Building at Chain

BarathKumar

Senior Software Engineer 3 · Chain·Coimbatore, India

I build interfaces worth obsessing over. Design systems, motion, and a frontend that is a feature, not an afterthought.

See what I've built
Barath Kumar, grinning in sunglasses on a beach at night
that's me, say hi

01/About

Simple on the surface. Obsessive underneath.

the short version

I'm a senior software engineer who cares about the last 10% — the spacing, the easing, the empty state nobody designed. That's usually where a product starts to feel like a product.

At Chain I lead the UX and Enablement team. I migrated our v1 app to a Next.js v2 that took Lighthouse performance from 70 to 95 and First Load JS from 1.5 MB to 200 KB, and built the design system the product now ships on.

Outside work I contribute to open source (kody.video, thesysdev/openui, Magic UI), give talks on motion and AI agents, and write about design systems.

Off the clock: I love Messimy wife (corrected to: my wife) more than Messi.(she proofreads this site)

SpeakerOpen-source contributorDesign systems5+ years shipping
non-negotiables

What I care about

  • Design systems that teams actually adopt
  • Motion with intent, never decoration
  • Performance you can feel, not just measure
  • Accessibility as the default, not a pass
  • Shipping the whole thing — design to deploy

02/Work

Things I've built, shipped or said out loud.

7 so far

Client sites built end-to-end, merged open-source PRs, an AI agent harness, and a talk about motion. Chain work lives in the Journey below.

Sree Krishnaa Property Developers screenshot

01 · Client site

Sree Krishnaa Property Developers

A real-estate platform for residential and commercial properties, built end-to-end from design to deployment.

What shipped

A property browsing experience that stays fast on Indian mobile networks, with image-heavy pages tuned for LCP.

  • Next.js
  • TypeScript
  • Tailwind CSS
Sakunthala Girish & Associates LLP screenshot

02 · Client site

Sakunthala Girish & Associates LLP

A chartered accountancy firm's site that has to communicate trust, expertise and a full spread of tax services.

What shipped

A calm, accessible information architecture with Radix primitives and restrained Framer Motion so the content leads.

  • Next.js
  • Radix UI
  • Framer Motion
merged ×2

03 · Open source

kody.video — two merged PRs

Contributions to Kent C. Dodds' kody.video: an accessibility fix for the share sheet, and validation hardening for backup import.

What I learned

Reading an unfamiliar codebase fast, writing PRs a maintainer can merge without a second round, and testing the edge case first.

  • React
  • TypeScript
  • a11y
  • Validation
merged

04 · Open source

thesysdev/openui — IME-safe composer

A merged fix to OpenUI's generative-UI React components: both chat composers stopped submitting on Enter while an IME composition (CJK and other input-method typing) was still open.

What I learned

Keyboard input is not one event. Checking isComposing before acting on Enter is the difference between a chat box that works for everyone and one that eats half a sentence.

  • React
  • TypeScript
  • i18n
  • Keyboard a11y
6 branches

05 · Project · Talk

bratcode — an AI coding-agent harness

A personal coding agent on a local LLM via Ollama, about 600 lines of TypeScript with no framework, built one capability per git branch: constrain, inform, verify, recover. Demoed live at React Meetup #108.

What I learned

The model is the engine, not the car. Permissions, memory and verification are what make an agent safe to let near a codebase.

  • TypeScript
  • LLM
  • Ollama
  • AI agents
on stage

06 · Talk

Lights, Camera, Framer Motion

A conference talk on animation techniques with Framer Motion — deliberate motion design for the web.

What I learned

Explaining easing and orchestration to a room means cutting everything that doesn't move the story forward.

  • Framer Motion
  • Motion design
  • React
long-form

07 · Writing

Technical articles on Medium

Essays on frontend engineering, design systems, and the craft of building for the modern web.

Why I write

Writing something down is the fastest way to find out whether I actually understand it.

  • Design systems
  • Frontend
  • Craft

03/Journey

Version history.

each role, a release

Every role shipped a new version of me. Open an entry to see the changelog.

  1. nowTodaycurrent

    Leading UX & Enablement at Chain

    Latest: the design system the product ships on, the Next.js v2 migration, bratcode, and merged contributions to kody.video and openui.

  2. v3.0May 2024 — Present

    Senior Software Engineer 3 · Chain

    • Lead the UX and Enablement team to raise product quality and velocity.
    • Migrated the v1 app to a Next.js v2 — Lighthouse 70 → 95, First Load JS 1.5 MB → 200 KB.
    • Built a new design system on Tailwind CSS and shadcn/ui.
    • Contribute back through blogs, talks and open source.
    • Next.js
    • TypeScript
    • Tailwind CSS
    • shadcn/ui
    • Design systems
  3. v2.0May 2021 — Apr 2024

    Frontend → Senior Software Engineer · Assembly

  4. v1.0Jan 2021 — Apr 2021

    Software Engineering Intern · Assembly

  5. v0.12020

    Fresh out of college

    Learned to ship, walked into Assembly as an intern, and earned the full-time seat.

04/Toolkit

What I reach for.

go on, drag them around

The stack I build products with today. Grouped, because context matters more than a logo wall.

Languages

  • TypeScript
  • JavaScript
  • HTML
  • CSS

Frontend

  • React
  • Next.js
  • Tailwind CSS
  • Framer Motion
  • Zustand
  • Radix UI
  • shadcn/ui

Quality

  • Playwright
  • Storybook

Tooling

  • Vite
  • Git
  • Vercel

Design

  • Design Systems
  • Figma

everything is where it should be.

05/Say hi

Let's talk.

i actually reply

Interesting problems, design systems, motion, speaking, or just a hello after a talk. Email is the fastest way in.