Arvind RatheeDeveloper & curious humanBack to selected work

Government SaaS · 2024–2026

Making complex workflows easier to evolve.

Rebuilt legacy workflows in React and helped grow a shared frontend library used across a suite of applications.

  • React
  • TypeScript
  • Nx
  • Vite
  • Redux Toolkit
  • RTK Query
  • TanStack Query
  • TanStack Router
  • React Hook Form
  • Chakra UI
ProjectVimo

Context

Vimo’s child care platform supported complex operational workflows across a suite of applications. My work ranged from shared frontend components to modernizing individual modules.

My role

Frontend development, technical planning, component-library contributions, and mentoring as part of a larger engineering team.

The challenge

The legacy Ticketing module combined interdependent search filters, nested requests, and conditional actions in an undocumented JSP application. Its behavior had to be understood and preserved while moving to React.

The approach

  • Traced the existing interface, request dependencies, and business rules before rebuilding the module in React.
  • Worked with backend engineers to simplify the request graph, defer noncritical data, and remove unused response data. The backend team implemented its own changes.
  • Expanded a shared component library, including form controls and accessibility checks. The library was a team effort and was used by approximately 15 applications by the time I left.
  • Later developed an AI-assisted migration workflow informed by the earlier manual migrations, and guided delivery and review on subsequent modules.

Outcome

Ticketing’s initial load time improved by approximately 30%, based on before-and-after browser network timings. The migration workflow was associated with an estimated 50% reduction in per-screen effort, based on level-of-effort comparisons rather than a controlled study.

Shared foundations

Vimo’s Child Care Exchange supported parents, childcare providers, and state agencies. I joined an existing Nx monorepo in March 2024 and spent my first months growing its shared Chakra UI component library.

I built and improved form controls, their error presentation, and accessibility checks alongside the team. Approximately 15 applications consumed the shared form components by my departure; I did not build all of those applications.

Understanding and modernizing legacy workflows

I manually traced undocumented JSP applications before rebuilding features in React. For Announcements, I integrated a reusable Lexical rich-text editor with formatting, lists, links, and other controls.

Ticketing included interdependent search filters, results, exports, and actions. I mapped its request dependencies, rebuilt the frontend, and worked with backend engineers on API simplification and deferred requests. Browser network timings showed approximately 30% faster initial loading.

Architecture suited to the application

I contributed to a move from Redux Toolkit and RTK Query conventions toward TanStack Query and TanStack Router where a broad global store was unnecessary. The choice reflected the application’s needs, while keeping local state local and leaving room for Redux where appropriate.

A reusable AI-assisted migration workflow

After researching coding assistants and observing repeated manual migration work, I developed a staged workflow that evolved from tool hooks and rules into reusable agent skills. It analyzed legacy behavior and target architecture separately, then produced an implementation plan for developer review before generating code and tests.

The workflow also used Playwright to check application behavior, followed by developer review and manual verification. An approximately 50% reduction in estimated per-screen effort was based on before-and-after level-of-effort comparisons, not a controlled study.

Entity and Agency

Entity was the first complete migration using the structured workflow. I refined it in practice while guiding two developers, assigning work, reviewing changes, and helping with onboarding.

For Agency, I combined architecture, implementation, estimation, reviews, and guidance for one developer. I completed the migration before leaving on 13 November 2026.

Debugging and team-wide influence

After a React 19 upgrade caused a production-only third-party library crash, I traced minified code and corrected a dependency-resolution configuration so the team could stay on the new version.

I also proposed a parallel specialist-agent architecture for a project-specific code-review workflow. Other developers implemented it and its later CI integration; the adopted workflow was used by approximately 30 frontend developers.