Sr Product Owner
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate, duplicated lines, EEO, legal, application instructions, etc.
We need to parse the posting and extract relevant content.
Let's identify sections:
- About NCR VOYIX (company description) maybe not needed as heading? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". They didn't say we cannot include About the company. But they list allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should only use those headings. The company description could go under About the role? Possibly we can include a brief paragraph about the company under About the role. But we must not invent headings not listed. So we can put company overview in a
under About the role or maybe as a separate paragraph before headings? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid having a leading paragraph before any heading. But they said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have other content not under those headings? Probably better to put everything under those headings. The "About the role" could contain the company description and role summary.
Responsibilities: list of duties from "IN THIS ROLE, YOU CAN EXPECT TO…" and bullet points after that.
Requirements: list from "YOU HAVE… Requirements:" and bullet points.
Qualifications: maybe "General knowledge, skills and abilities:" could be qualifications? But they also have skills list. Could treat "General knowledge, skills and abilities:" as Qualifications. And the earlier bullet list under "YOU HAVE…" includes skills like Entrepreneurship skills, etc. Those could be Skills. But we need to decide.
We have to avoid duplication. Let's extract substantive content.
First, company description: Two paragraphs about NCR Voyix. We'll include that under About the role.
Then role summary: "Senior Product Owner" maybe not heading. Under About the role we can have a paragraph describing the role: "The NCR Voyix Payments Processing Product Owner will be responsible for setting, prioritizing, and accepting the work generated by a team in order to ensure the most valuable and proper functionality of the product." etc.
Then Responsibilities: list of duties from "IN THIS ROLE, YOU CAN EXPECT TO…" and the bullet points after that (the long list). We'll capture each bullet as
- .
Then Requirements: from "YOU HAVE… Requirements:" bullet list.
Then Qualifications: from "General knowledge, skills and abilities:" bullet list.
Then Skills: maybe we could combine some but we already have Skills list from Requirements? Actually Requirements list includes many skills. Could treat Requirements as qualifications and Skills as separate? But we have both Requirements and Qualifications sections allowed. We could put the "YOU HAVE… Requirements:" as Requirements, and the "General knowledge, skills and abilities:" as Qualifications. Then we could have Skills section maybe empty; we should not include empty sections. So we omit Skills.
We must not include Benefits, Pay, Schedule.
Now we need to ensure we preserve all substantive information. Let's extract the exact text.
Company description paragraphs:
First paragraph: "NCR Voyix Corporation (NYSE: VYX) is a global platform-powered leader in unified commerce for shopping and dining. Combining a flexible, intelligent platform with end-to-end payments capabilities and services developed through its deep industry experience, NCR Voyix empowers retailers and restaurants to accelerate new possibilities for their operations, experiences and business outcomes. NCR Voyix is headquartered in Atlanta, Georgia, and serves customers in more than 35 countries worldwide."
Second paragraph (under "WE ARE…"): "NCR Voyix Corporation (NYSE: NCR) is the global leader in consumer transaction technologies, turning everyday interactions with businesses into exceptional experiences. With its software, hardware, and portfolio of services, NCR Voyix enables nearly 700 million transactions daily across retail, financial, travel, hospitality, telecom and technology, and small business. NCR Voyix solutions run the everyday transactions that make your life easier. NCR Voyix Payment Solutions is a completely secure payment solution delivering uncompromising data protection and future innovation readiness. It is the ideal answer to the rising risk of electronic transaction-related fraud and payment data security breaches. Implemented as a SaaS (Software-as-a-Service) solution, Payment Solutions offers a secure payment route and ensures complete data and transmission protection, from PIN pad to payment processor. Our Payments solutions allow retailers to easily comply with evolving payment regulations and standards, such as PCI DSS (Payment Card Industry Data Security Standard) and EMV (Europay, MasterCard and Visa), and offers them the freedom to work with any payment processor and peripheral vendor. Payment Solutions ultimately provides retailers with the innovation-ready architecture, reliability and centralized management they need to prepare for a future of new payment options that improve shopper experience."
We could combine both as About the role.
Now role summary: "IN THIS ROLE, YOU CAN EXPECT TO… The NCR Voyix Payments Processing Product Owner will be responsible for setting, prioritizing, and accepting the work generated by a team in order to ensure the most valuable and proper functionality of the product. As Product Owner, you will gather feature requests, schedule releases and coordinate sprints. You should be able to identify user needs, help a customer understand business value, and work with cross-functional teams to manage product releases. You will need to deliver a product not just according to users’ needs, but a product that helps make our company vision a reality."
Then the bullet list after "Product Owner contributes in the following:" Actually that's a heading inside the responsibilities. We'll treat those as responsibilities.
Let's list them:
- Serve as the voice of the client (external and internal).
- Work with internal and external customers to analyze the needs and align product roadmap to strategic goals.
- Owns the product roadmap.
- Develop scope and define backlog items (epic/features/user stories) that guide the Agile software development team.
- Solve product related problems, make decisions, complete trade-off analysis to stay on track towards business deliverable commitments.
- Draft key objectives and results, strategies and apply the data for the product to make business decisions.
- Possess a fundamental understanding of end-to-end customer experience integration and dependencies.
- Collaborate with stakeholders during the visioning and concept development of a product.
- Accountable for the created product(s), delivering in the product model and communicating the product needs with business partners.
- Asses value, develop cases, and prioritize stories, epics and themes to ensure work focuses on those with a maximum value that are aligned with product strategy.
- Identifies and help the client understand the business model, value and value proposition.
- Develop and maintain an appropriately prioritized backlog of user stories for implementation.
- Act as an ambassador for the product internally and externally and as the primary contact for queries related to the product.
- Develop appropriately detailed specifications for the product features so they are clearly understood by the development teams.
- Represents team in front of stakeholders, clients or users.
- Work closely senior PO in order to create a product that fits the company portfolio.
- Research and analyze market, the users, and the roadmap for the product.
- Follow our competitors and the industry.
- Increase an understanding of Agile practices, Lean Startup, new technologies opportunities and other new trends.
Note some have typos: "Asses" should be "Assess". We'll keep as is.
Now Requirements bullet list from "YOU HAVE… Requirements:":
- Entrepreneurship skills or experience.
- Creative thinker.
- Strategic thinking.
- Product Management.
- The experience in sales or marketing is an advantage.
- Management of stakeholders and their expectation.
- Deep understanding and experience with Agile methodologies.
- Ability to work with cross-functional teams to deliver on a common goal.
- Interpersonal skills and developing relationships with team members and customers.
- Experience with a definition of minimum marketable features and minimum viable products.
- Knows how to define the product roadmap.
- Outstanding communication, presentation and leadership skills.
- Organizational and time management skills.
- Analytical and problem-solving skills
- Attention to details.
- Discipline.
- Active listening.
- Overall understanding of technologies used in the product.
Now Qualifications bullet list from "General knowledge, skills and abilities:":
- Knowledge of financial services payments industry
- Azure or GCP Public Cloud Technologies
- SaaS
- Jira and Atlassian stack
- Agile, Scrum and Kanban
- Jira Align
Also there is a line: "Offers of employment are conditional upon passage of screening criteria applicable to the job" - that's boilerplate? Might be considered metadata but not a heading. We could include as a short paragraph maybe under Requirements? But it's more like a condition. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This line is minor metadata; we could fold into a short p under Requirements or maybe after Qualifications. But we should preserve substantive information; it's not substantive? It's about offer conditional upon screening. Might be considered boilerplate but not EEO. I'd keep it as a short p under Qualifications maybe.
Also there is EEO statement and third party agency statement and application instruction about emails. Those are boilerplate to remove.
Thus we will output:
About the role
... company description paragraphs ...
... role summary paragraph ...
Then Responsibilities
... list items ...
Then Requirements
... list items ...
Then Qualifications
... list items ...
Offers of employment are conditional upon passage of screening criteria applicable to the job.
We must not include any other headings.
Check for duplicated lines: Ensure we didn't repeat any.
Now format HTML.
We need to ensure proper escaping of any special characters like & etc. The text includes "NCR Voyix Corporation (NYSE: VYX)" etc. No special HTML characters except maybe & in "PCI DSS". That's fine.
We'll output exactly.
Let's craft the About the role paragraph(s). Could combine into one with both company description and role summary? Better separate: first p for company description, second p for role summary.
Company description: combine both paragraphs? Might be long but okay.
Let's write:
NCR Voyix Corporation (NYSE: VYX) is a global platform-powered leader in unified commerce for shopping and dining. Combining a flexible, intelligent platform with end-to-end payments capabilities and services developed through its deep industry experience, NCR Voyix empowers retailers and restaurants to accelerate new possibilities for their operations, experiences and business outcomes. NCR Voyix is headquartered in Atlanta, Georgia, and serves customers in more than 35 countries worldwide. NCR Voyix Corporation (NYSE: NCR) is the global leader in consumer transaction technologies, turning everyday interactions with businesses into exceptional experiences. With its software, hardware, and portfolio of services, NCR Voyix enables nearly 700 million transactions daily across retail, financial, travel, hospitality, telecom and technology, and small business. NCR Voyix solutions run the everyday transactions that make your life easier. NCR Voyix Payment Solutions is a completely secure payment solution delivering uncompromising data protection and future innovation readiness.
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate, duplicated lines, EEO, legal, application instructions, etc. We need to parse the posting and extract relevant content. Let's identify sections: - About NCR VOYIX (company description) maybe not needed as heading? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". They didn't say we cannot include About the company. But they list allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should only use those headings. The company description could go under About the role? Possibly we can include a brief paragraph about the company under About the role. But we must not invent headings not listed. So we can put company overview in a
under About the role or maybe as a separate paragraph before headings? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid having a leading paragraph before any heading. But they said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have other content not under those headings? Probably better to put everything under those headings. The "About the role" could contain the company description and role summary. Responsibilities: list of duties from "IN THIS ROLE, YOU CAN EXPECT TO…" and bullet points after that. Requirements: list from "YOU HAVE… Requirements:" and bullet points. Qualifications: maybe "General knowledge, skills and abilities:" could be qualifications? But they also have skills list. Could treat "General knowledge, skills and abilities:" as Qualifications. And the earlier bullet list under "YOU HAVE…" includes skills like Entrepreneurship skills, etc. Those could be Skills. But we need to decide. We have to avoid duplication. Let's extract substantive content. First, company description: Two paragraphs about NCR Voyix. We'll include that under About the role. Then role summary: "Senior Product Owner" maybe not heading. Under About the role we can have a paragraph describing the role: "The NCR Voyix Payments Processing Product Owner will be responsible for setting, prioritizing, and accepting the work generated by a team in order to ensure the most valuable and proper functionality of the product." etc. Then Responsibilities: list of duties from "IN THIS ROLE, YOU CAN EXPECT TO…" and the bullet points after that (the long list). We'll capture each bullet as
or drop it." This line is minor metadata; we could fold into a short p under Requirements or maybe after Qualifications. But we should preserve substantive information; it's not substantive? It's about offer conditional upon screening. Might be considered boilerplate but not EEO. I'd keep it as a short p under Qualifications maybe. Also there is EEO statement and third party agency statement and application instruction about emails. Those are boilerplate to remove. Thus we will output:
About the role
... company description paragraphs ...
... role summary paragraph ...
ThenResponsibilities
- ... list items ...
Requirements
- ... list items ...
Qualifications
- ... list items ...
Offers of employment are conditional upon passage of screening criteria applicable to the job.
We must not include any other headings. Check for duplicated lines: Ensure we didn't repeat any. Now format HTML. We need to ensure proper escaping of any special characters like & etc. The text includes "NCR Voyix Corporation (NYSE: VYX)" etc. No special HTML characters except maybe & in "PCI DSS". That's fine. We'll output exactly. Let's craft the About the role paragraph(s). Could combine into onewith both company description and role summary? Better separate: first p for company description, second p for role summary. Company description: combine both paragraphs? Might be long but okay. Let's write:
NCR Voyix Corporation (NYSE: VYX) is a global platform-powered leader in unified commerce for shopping and dining. Combining a flexible, intelligent platform with end-to-end payments capabilities and services developed through its deep industry experience, NCR Voyix empowers retailers and restaurants to accelerate new possibilities for their operations, experiences and business outcomes. NCR Voyix is headquartered in Atlanta, Georgia, and serves customers in more than 35 countries worldwide. NCR Voyix Corporation (NYSE: NCR) is the global leader in consumer transaction technologies, turning everyday interactions with businesses into exceptional experiences. With its software, hardware, and portfolio of services, NCR Voyix enables nearly 700 million transactions daily across retail, financial, travel, hospitality, telecom and technology, and small business. NCR Voyix solutions run the everyday transactions that make your life easier. NCR Voyix Payment Solutions is a completely secure payment solution delivering uncompromising data protection and future innovation readiness.