Jobs · OTHR · Michigan

Product Support Specialist

Post Office Ltd · Chesterfield, MI · 1 mo ago
OTHRFull-time
We need to output HTML fragment with sections only when content exists. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We must not include Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Let's extract sections: - Summary: Salary: Competitive plus comprehensive benefits package Grade: 3B Reporting Line: Banking Automation Lead Contract Type: Permanent Location: Remote - wil be required to visit Bolton, Chesterfield or London offices But we should not include Pay/Schedule unless stated. Salary is mentioned as "Competitive plus comprehensive benefits package". That's vague; we should not create Pay section unless actual numbers. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated later in "What We Can Do For You". So we can have Benefits section. Pay: we have only "Competitive plus comprehensive benefits package" which is not specific; we should not create Pay section. Schedule: not stated. Thus sections: About the role (maybe from "What To Expect" paragraph), Responsibilities (maybe from description of duties), Requirements (maybe from "What You’ll Need To Succeed"), Qualifications (maybe overlapping), Skills (maybe from same), Benefits (from benefits list). We need to decide which headings to use based on content. We must not create empty sections. Use only those with real content. Let's extract content: About the role: The paragraph starting "What To Expect As a Banking Automation Product Support Specialist you will act as a Hardware Product Specialist ..." That's description of role. Could be About the role. Responsibilities: The duties: "supporting our in store range of Banking Automation Products and Services", "working closely with our Post Offices and the wider Banking team", "provide guidance in product and vendor management", "champion best practice", "supporting the Banking Automation team’s suite of products, including ATMs, Teller Cash Recyclers (TCRs), Multi‑Function Devices (MFDs) and Note Counters", "develop, maintain and own the incident management framework", "oversee engagement management practices", "ensuring automated banking products consistently deliver high performance, maximising revenue while keeping costs within budget", "promote a culture of inclusion, continuous improvement and high performance, with a strong focus on revenue growth, process optimisation and innovation", "role model the Post Office behaviours and demonstrate an Operator first mindset". That's responsibilities. Requirements: "To be successful in this role you will need experience in Banking Automation devices (ATM's) ideally within a Product Support capacity or similar. As a Product Support Specialist, Experience With Contract Management Or Supplier Relationships Would Be Advantageous. In Addition To This, The Ideal Candidate Will Have strong stakeholder engagement skills and experience Strong interpersonal and presentation skills with the ability to communicate effectively Wider product experience in technology or finance is advantageous Commercial business acumen with the ability to make data-driven business decisions. Proven experience collaborating with peers, colleagues, and stakeholders to contribute to the delivery of functional strategy to achieve business objectives Experience in establishing successful, cross-functional stakeholder relationships Demonstrable experience of leading on leading on key objectives" Qualifications: Might be similar to requirements; but we can treat "Grade: 3B" maybe as qualification? Not sure. The posting includes Grade: 3B, Reporting Line, Contract Type, Location. Those could be considered metadata; we could put them in a short

under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include Grade, Reporting Line, Contract Type, Location in a short paragraph maybe under About the role or a separate meta paragraph. But we should not create a heading for them. Skills: Could be extracted from requirements: stakeholder engagement, interpersonal, presentation, communication, product experience, commercial acumen, data-driven decisions, collaboration, cross-functional relationships, leadership. Benefits: list given. We need to avoid duplication. Let's craft sections:

About the role

Grade: 3B • Reporting Line: Banking Automation Lead • Contract Type: Permanent • Location: Remote (with required visits to Bolton, Chesterfield or London offices). As a Banking Automation Product Support Specialist you will act as a Hardware Product Specialist whilst joining us on our journey by undertaking a valuable role responsible for supporting our in store range of Banking Automation Products and Services. By working closely with our Post Offices and the wider Banking team you will be best placed to ensure we are maximising the functionality and revenue potential for our ATM's and MFD's. As a trusted advisor you will provide guidance in product and vendor management and champion best practice across the Post Office Banking space. The specialist will play a key role in supporting the Banking Automation team’s suite of products, including ATMs, Teller Cash Recyclers (TCRs), Multi‑Function Devices (MFDs) and Note Counters. They will also develop, maintain and own the incident management framework, as well as oversee engagement management practices. This position is accountable for ensuring automated banking products consistently deliver high performance, maximising revenue while keeping costs within budget. They promote a culture of inclusion, continuous improvement and high performance, with a strong focus on revenue growth, process optimisation and innovation. How our people behave is as important to Post Office, as what is delivered. The Banking Automation Specialist will role model the Post Office behaviours and demonstrate an Operator first mindset.

