Senior Frontend Engineer

I design and ship reliable frontend systems for enterprise-scale products.

5+ years across micro-frontend architecture, performance optimization, analytics correctness, and production reliability. Current focus: platform-level frontend engineering.

Read Case StudiesGet in TouchGitHubLinkedIn

Experience

Technical case studies from production systems

American Express (via Cognizant) · Global Search

Micro-Frontend Tenancy Migration

Problem

Search UI lived under MYCA tenancy in OneApp. Release cadence was coupled to another team's root module, analytics executed late, and legacy SAN + Iguazu dependencies increased system drag.

Constraints

High traffic surface, strict rollout safety, cross-team tenancy dependencies, and no tolerance for analytics loss during migration.

Architecture Diagram

Before:
[Client] -> [OneApp MYCA Shell] -> [Search MFE]
                        -> [Late Analytics Init]
                        -> [SAN + Iguazu Coupling]

After:
[Client] -> [Global Search CNAME]
         -> [Dedicated Root Module]
         -> [Dedicated Search Tenancy + Pods]
         -> [Early Analytics Init]
         -> [Decoupled Release Lifecycle]

Decisions

  • Led 6-month migration to dedicated tenancy.
  • Provisioned new root module, clusters, and pods.
  • Skipped SAN/Iguazu inheritance to avoid framework bloat.
  • Designed CNAME-based domain switch + subdomain routing.
  • Reordered analytics initialization to remove blind spot.

Outcome & Lessons

  • Eliminated ~10s analytics tracking gap.
  • Decoupled release cycles from external root ownership.
  • Improved operational reliability via isolated tenancy.
  • Documented migration path and mentored junior engineer.

American Express (via Cognizant) · Partner Servicing Portal

Enterprise Onboarding Platform

Problem

Multi-step partner onboarding workflows, lifecycle dashboards, and large-scale card art management required high performance and strong accessibility in an enterprise environment.

Decisions

  • Applied workflow-driven state management patterns.
  • Migrated tests from Enzyme to React Testing Library.
  • Owned feature delivery during tech lead absence.
  • Prioritized perf + a11y + security together.

30%

Performance improvement

45%

Accessibility improvement (WCAG)

60%

Vulnerability reduction

Project

ForexFix: deterministic finance logic with LLM-assisted guidance

ForexFix is a travel FX intelligence product built with Next.js App Router, TypeScript, Supabase, and Gemini. The core engineering decision: deterministic financial math stays in code; LLM output is restricted to narrative strategy.

System Diagram

[Client (RSC + UI)]
        |
        v
[Next.js App Router]
   |            |
   |            +--> [API Route: LLM Narrative Layer]
   |                        |
   |                        v
   |                  [Gemini Model]
   |
   +--> [Deterministic FX Engine]
                |
                v
       [Supabase Postgres + Cache]
                |
                v
          [Strategy Response]

Why this architecture

  • Numeric correctness cannot depend on model variability.
  • LLM is used for explanation quality, not calculations.
  • Caching strategy is cost-aware and latency-aware.
  • App Router keeps server/client boundaries explicit.

Stack

  • Next.js 15+ App Router
  • React + TypeScript
  • Supabase (Postgres + caching)
  • Gemini for narrative strategy generation
  • Vercel deployment
Live ProductRepository

Technical Philosophy

Architecture first. Framework second.

Design for failure modes

Production reliability is a design decision, not a post-launch patch. I design for rollout safety, blast radius control, and clear rollback paths.

Observability is product quality

If analytics and telemetry are late or incorrect, product decisions become guesswork. Correct instrumentation is part of the core feature, not an add-on.

Performance is architectural

I prioritize boundaries, loading strategy, and state ownership before micro-optimizations. Most performance wins come from system shape, not tiny tweaks.

Own outcomes, not tickets

I take architectural accountability: tradeoff decisions, implementation quality, team alignment, and production behavior.

Contact

Open to senior frontend and platform engineering roles.

If your team is building high-scale frontend systems and values architecture, observability, and reliable delivery, I'm happy to talk.

EmailLinkedInResume