Product and Solution Owner
Diebold Nixdorf (company site, opens in a new tab)2–4 yrsOn-siteDirect career pageEst. 8–16 LPA
Posted on 1 Sept
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Reach people at Diebold Nixdorf
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Diebold Nixdorf you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Own and develop technical requirements, use cases, and backlog for the Vynamic Transaction Middleware product used in financial transaction processing.
- Collaborate closely with development teams to ensure aligned implementation and manage backlog prioritization supporting software release planning.
- Support sales, solution architects, delivery, and presales teams by creating enablement documentation and systems to facilitate customer onboarding.
Minimum Requirements
- 2 to 4 years of experience in the Payments domain.
- Strong hands-on experience with ISO 8583 payment messaging standards (mandatory).
- Experience with product management, product ownership, and working with cloud-based services, integration frameworks, device/peripheral management, and API development relevant to financial transaction processing.
- Work Experience Required: 2 to 4 years in Payments domain
Ideal Candidate Profile
- Experienced in payment processing ecosystems covering both Issuer and Acquirer domains.
- Skilled in requirements gathering, business analysis, and preparation of detailed BRDs and functional specifications.
- Familiarity with Network Scheme certifications and mandates related to Visa, Mastercard, and Amex, able to collaborate with both business and technical stakeholders.