Frontend systems for real customer journeys
Customer-facing ecommerce at Victoria’s Secret & Co. — the React product-page experiences that stand between a person and the thing they came to buy. Presented as a capability study, not a claim about one confidential product.
Company
Victoria’s Secret & Co.
Role
Front End Web Developer
Period
Dec 2023 → present
Surface
Digital commerce, at scale
01 · Context
IndexChapter 01
Context
A product detail page looks simple and is not. It is the point where inventory, pricing, sizing, imagery, fulfilment promises, accessibility law, marketing experiments, and analytics all have to resolve into one screen that loads fast on a phone with two bars of signal. Get it wrong in a small way and a person quietly leaves.
Chapter 02
Frontend ownership
What I own, end to end.
Product-page experiences
React interfaces for discovery and purchase confidence — how availability, sizing, and fulfilment are presented, and how the page behaves as a customer changes their mind.
End-to-end feature ownership
From technical discovery through production: UI behaviour, state handling, the edge cases nobody wrote a ticket for, and the release itself.
Experimentation & analytics
Features built to be A/B tested, instrumented so the result is measurable, and shipped with the discipline to actually read the outcome.
Reusable frontend patterns
Cleaner component logic and improved test coverage so the next feature is cheaper than the last one.
Chapter 03
The customer journey
A sanitized view of the states a product experience has to handle. Step through it — the interesting engineering lives in the states nobody mocked up.
Discover
A customer arrives at a product from search, browse, or a campaign, and forms a first impression in one screen.
States the frontend handles
- Loading
- Image gallery
- Deep link
- Low bandwidth
Chapter 04
Frontend challenges, honestly
- Accessibility is not a checklist item. Size pickers, image galleries, and availability messaging have to work with a screen reader and a keyboard, on desktop and on mobile. This is the part of the job I care most about getting right.
- Performance is a customer experience. Every kilobyte and every layout shift is a tax on someone’s patience and someone’s data plan.
- State is where the bugs live. A page reflecting a live inventory system has more states than the design file shows, and the interesting engineering is in the ones nobody mocked up.
Chapter 05
Collaboration model
Features move through Product, UX, QA, Backend, and Analytics before they reach a customer. Cross-functional delivery means the frontend engineer is often the person who notices that three of those groups have different assumptions about the same edge case — and says so early, when it is still cheap.
Lessons
What it taught me
- At scale, small frontend details are big business. A confusing size selector is not a design quibble.
- Ownership is mostly communication with a deadline attached.
- Experimentation replaces argument with evidence — the same instinct that made me publish datasets rather than claims.