Skip to main content

Staff Frontend Engineer · Frontend Architect

Aayush Singh

I architect frontend systems that outlive their original teams — 11+ years setting the patterns, build systems and standards that other engineers build on, across regulated fintech and enterprise e-commerce.

View workDownload CV

Discipline

Frontend architecture, design systems, build & release

Domains

Regulated fintech · Enterprise e-commerce · Real-time 3D

Core stack

React · Next.js · TypeScript · GraphQL · NX

Based

Ghaziabad, India (IST) — open to anywhere

Status

Open — remote or relocation, worldwide

§ 01 — Evidence

Scope, in the units that matter

Every figure traces to a named engagement. Nothing here is self-scored.

1M+

Users reached

SigFig, via banking partners

5 / 12

Brands / locales

Goodyear NX monorepo

0

WCAG AA findings

Audited, not claimed

100K+

Designers served

Foyr, 30+ countries

§ 02 — Method

How I decide

Each position is paired with the work that earns it.

  1. 01

    Standards live in documents, not code review

    Code review catches one diff at a time. If a standard matters, it belongs in a design review and a written technical document that outlives the person who wrote it.

    Evidence

    At Publicis Sapient I presented solution designs for senior-architect review before rollout, and set implementation direction for other engineers in the pod through those documents rather than after the fact.

  2. 02

    Accessibility is a build-time guardrail

    WCAG AA is not a remediation pass scheduled before launch. It is a constraint you design to from the first component, which is the only way it survives contact with a deadline.

    Evidence

    Delivered an enterprise e-commerce platform with zero WCAG 2.1 AA audit violations — focus management and ARIA built into the shared components, not retrofitted.

  3. 03

    The best architecture is the one the team adopts

    I weight team familiarity and adoption cost as heavily as technical merit. An elegant pattern nobody sustains is a liability with good documentation.

    Evidence

    Chose Zustand over Redux Toolkit for the account domain because the ceremony would not have been sustained, then wrote the state-ownership guide so the decision held after I moved on.

  4. 04

    Diagnose before you choose

    Most architecture arguments are really unmeasured performance arguments. Find the actual cause first; the right tool is usually obvious once you have.

    Evidence

    Traced a re-render cascade across an account tree to Context identity churn before touching a state library — the migration was the consequence of the diagnosis, not a preference.

  5. 05

    Build the layer other teams stand on

    Platform work is leverage. One correct shared foundation is worth more than five well-built features, because it decides how expensive the next hundred features are.

    Evidence

    Engineered NX monorepo infrastructure for 5 brands across 12 locales — CSRF protection, a GraphQL proxy keeping credentials server-side, React Query SSR — consumed by every delivery pod.

§ 03 — Case records

Selected work

Read as decision records: the constraint, what was rejected and why, what it bought.

Goodyear E-Commerce

US retail e-commerce platform · NX monorepo, 5 brands, 12 locales

goodyear.com (opens in a new tab)

Scope

Platform infrastructure and the full authenticated experience for Goodyear's US storefront on Next.js 15 — CSRF protection, a GraphQL proxy keeping service credentials server-side, React Query SSR with HydrationBoundary, and the authentication, account and order domains built on top of them.

Constraint & decision

Order Details had to serve three fulfilment types with divergent data models and financial rules. Conditional-rendering sprawl breaks down past two types and a shared mega-component is untestable, so each fulfilment owns its own calculation and UI contract against a common interface — a fourth type lands without touching the other three. Separately, a re-render cascade across the account tree traced back to Context identity churn; migrating to Zustand gave fine-grained subscriptions without the ceremony Redux Toolkit would have added.

Outcome

  • 5 brands · 12 locales
  • Zero WCAG 2.1 AA audit violations
  • 3 fulfilment types on one contract
  • Next.js 15
  • React 18
  • TypeScript
  • GraphQL
  • NX Monorepo
  • Zustand
  • React Query

Digital Wealth

Digital wealth-management & robo-advisory platform · 1M+ end users via banking partners

sigfig.com (opens in a new tab)

Scope

Core modules of a regulated wealth platform delivered through banking partners — schema-driven investment, suitability and regulatory questionnaires, employer-sponsored plan flows, brokerage funding, new-client onboarding, and a React-PDF proposal generator.

Constraint & decision

The shared core repo and the per-partner repos were developed and released separately, so every partner deploy needed manual release sequencing. I ran the R&D to run both from a single folder structure under Vite and rebuilt the CI/CD pipeline to drive them from one place — a partner deploy now triggers the core pipeline automatically. Separately, the questionnaire playback module hit a hard 100-object Contentstack ceiling; migrating from an object-based to an array-of-objects model removed the limit and restored scalable detail rendering.

Outcome

  • 1M+ end users
  • ~45% faster load times
  • 30% faster builds · 40% faster partner onboarding
  • React
  • TypeScript
  • Vite
  • GraphQL
  • React Hook Form
  • CI/CD
  • Jest / RTL

