Role: Lead UX Designer

Responsibilities: Collaborated with PMs and engineers to understand backend constraints and customer use cases. Then, I mapped out user journeys and pain points to design a new interface that allows users to define flexible cost allocation rules using common traffic attributes such as source account, destination account, or flow 5-tuple. I prioritized making rule creation intuitive, even for non-technical users.

Duration: 6 months

Users & Audience: Cloud Finance teams, Network Engineers, Account Administrators in large multi-account AWS orgs

Problem: In AWS Transit Gateway, data transfer costs are always billed to the source attachment owner. This rigid structure frustrated customers—especially large organizations—who wanted the flexibility to charge costs to other teams or accounts based on who initiated the traffic, the destination, or the service. Without this, companies had to maintain their own internal billing reconciliation systems.

Solution: Designed a rules-based interface where users can:

• Choose which conditions (e.g., source/destination attachment, 5-tuple) trigger billing behavior

• Assign cost responsibility to a specified account based on those conditions

• View and manage all allocation rules from a central location