Product Owner/Manager

Job Title: Product Owner

Location: NYC (5days/week onsite)

Duration: Long-Term Contract

Mandatory skills: Commercial Payment or Wholesale Payment experience

Pay Rate : $65/hr on C2C

Local candidates most preferred and considered or near by candidates

Virtual 

Product Management Role Requirements

1. Role Focus & Domain Expertise

The team is hiring Product Managers for a commercial/wholesale payments environment. These roles require deep functional knowledge in:

• Commercial / Wholesale Payments
• Payment rails: ACH, wires, cross‑border FX, banking rails, push‑to‑card, PayPal‑like flows
• Merchant‑facing experiences: portals for refunds, reversals, reports, tax statements, transaction performance analytics
• Internal operations tools: screens and workflows for operations, internal support, and tooling
• Scalable platform‑level payments (e.g., experience from Amazon, Walmart, Expedia, etc.)
• End‑to‑end payment lifecycle: from merchant interactions to backend reconciliation and payouts

Explicit exclusions:

• Not looking for EMV, hardware, or terminal-focused payments backgrounds
• Limited applicability for candidates strictly from checkout optimization / top‑of‑funnel consumer payments

2. Seniority & Experience Range

Preferred experience band is:

• 4 to 10 years of product management or hybrid BA/PM experience

Anything beyond that may result in:

• Over‑seniority
• Risk of dissatisfaction or attrition unless down‑leveled3. Role Structure & Expectations

The role is described as an integrated PM/BA hybrid, requiring candidates to be:

• Hands‑on (not managerial)
• Writing PRDs, epics, and user stories directly
• Working directly with developers (not via separate BAs)
• Managing UAT cycles and supporting technical teams
• Able to own end‑to‑end delivery within two‑week Agile sprints

This is not a “feature shepherding" PM role—it is a sleeves‑rolled‑up, execution‑heavy position.

4. Communication & Stakeholder Management

Excellent communication is mandatory.
This was repeatedly emphasized as a top‑level filter.

Reasons:

• Cross‑domain coordination
• Influencing without authority
• Collaboration with multiple internal and merchant‑facing teams

Candidates with strong technical skills but weak communication are immediate rejects.

5. Culture & Working Style

The team culture is:

• Fast‑paced and execution‑oriented
• “No mediocrity”—only high performers can keep pace
• Requires proactive individuals who: ( meaning the PMs are the "business" in discussions with developers)

• Don’t wait for instructions
• Drive clarity
• Push deliverables independently

Work style:

• In‑office, 5 days per week (New York)
• Casual dress environment (jeans, sneakers acceptable)
• No traditional “banking suits” culture
• Collaborative and people‑first

6. Priority Workstreams

The most urgent hiring focus is on the Arsenal program, specifically:

• Reporting needs
• Setup flows
• Merchant-facing and internal operational tooling

These roles are needed immediately (“bodies yesterday”).

7. Additional Recruiting Guidance

What HR should prioritize:

Strong Fits

• Candidates with platform‑level, high‑scale payments experience
• PMs comfortable drafting PRDs, user stories, end‑to‑end flows
• Individuals with both product + BA skillsets
• Hands‑on contributors who thrive in high‑velocity environments

Red Flags / Reject Criteria

• Weak communication- meaning clear spoken English with minimal accent.
• Purely EMV/hardware/terminal payment backgrounds
• Candidates seeking only strategy or oversight roles
• Individuals uncomfortable with a high‑pressure environment
• Those unwilling to work onsite in NYC five days a week