That covers role description and metadata. Now Responsibilities: Could be separate but we already included many responsibilities in About the role. To avoid duplication, maybe we split: About the role short intro, Responsibilities list. But we must not repeat same content. Let's think: The "What To Expect" paragraph is essentially role overview; we could treat that as About the role. Then responsibilities could be bullet list of duties. Let's extract responsibilities list: - Supporting in-store range of Banking Automation Products and Services. - Working closely with Post Offices and wider Banking team to maximise functionality and revenue potential of ATMs and MFDs. - Providing guidance in product and vendor management. - Championing best practice across the Post Office Banking space. - Supporting the Banking Automation team’s suite of products: ATMs, Teller Cash Recyclers (TCRs), Multi‑Function Devices (MFDs), Note Counters. - Developing, maintaining and owning the incident management framework. - Overseeing engagement management practices. - Ensuring automated banking products consistently deliver high performance, maximising revenue while keeping costs within budget. - Promoting a culture of inclusion, continuous improvement and high performance, with a strong focus on revenue growth, process optimisation and innovation. - Role modelling Post Office behaviours and demonstrating an Operator first mindset. We can put these in
  • . Now Requirements / Qualifications / Skills: We need to decide which headings to use. The posting includes "What You’ll Need To Succeed" which is a mix of experience, skills, qualifications. We could split into Requirements (experience) and Skills (soft skills). But we must not create thin sections. Perhaps combine into one section "Requirements" with both experience and skills. Or we could have "Requirements" for experience and "Skills" for abilities. Let's see if we have enough content for each. Experience requirements: - Experience in Banking Automation devices (ATM's) ideally within a Product Support capacity or similar. - Experience With Contract Management Or Supplier Relationships Would Be Advantageous. - Wider product experience in technology or finance is advantageous. - Proven experience collaborating with peers, colleagues, and stakeholders to contribute to the delivery of functional strategy to achieve business objectives. - Experience in establishing successful, cross-functional stakeholder relationships. - Demonstrable experience of leading on key objectives. Skills: - Strong stakeholder engagement skills and experience. - Strong interpersonal and presentation skills with the ability to communicate effectively. - Commercial business acumen with the ability to make data-driven business decisions. We could have Requirements (experience) and Skills (abilities). Both have substantive content. Thus:

    Requirements

    • Experience in Banking Automation devices (ATM's) ideally within a Product Support capacity or similar.
    • Experience with contract management or supplier relationships (advantageous).
    • Wider product experience in technology or finance (advantageous).
    • Proven experience collaborating with peers, colleagues, and stakeholders to contribute to the delivery of functional strategy to achieve business objectives.
    • Experience in establishing successful, cross-functional stakeholder relationships.
    • Demonstrable experience of leading on key objectives.

    Skills

    • Strong stakeholder engagement skills and experience.
    • Strong interpersonal and presentation skills with the ability to communicate effectively.
    • Commercial business acumen with the ability to make data‑driven business decisions.
    Now Benefits: we have list. We need to output Benefits section only if posting actually states them. Yes. Benefits list: - 25 days annual leave (rising to 30 after 2 years), plus bank holidays - Up to 10% on target bonus opportunity - Generous pension scheme with minimum 10% employer contribution - Access to 24/7 digital GP services and our Employee Assistance Programme - 6 x Life assurance and income protection after 12 months service - Over 400 online courses, mentoring, apprenticeships, and development programmes - Access to our benefits platform for exclusive discounts & savings We should not include the line "Click here for a detailed overview of our benefits" as it's a link/instruction; we can drop it. Thus:

    Benefits

    • 25 days annual leave (rising to 30 after 2 years), plus bank holidays
    • Up to 10% on target bonus opportunity
    • Generous pension scheme with minimum 10% employer contribution
    • Access to 24/7 digital GP services and our Employee Assistance Programme
    • 6 × Life assurance and income protection after 12 months service
    • Over 400 online courses, mentoring, apprenticeships, and development programmes
    • Access to our benefits platform for exclusive discounts & savings
    We should not include Pay or Schedule sections. Now ensure we didn't repeat content. The About the role paragraph includes some responsibilities; we might have duplicated some. To avoid duplication, we could shorten About the role to just overview and meta, leaving responsibilities to separate list. Let's craft About the role as a brief summary: "As a Banking Automation Product Support Specialist you will act as a Hardware Product Specialist, supporting our in‑store range of Banking Automation Products and Services, working closely with Post Offices and the wider Banking team to maximise functionality and revenue potential of ATMs and MFDs, providing product and vendor guidance, championing best practice, and supporting the Banking Automation team’s suite of products (ATMs, TCRs, MFDs, Note Counters) while developing incident management and engagement practices." That captures role but not all responsibilities. Then Responsibilities list can include the rest. But we must preserve ALL substantive information; we cannot omit details. So we need to ensure all details appear somewhere. If we put some in About the role and some in Responsibilities, that's fine as long as we don't duplicate. Let's decide to put the core role description in About the role, and then Responsibilities list for detailed duties. Let's extract core role description from "What To Expect": "As a Banking Automation Product Support Specialist you will act as a Hardware Product Specialist whilst joining us on our journey by undertaking a valuable role responsible for supporting our in store range of Banking Automation Products and Services. By working closely with our Post Offices and the wider Banking team you will be best place to ensure we are maximising the functionality and revenue potential for our ATM's and MFD's. As a trusted advisor you will provide guidance in product and vendor management and champion best practice across the Post Office Banking space. The specialist will play a key role in supporting the Banking Automation

Similar jobs