Skip to evidence →
tanyasingh
← Back to evidence index
Exhibit A · Open

Evidence folder

MACH Headless Storefront

Client
Princess Auto · via EPAM
Role
Lead Software Engineer / Frontend Architect
Timeline
EPAM tenure · multi-year program
Team
Team · 14–18 engineers
65%Data-fetch latency cutQuery batching and caching strategy on the Next.js storefront path.
35%Less code duplicationShared packages and Storybook system across squads.

Objective

Stand up a greenfield headless commerce storefront on MACH principles — Next.js 15, shared monorepo, and integration rails durable enough for a multi-squad team shipping to a global catalog footprint.

Decision log

Choices under review — why they stuck, and what they cost.

  1. Decision 01

    Turborepo + shared UI package over per-squad apps

    WhyDuplication was already taxing velocity; a single design system and build graph was the only way 14–18 engineers could move together.

    TradeoffUpfront platform investment delayed some feature starts — paid back in duplication cuts and review speed.

  2. Decision 02

    BigCommerce + Constructor.io with Azure Service Bus pipelines

    WhyCommerce and search needed event-driven boundaries, not a monolith of sync calls in the storefront.

    TradeoffOperational complexity shifted to messaging contracts — worth it for isolation and scale.

  3. Decision 03

    Storybook as the contract surface (50+ components)

    WhyVisual + a11y review needed a shared source of truth before PR merge, not after production screenshots.

    TradeoffComponent discipline slowed cowboy UI — raised the floor for every squad.

What we built

  • Greenfield Next.js 15 storefront on MACH boundaries
  • Shared Turborepo monorepo and UI design system
  • Commerce, search, and messaging integration rails

Filed stack · Next.js 15 · TypeScript · Turborepo · BigCommerce · Azure Service Bus · Storybook

Panel observations · people

  • Obs. A

    Set monorepo and design-system standards the wider program adopted

  • Obs. B

    Mentored seniors into ownership of integrations and CI quality gates

  • Obs. C

    Ran technical reviews that optimized for teachable decisions, not gatekeeping

Discuss this kind of engagement → Contact