Product Owner

MoldStud; United States; Remote; USD 90,000 - 130,000; Full time

Job summary

MoldStud is seeking a Product Owner to own the roadmap and delivery of a fintech product used at scale. You will convert business and regulatory goals into a clear backlog, set priorities, and collaborate closely with engineering from discovery through release.

A strong technical background is essential to evaluate architecture, APIs, and data decisions. You will work between product, engineering, design, and compliance, reporting to product leadership and coordinating with teams delivering the

Qualifications

• Proven experience as a Product Owner or Product Manager on a software product.
• Backlog ownership and end-to-end shipping.
• Write user stories and acceptance criteria clear enough to build from without guesswork.
• Experience turning regulatory or compliance requirements into deliverable work.

Responsibilities

• Own and prioritize the product backlog.
• Translate business, regulatory, and compliance requirements into clear user stories and acceptance criteria.
• Lead backlog refinement, sprint planning, and release planning with engineering.
• Make priority and scope calls, and defend the trade-offs to stakeholders.
• Take part in technical design discussions, API contracts, and data model decisions.
• Define and track success metrics for every release.
• Manage cross-team dependencies and risks, and flag them early.
• Keep stakeholders aligned on roadmap, progress, and changes.

Skills

Backlog ownership

Prioritization

Stakeholder communication

Decision making

Technical clarifications

Tools

APIs

Databases

Microservices

Job description

We are looking for a Product Owner to own the roadmap and delivery of a fintech product used at scale. You will turn business and regulatory goals into a clear backlog, make the call on priorities, and work shoulder to shoulder with engineering from discovery through release. This role needs a real technical background. You will be weighing trade-offs on architecture, APIs, and data, so you need to understand them, not just pass them along.

Your Team

You sit between product, engineering, design, and compliance. Engineers come to you for clarity on what to build and why. You report into product leadership and partner closely with the teams shipping the platform the client’s donors and partner organizations rely on.

Critical Requirements

• Technical background: you have written production code or worked as an engineer before moving into product. You can read code, follow technical design discussions, and challenge engineering trade-offs on merit. You are comfortable with APIs, databases, and how distributed systems fit together.

Responsibilities

• Own and prioritize the product backlog, keeping it refined and understood by the team.
• Translate business, regulatory, and compliance requirements into clear user stories and acceptance criteria.
• Lead backlog refinement, sprint planning, and release planning with engineering.
• Make priority and scope calls, and defend the trade-offs to stakeholders.
• Take part in technical design discussions, API contracts, and data model decisions.
• Define and track success metrics for every release.
• Manage cross-team dependencies and risks, and flag them early.
• Keep stakeholders aligned on roadmap, progress, and changes.

Requirements

• Proven experience as a Product Owner or Product Manager on a software product.
• Track record of owning a backlog and shipping releases end to end.
• Write user stories and acceptance criteria clear enough to build from without guesswork.
• Experience turning regulatory or compliance requirements into deliverable work.

Core Competencies

• Keep engineering, design, and business stakeholders aligned without losing momentum.
• Ownership: you take a feature from idea to production and own the outcome.
• Decision-making: you prioritize with incomplete information and stand behind the call.
• Problem-solving: you break down ambiguous problems and find a workable path.
• Communication: you explain the \"why\" clearly to technical and non-technical people.

Nice to Have

• Experience in fintech, payments, or another regulated domain.
• Familiarity with event-driven systems or microservices.
• Hands-on use of analytics tools to measure product impact.