Fig. 00 · Manohar Kumar · Lead Frontend Engineer · Gurgaon, IN

Frontend,
drawn to scale.

Nine years of interfaces engineered like structures — microfrontends, design systems, and the tooling that keeps teams shipping. Currently leading frontend on Netomi's AI customer-service platforms, Heimdall and Studio.

Manohar Kumar
Fig. 01 — The architectScale 1:1
09+
years shipping frontend
05
companies, Capgemini → Netomi
12
enterprise tenants on Heimdall
30%
faster loads at erosnow.com
Sheet 02  ·  Revision history

Every revision shipped.

Chronological, as a drawing logs its revisions. The current issue is at the bottom — where drawings keep it.
RevIssue

Role-based dashboards for GE clients using PolymerJS and the Predix Framework.

  • Built a role-based dashboard to streamline machinery part management for GE clients.
PolymerJS · Predix · Dashboards

Data aggregation at scale — scraping scripts and headless browsers for financial histories.

  • Built robust scraping scripts using Puppeteer / headless browsers for transaction histories & account verification.
Puppeteer · Node · Automation

Rebuilt erosnow.com on a modern SSR stack; shipped a keyboard-navigable HTML5 TV app.

  • Migrated erosnow.com from a legacy PHP system to a VueJS SSR platform.
  • Profiled and fixed performance bottlenecks — 30% improvement in load/render times.
  • Built a keyboard-navigation-enabled HTML5 TV Web App with React for smart TVs.
VueJS SSR · Performance · React · Smart TV · A11y

AI/ML-driven insurance submission tickets — workflow dashboards and a full Vue 2 → Vue 3 migration.

  • Designed a role-based dashboard for AI/ML submission tickets, improving ticket lifecycle visibility.
  • Led the Vue 2 → Vue 3 migration, improving performance, scalability and maintainability.
Vue 3 · Vuex · Role-based UI · Migration

Leading a frontend team building AI customer-service platforms. Architected the next-gen microfrontend app in React 18 + Next.js.

  • Led architecture of a next-gen microfrontend app using React 18 & Next.js — independently deployable modules.
  • Spearheaded Heimdall — a complex no-code flow platform with loops, conditional branching and dynamic nodes, built on ReactFlow + Codemirror.
  • Ran bi-weekly knowledge-sharing sessions for a period; mentored engineers and drove hiring.
  • Partnered with PMs, UX and backend across Studio, Chat Widget, Multi-Channel Platform.
React 18 · Next.js · Microfrontends · ReactFlow · Codemirror · Design systems
Sheet 03  ·  Drawings

The drawings.

Four systems from production, drawn as shipped. Simplified for the sheet; load-bearing in real life.
Heimdall flow diagramTriggerClassify intentBranchReplyEscalateLog eventEndheimdall/flow
Fig. 02HeimdallNetomi · 2024
Fig. 02
Heimdall

A no-code flow platform for building intricate AI data flows — loops, conditional branching, dynamic nodes. Think Figma, but for customer-service automation.

Role
Architecture & lead implementation
Impact
Zero-downtime launch across 12 enterprise tenants
Stack
React 18 · ReactFlow · Codemirror · Zustand · TypeScript
Studio composer layoutconversation.tsx
Fig. 03StudioNetomi · 2023
Fig. 03
Studio

The composer surface agents use to build, test and publish AI conversations. Built on a shared microfrontend shell with independently deployable modules.

Role
Tech lead · design-system owner
Impact
3× faster release cadence post-migration
Stack
Next.js · Microfrontends · Shadcn · Storybook
Streaming grid
Fig. 04erosnow.com — SSR rebuildEros Now · 2020
Fig. 04
erosnow.com — SSR rebuild

Re-platformed a legacy PHP streaming site onto a modern VueJS SSR stack. Profiled and removed the long tail of layout & render thrash.

Role
Senior engineer
Impact
30% faster load & render
Stack
VueJS · SSR · Vuex · Lighthouse
TV app layoutFeatured
Fig. 05HTML5 TV AppEros Now · 2020
Fig. 05
HTML5 TV App

A keyboard-navigable streaming app for smart TVs. Spatial focus management, large-type UI, and a remote-first navigation model built to feel native.

Role
Frontend engineer
Impact
Shipped to 5 OEM partners
Stack
React · Spatial nav · A11y
Sheet 04  ·  General notes

Read before building.

Every drawing set carries general notes: the rules that apply to all sheets. These apply to all teams I run.

I'm Manohar — today I spend my days in React 18, Next.js and ReactFlow at Netomi. Before that I lived inside a Vue codebase at Eros Now, wrote scrapers at Finicity, and started my career writing PolymerJS at Capgemini back in 2016.

The through-line is systems: component libraries that make the right thing easy, microfrontend architectures that let teams ship independently, and review habits that raise the floor without flattening the ceiling.

Outside code, I've always cared about team craft — running reviews, mentoring, and for a while hosting Frontend Darbar, a bi-weekly forum where we shared what we learned, what broke, and what we were trying next. Favourite kind of meeting.

  1. N-01
    Code reviews

    Rigorous, kind, specific. PRs are where team culture is built.

  2. N-02
    Ship velocity

    Fewer meetings, better tooling, stronger defaults.

  3. N-03
    Design systems

    One Button, one Input, one Dialog. The rest is garnish.

  4. N-04
    Hiring

    Engineers I'd follow — interviews focused on taste, curiosity, and rigor.

Sheet 05  ·  Bill of materials

The toolkit, itemized.

Things I use most. I care less about the stack and more about the rigor of the reasons behind it.
01ArchitectureMicrofrontends · SSR · Performance profiling · Design systems · Modular designIn service
02FrameworksReact 18 · Next.js · VueJSIn service
03StylingSCSS · CSS Modules · Tailwind · MUI · ShadcnIn service
04PerformanceLighthouse · React Profiler · Vite · Bundle analysisIn service
05StateRedux Toolkit · Zustand · Recoil · VuexIn service
06BackendNodeJS · GraphQL · Strapi · SupabaseIn service
07CI/CDGitHub Actions · Docker · Kubernetes · VercelIn service
08TestingStorybook · Chromatic · Jest · React Testing LibraryIn service
09Past lifeAngular · PolymerJS · NestJS · Webpack · Jenkins · GitLab · Core JavaRetired
Sheet 06  ·  Issue

Issued for construction.

I'm happiest building product with thoughtful teams — and always up for a good conversation about microfrontends, design systems or the craft of shipping. Whether you want to trade notes, collaborate on something, or just say hi: the inbox is open.

Open to: advisory · freelance · good problems