Neo

Browser-based real-time 3D interior-design platform · 100K+ designers in 30+ countries

neo.foyr.com (opens in a new tab)

Scope

The core user-facing application, built from scratch to production on Vue.js, Nuxt.js and Vuex — authentication, dashboards and every primary surface — for a platform that turns floor plans into 3D renderings and 4K walkthroughs in the browser.

Constraint & decision

The interaction layer and the rendering engine had to stay in sync in both directions without either owning the other's state. I designed a bidirectional middleware between Vue and Three.js: a property change in Vue — object height, say — invokes the engine to update the 3D/2D canvas in real time, and engine-side changes propagate back to the UI. A molecules-and-components design system built alongside it eliminated duplicate UI and became the shared vocabulary for feature teams.

Outcome

  • 100K+ designers · 30+ countries
  • ~30% faster 3D model loads
  • Design system built from scratch
  • Vue.js
  • Nuxt.js
  • Vuex
  • Three.js
  • WebSockets
  • Algolia
  • Design Systems
All projects
§ 04 — Capability

Depth, against a stated benchmark

Bands, not percentages — so the claim can be interrogated.

Architecture

  • Frontend ArchitectureExpert
  • NX MonorepoExpert
  • Design SystemsExpert
  • SSR / HydrationExpert
  • Multi-tenant & Multi-locale PlatformsExpert
  • Micro-frontendsAdvanced
  • System DesignAdvanced

Core Frontend

  • React.jsExpert
  • Next.js 15Expert
  • ZustandExpert
  • React QueryAdvanced
  • Vue.js / Nuxt.jsAdvanced
  • ReduxAdvanced
  • React Hook FormAdvanced
  • Tailwind CSSAdvanced
  • Material UIAdvanced
  • StorybookAdvanced

Graphics & Motion

  • Canvas / 2D RenderingExpert
  • Three.js InteropAdvanced
  • Real-time Sync (WebSockets)Advanced
  • Animation & Motion SystemsAdvanced
  • Parallax & Scroll ChoreographyAdvanced
  • SVGAdvanced

Languages

  • TypeScriptExpert
  • JavaScript (ES6+)Expert
  • HTML5 / CSS3 / SASSExpert

Platform & Quality

  • ViteExpert
  • Git / GitHubExpert
  • Jest / React Testing LibraryExpert
  • WCAG 2.1 AA AccessibilityExpert
  • Performance OptimizationExpert
  • CI/CD PipelinesAdvanced
  • WebpackAdvanced
  • DockerWorking
  • AWSWorking

APIs & Backend

  • REST API DesignExpert
  • GraphQLAdvanced
  • Node.jsAdvanced
  • Express.jsAdvanced
  • MongoDBWorking
  • Firebase / SupabaseWorking
Expert
Production-proven at scale, with architectural responsibility
Advanced
Shipped features and reviewed others' work
Working
Used in real projects, not a primary focus
§ 05 — Track record

Eleven years, no gaps

  1. August 2025 - March 2026

    Contract

    Lead Frontend Engineer (Senior Experience Engineer)

    Publicis Sapient — client: Goodyear

    Engineered the platform infrastructure behind an NX monorepo serving 5 brands across 12 locales — multi-locale/brand API configuration, CSRF protection, a GraphQL proxy keeping service credentials server-side, and React Query SSR with HydrationBoundary — shared foundations consumed by every delivery pod.

  2. January 2025 - August 2025

    Independent

    Career Focus Period

    Independent — Frontend & GenAI Engineering

    Went deep on GenAI engineering — Model Context Protocol, Claude Code, LLM workflow design and prompt engineering — and shipped QuizKode, an AI-powered quiz platform on Next.js and TypeScript with real-time code evaluation.

  3. March 2022 - January 2025

    Full-time

    Software Development Engineer 2 — Frontend

    SigFig

    Re-engineered the local-development and release layer so the shared core repository and the per-partner repositories run from a single folder structure under Vite, then rebuilt the CI/CD pipeline to drive both from one place — deploying a partner repo now triggers the core pipeline automatically, removing manual release sequencing.

  4. July 2021 - March 2022

    Full-time

    Web Development Engineer II

    CoreValue Technologies

    Built a React.js merchant dashboard with real-time analytics that let e-commerce merchants compose dynamic, personalized storefront content, lifting engagement 35%.

  5. April 2019 - July 2021

    Full-time

    Senior Frontend Developer

    Foyr (RBJ Technologies)

    Designed a bidirectional middleware between the Vue interaction layer and the Three.js engine: a property change in Vue — object height, for instance — invokes the 3D engine to update the 3D/2D canvas in real time, and engine-side changes propagate back to the UI.

Full history

Open to Staff / Principal and architect roles

Based in Ghaziabad, India (IST) and open to anywhere — fully remote, or relocation with visa sponsorship. Hours overlap European afternoons and US mornings.

Get in touchEmail directly