Design System & Platform Engineering

Adim is a creative collaboration platform for TV and movie production. When I joined, the startup was moving fast but had no real design system — duplicated components, visual drift, messy Tailwind, and no Storybook standard. I built shared React components on Next.js and TypeScript, established Storybook and Tailwind discipline, and introduced FE process (PR template, regular FE-only meetings, proactive technical-debt identification) to ship more consistently with fewer preventable bugs.

Company product video — context for what Adim is, not a UI walkthrough of my work.

Product overview video

Title

Senior Front-End Engineer

Context

Cross-functional startup; primary FE owner of design system and team practices.

Scope

Design system and component library, Storybook, Tailwind refinement, marketing site redesign, and FE team process.

The product shipped fast but UI was duplicated and inconsistent — no shared component layer, undisciplined Tailwind, and no FE process to catch debt or align the team before it compounded.

• Design system and component library

  Problem

  Engineers rebuilt the same UI every sprint; screens drifted from each other and from design.

  Fix

  Shared React component library on Next.js and TypeScript — product screens import shared components instead of one-offs.

  Result

  A reusable UI layer the team could build on consistently.

• Storybook

  Problem

  No rigorous catalog for what polished UI looked like before it hit the app.

  Fix

  Storybook as the surface to set and review UI standards before shipping.

  Result

  Engineers built and reviewed interfaces against a shared catalog.

• Tailwind CSS

  Problem

  Utility styling was copied ad hoc with no shared conventions.

  Fix

  Streamlined and refined Tailwind across the platform on top of the component layer.

  Result

  Cohesive styling the team could apply the same way every time.

• FE team process

  Problem

  Inconsistent PRs, silent tech debt, and too little FE alignment slowed production and let bugs through.

  Fix

  PR template, regular FE-only sync meetings, and proactive identification of future technical debt.

  Result

  More cohesive FE team and fewer preventable issues — no velocity metric claimed.

• Marketing website

  Problem

  The marketing site didn't match the product's brand or feel current.

  Fix

  Redesigned it with a modern, intuitive interface.

  Result

  Stronger brand presence and a clearer first impression for users.

• Stakeholder documentation

  Problem

  Documentation gaps were stalling project flow.

  Fix

  Direct stakeholder communication to unblock docs and decisions.

  Result

  Work kept moving instead of waiting on unanswered questions.

Consistency and shipping speed improved for the FE team — fewer one-offs, clearer reviews, better alignment — but I don't claim a hard velocity number. In ~10 months I left foundation work: design system, Storybook, Tailwind discipline, and FE process that would outlast individual features.