> Markdown version of [/jobs/ext/4660706-product-owner-payments](https://www.wearedevelopers.com/jobs/ext/4660706-product-owner-payments). 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).

---

# Product Owner (Payments)

- **Company:** PAYJUNCTION
- **Location:** Santa Barbara, CA, United States (Remote available)
- **Experience:** Experienced
- **Salary:** $115,000 - $125,000
- **Contract:** Permanent contract
- **Skills:** Agile Methodology, Confluence, JIRA, Payment Systems, Scrum Methodology
- **Published:** November 10, 2026
- **Apply:** https://www.careerbuilder.com/job-details/product-owner-payments-santa-barbara-ca--697d7241-c22a-479c-b0cc-059e9401f24d

## About the Role

Business Processes, Entrepreneurship, Industry Standards, Product Backlog, Use Cases, Risk, Sales Operations, Sales Support, Agile Programming Methodologies, Establish Priorities, We exist to drive the success of our partners. We do this by fundamentally changing the way you transact with others. We just happen to make great payment systems. If you love helping others succeed, in a culture that celebrates perfecting your craft, consider partnering with us., * Three or more years as a Product Owner or in a close role (Product Manager, or a business analyst with strong product ownership).

 * Two or more years with Agile and Scrum where you drove refinement and backlog health, not just attended.
 * Track record of outcome-focused delivery you can point to.
 * Direct experience with users and internal stakeholders.
 * Have written clean user stories and acceptance criteria, prioritized with explicit criteria, and kept work visible in tools like Jira and Confluence.
 * Preferred: experience in payments, fintech, or B2B SaaS; a CSPO or PSPO certification; and comfort reading product data to inform priorities.

## Description

* Own and order the product backlog for Payment Experience so the highest-value work is always at the top and clearly tied to product and company goals.
 * Break initiatives and incoming requests into user stories with clear problem statements, acceptance criteria, and identified dependencies.
 * Chase down the answers: talk to stakeholders across Risk, Support, Sales, and Rev Ops, and bring back the use cases and requirements the team needs.
 * Run backlog refinement every sprint and keep at least two sprints of Ready work in front of the team.
 * Act as the single, clear voice between stakeholders and engineering, so nothing disappears and no one is surprised mid-sprint.
 * Track adoption and outcomes after release, and use what you learn to adjust priorities.