About the role
About Sapiom AI agents are beginning to act on behalf of companies and users — making purchases, spinning up compute, triggering workflows, and interacting with third-party systems. But today's financial infrastructure was built for humans, not autonomous systems. Companies and developers need a way to give agents controlled access, meter actions, monetize usage, and transact across rails, without rebuilding payments, risk, and compliance internally. Sapiom builds the financial payments infrastructure for the machine economy - autonomous spend rails that enable AI agents to transact with real-world services safely, processing every dollar spent, every policy decision navigated, and every risk signal generated. We have assembled a world-class team with deep payments and infrastructure DNA to build the operating system for machines. Backed by a $15.75M investment from Accel, Menlo, and Anthropic, we are moving with relentless focus to deploy the economic substrate for autonomous agents.
About
the Role Financial infrastructure for autonomous agents is a design problem as much as an engineering one — the surfaces we build determine whether developers trust the system, understand what's happening, and can move fast without breaking things. This role sits at the center of that challenge: shaping how complex, high-stakes transaction flows become interfaces that feel inevitable. The right person is a systems thinker who's equally comfortable pushing pixels and pushing back on product assumptions. What You Will Do Own the end-to-end design process across Sapiom's core product — from early discovery and
requirements gathering with Product, through iterative visual design, to guiding implementation with Engineering. You'll work across the hardest UX challenges in agentic commerce: spend controls, policy configuration, real-time risk visibility, developer-facing APIs, and the dashboards that make autonomous financial activity legible to the humans overseeing it. You'll help define Sapiom's design language as it matures — knowing when to use the system, when to evolve it, and when to break it deliberately. The goal: software that earns developer trust on first use and deepens it every time.
