> Markdown version of [/jobs/ext/4324858-staff-software-engineer-full-stack-agentic-payment](https://www.wearedevelopers.com/jobs/ext/4324858-staff-software-engineer-full-stack-agentic-payment). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Staff Software Engineer, Full Stack (Agentic Payment) - **Company:** Sapiom, Inc. - **Location:** San Francisco, CA, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Shopify, TypeScript, Large Language Models, Agentic-AI - **Published:** October 25, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=042440220b778574 ## About the Role * You have 8+ years building production software, several of them in payments, money movement, or financial infrastructure. We're hiring for depth in the domain. * You've owned architecture from first principles - set the design, defended it, and lived with what it cost. * You've worked somewhere being wrong was expensive, and you design for failure up front: idempotency, retries, reconciliation against a number someone else is also computing. * You have real range across the stack. Strong TypeScript, and you build the interface on top of your own system instead of handing that off. * You've run a multi-month project from a problem statement rather than a spec, and other engineers built on what you shipped. * You use AI tools in your own engineering workflow. Nice to have: card issuing, tokenization, or PCI scope; checkout integrations at depth; browser automation or request interception; something you shipped that an LLM calls as a tool; early-stage companies where you set the architecture rather than inherited it. ## Description Agents can think now, and increasingly they can act. What they can't do is spend. The rails underneath assume a person at the keyboard, so teams fall back on closed catalogs, cards and API keys pasted into config, or a human approving every purchase. We're removing that constraint. A customer connects a card and grants a named agent permission without leaving your product. They set the limits - per purchase, per merchant, approval required or not. The agent buys inside those limits across browser checkout, payment protocols, and APIs. Card details never enter the conversation, and every purchase leaves a record from approval through merchant confirmation. The work spans the whole path a purchase takes: connecting a customer and their agent, vaulting the card, establishing agent identity, enforcing the rules, moving the payment, and making the outcome legible afterward. Card issuing, voice-initiated payments, payment recovery, and insurance are all part of where this goes. We have assembled a team with deep infrastructure and payments DNA. Our founder ran payments engineering at Shopify for five years and built an autonomous consumer agent company before that. We raised a $35M Series A led by Dragonfly in August, bringing us to $50M total. Accel led our seed; Menlo Ventures and Anthropic are also behind us., Agents are starting to buy things on their own, and the rails underneath all assume a person at the keyboard. Letting an agent complete a purchase inside limits its owner actually set, and keeping proof of what was agreed, is the company.