Post-Purchase Platform

Modernized a multi-tenant post-purchase experience spanning shopper pages, merchant customization, embedded account widgets, and its GraphQL backend.

Tech stack: Python · Django · GraphQL · Next.js · React · TypeScript · MySQL · Redis · AWS · SQS · Webpack
Operating context: Multi-tenant retail platform · 3M+ daily requests · 40M+ users
Role: Software Engineer, primary contributor after the initial product phase
Ownership: Feature ownership across the shared experience layer and its GraphQL integration after the initial product phase.

Selected ownership

Tracking history across the stack

Added shipment history across heterogeneous tracking-update paths by capturing meaningful status or location changes, mapping them through GraphQL, and rendering a responsive shopper timeline.

Update paths

Carrier API pollingWebhooksBatch EDI

Direct contribution

Capture changesstatus or location

Persist historyshipment event model

Expose historymapped GraphQL stages

Render timelineresponsive shopper UI

Multi-tenant experience and customization

Extended the shared post-purchase experience and its component-based customizer across tracking, privacy, navigation, accessibility, and structured merchant settings, preserving one product across retailer configurations.

Embedded account widgets

Built a separate Webpack and CDN delivery path for embedded account widgets, giving retailer account pages a stable integration contract while legacy and new experiences coexisted.

GraphQL query-path profiling

Profiled a slow shopper-order GraphQL request through its SQL work, then replaced repeated delivery lookups with one order-level fetch and an in-memory mapping while preserving legacy business rules.

The conceptual map provides system context. Highlighted areas and the records below describe direct work. Scale refers to the production environment, not components authored by one engineer.