The marketplace experience expanded into 20+ international seller accounts and cross-border operations, with responsibility spanning listings, inventory, advertising, account health and repeatable workflows.
Scale stopped being one-dimensional
Operating internationally was not simply a larger version of one account. Each marketplace brought different catalog requirements, policies, customer expectations, inventory decisions and advertising conditions.
Managing many accounts required standardization: repeatable checks, cleaner data, clearer ownership and better ways to identify where an operation needed attention.
From doing the work to designing the work
As operations expanded, the job increasingly became designing processes that other people and systems could execute consistently. That meant templates, checks, workflows and eventually automation.
This period is where the later title “systems architect” began to make sense. The work was no longer only ecommerce execution; it was deciding how ecommerce execution should operate at scale.