Sr. Product Designer, Payments

Zapier•San Francisco, CA

8d•Remote

About The Position

Customers shouldn’t have to guess what they’re being charged for—or why. Today, understanding subscription costs, usage-based billing, and invoice details can feel opaque. Our job is to change that by designing experiences that help customers understand, trust, and verify how they’re charged over time. As a Product Designer for the Revenue zone focused on Payments, you’ll design how customers see and interact with billing across the product: how they pay for subscriptions and usage, how they track and interpret what they’re being charged for, and how they manage settings, invoices, and credits. You’ll work across self-serve and Enterprise billing workflows so that everyone—from individual automators to large organizations—has clarity and control. You’ll partner with product, engineering, and design peers to shape billing-aligned usage tracking (including Usage Insights and billing-related reporting), usage notifications and threshold moments, and billing settings (taxes, currency, credits, invoices). Your work will directly answer the question customers ask most: “What am I being charged for, and why?”

Requirements

You’re a product designer with 5–7 years of experience. You’ve shipped end-to-end design work and are comfortable owning design from discovery through to implementation and iteration.
You care about clarity and trust in financial UX. You’re motivated by making complex billing, usage, or subscription information understandable and actionable—whether in self-serve flows or enterprise contexts.
You’re comfortable with data-heavy and settings-heavy experiences. You can design for usage reporting, thresholds, invoices, and billing settings without overwhelming users, and you think in systems (tables, filters, notifications) as well as single screens.
You collaborate closely with PM and engineering. You ask good questions, align on constraints (e.g., billing systems, tax rules), and iterate based on feedback and research.
You’re curious about both self-serve and Enterprise needs. You’re willing to learn how billing differs for individual customers vs. large organizations and to design for both when the product does.