Partner Success Operations Manager
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "About Us" (should be omitted? It's not a heading we need; we can include as prose maybe but not as heading). The instructions: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. We need to preserve all substantive information; remove boilerplate etc. We need to parse the content. Given text: About Us We are Ocado Group, and we're bringing world-class automation to online grocery. Our Ocado Smart Platform (OSP) combines cutting-edge robotics, AI, and IoT within our advanced CFCs (Customer Fulfilment Centres). We've mastered the single pick, transforming online delivery for our global partners. Join us and be part of a team pushing the boundaries of retail technology. About The Role The Ocado Smart Platform (OSP) is a modular, scalable software and hardware solution supporting highly automated customer fulfilment warehouses (CFCs) integrated with a fully fledged grocery e-commerce platform. The vision is to provide large bricks and mortar retailers across the globe with an online service using our disruptive technology. Partner Success Managers are the primary point of contact for our OSP Partners to ensure they are using OSP to maximum potential. They work with Partners to identify areas of opportunity to drive maximum performance and business value for the Partners and for Ocado. Partner Success Managers work closely with Partners from pre go-live through the lifetime of the contract. They form part of the Partner Account Team and collaborate closely with other Partner Success teams and teams across the Ocado Group to ensure Partners receive expert knowledge and support in the effective use of OSP and the seamless deployment of new features and products. The Partner Success Manager is the primary point of contact for their assigned Partner(s) for the effective, stable and value-driven use of the Ocado Smart Platform (OSP), covering fulfilment, supply chain, and last mile operations.A core member of the Partner Account Team, working closely with Partner operational teams and cross-functional Ocado teams to ensure Partner priorities are clearly represented and delivered in a joined-up way.Uses operational data, performance metrics and analytics to develop and maintain a deep understanding of Partner performance, risks and dependencies, and to identify opportunities to improve efficiency, resilience and service outcomes.Accountable for understanding the Partner’s operating model, contractual scope and operational objectives, and for supporting Partners to achieve strong, sustainable performance within the agreed framework.Acts as the primary operational and platform liaison between the Partner and Ocado, ensuring Partner context, requirements, constraints and business case are clearly understood and appropriately prioritised for implementation.Owns the Partner relationship for operational OSP roadmap engagement, acting as the named point of contact for operational roadmap topics, feature delivery queries and platform evolution in the context of operations.Represents Partner operational requirements and priorities into Ocado’s roadmap and change governance processes, ensuring clear problem definition, Partner impact and business case and operational context are understood.Owns Partner readiness for change, including the preparation and delivery of operational go-lives and deployments, ensuring Partners are informed, prepared and able to adopt new functionality effectively.Ensures Partners are making effective use of relevant and available OSP functionality, promoting adoption of standard capabilities and best practice to maximise operational value.Proactively monitors delivery of Partner-relevant platform changes, working with internal stakeholders to resolve issues, manage dependencies and escalate risks where delivery may impact Partner operations or confidence.Balances Partner support needs with contractual commitments and commercial considerations, ensuring support is delivered in a way that is both Partner-centric and commercially responsible.Builds and maintains strong, positive working relationships with Partner teams and internal stakeholders, fostering trust, transparency and effective collaboration.Contributes to the continuous improvement of Partner Success ways of working through sharing best practice, supporting cross-partner initiatives, and helping evolve processes, standards and tooling across the function. About You Experience in a retail or logistics operationFamiliarity with continuous improvement and optimisation processesStakeholder, relationship building and networking skillsSelf-motivated with an ability to deliver to deadlines and multi-task under pressureHighly organised and resilient with an eye for detailAbility to think strategically beyond the needs of the organisation todayUnderstanding of project management frameworksExperience of working cross-functionally both internally and externally to drive partnerships or projectsBusiness management experience and commercial awareness What We Offer 401k Plan; 100% match up to 5% of earningsPaid Vacation and Sick Days10 Paid Public HolidaysMedical, Dental, and Vision InsuranceMedical and Dependent CareFlexible Spending Accounts Health Reimbursement AccountCompany Contribution of 50% of Annual DeductibleCompany Paid Life InsuranceShort and Long Term Disability InsuranceEmployee Assistance Program We need to map sections. - About the role: we have "About The Role" paragraph. That's content for About the role. Should be
About the role
then... (the paragraph). Should we split? Probably keep as one paragraph. - Responsibilities: The role description includes many responsibilities. Could extract bullet list of duties. The text after "About The Role" includes many sentences describing responsibilities. We could turn them into
- items. The instruction: Use
- for any list of duties/requirements/benefits. So we need to create a list for responsibilities. We'll parse sentences into list items.
- Requirements/Qualifications/Skills: The "About You" section lists experience and skills. Could be considered Requirements or Qualifications or Skills. We need to decide which sections to include. The posting has "About You" with bullet-like items (though not bullet). We can treat as Requirements (or Skills). Since we have multiple possible sections, we should prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section? But we have headings for Requirements, Qualifications, Skills. We need to include only when posting has real specific content for it. The "About You" includes experience, familiarity, skills, self-motivated, organised, ability to think strategically, understanding of project management frameworks, experience cross-functionally, business management experience and commercial awareness. That's a mix of requirements and skills. Could split into Requirements (experience, familiarity, understanding of project management frameworks, business management experience) and Skills (stakeholder, relationship building, networking, self-motivated, organised, eye for detail, strategic thinking, etc). But we need to avoid thin sections. Perhaps we can make one section "Requirements" and include all as list items. Or "Skills". The instruction: Prefer a few substantive sections over many thin ones. So better to have one section, maybe "Requirements" (or "Skills") containing all. Which heading is more appropriate? The content is about experience and skills; could be "Requirements". We'll choose "Requirements". We'll not include Qualifications or Skills separately.
- Benefits: "What We Offer" includes benefits list. That's Benefits section. We'll create
Benefits
then- items.
- Pay and Schedule: Not mentioned. So we omit those sections.
- Also we might include "About Us" as a short paragraph? The instruction: do not repeat job title; we can include About Us as a paragraph maybe under a heading? There's no heading for About Us in the list; we could just include as a
before sections. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep About Us content. It's not a heading we need to output; we can just put it as a
at top. Thus final HTML:
About Us We are Ocado Group, and we're bringing world-class automation to online grocery. Our Ocado Smart Platform (OSP) combines cutting-edge robotics, AI, and IoT within our advanced CFCs (Customer Fulfilment Centres). We've mastered the single pick, transforming online delivery for our global partners. Join us and be part of a team pushing the boundaries of retail technology.
About the role
The Ocado Smart Platform (OSP) is a modular, scalable software and hardware solution supporting highly automated customer fulfilment warehouses (CFCs) integrated with a fully fledged grocery e-commerce platform. The vision is to provide large bricks and mortar retailers across the globe with an online service using our disruptive technology. Partner Success Managers are the primary point of contact for our OSP Partners to ensure they are using OSP to maximum potential. They work with Partners to identify areas of opportunity to drive maximum performance and business value for the Partners and for Ocado. Partner Success Managers work closely with Partners from pre go-live through the lifetime of the contract. They form part of the Partner Account Team and collaborate closely with other Partner Success teams and teams across the Ocado Group to ensure Partners receive expert knowledge and support in the effective use of OSP and the seamless deployment of new features and products. The Partner Success Manager is the primary point of contact for their assigned Partner(s) for the effective, stable and value-driven use of the Ocado Smart Platform (OSP), covering fulfilment, supply chain, and last mile operations.A core member of the Partner Account Team, working closely with Partner operational teams and cross-functional Ocado teams to ensure Partner priorities are clearly represented and delivered in a joined-up way.Uses operational data, performance metrics and analytics to develop and maintain a deep understanding of Partner performance, risks and dependencies, and to identify opportunities to improve efficiency, resilience and service outcomes.Accountable for understanding the Partner’s operating model, contractual scope and operational objectives, and for supporting Partners to achieve strong, sustainable performance within the agreed framework.Acts as the primary operational and platform liaison between the Partner and Ocado, ensuring Partner context, requirements, constraints and business case are clearly understood and appropriately prioritised for implementation.Owns the Partner relationship for operational OSP roadmap engagement, acting as the named point of contact for operational roadmap topics, feature delivery queries and platform evolution in the context of operations.Represents Partner operational requirements and priorities into Ocado’s roadmap and change governance processes, ensuring clear problem definition, Partner impact and business case and operational context are understood.Owns Partner readiness for change, including the preparation and delivery of operational go-lives and deployments, ensuring Partners are informed, prepared and able to adopt new functionality effectively.Ensures Partners are making effective use of relevant and available OSP functionality, promoting adoption of standard capabilities and best practice to maximise operational value.Proactively monitors delivery of Partner-relevant platform changes, working with internal stakeholders to resolve issues, manage dependencies and escalate risks where delivery may impact Partner operations or confidence.Balances Partner support needs with contractual commitments and commercial considerations, ensuring support is delivered in a way that is both Partner-centric and commercially responsible.Builds and maintains strong, positive working relationships with Partner teams and internal stakeholders, fostering trust, transparency and effective collaboration.Contributes to the continuous improvement of Partner Success ways of working through sharing best practice, supporting cross-partner initiatives, and helping evolve processes, standards and tooling across the function.
Responsibilities
- Act as the primary point of contact for assigned Partner(s) for the effective, stable and value‑driven use of the Ocado Smart Platform (OSP), covering fulfilment, supply chain, and last mile operations.
- Work closely with Partner operational teams and cross‑functional Ocado teams to ensure Partner priorities are clearly represented and delivered in a joined‑up way.
- Use operational data, performance metrics and analytics to develop and maintain a deep understanding of Partner performance, risks and dependencies, and identify opportunities to improve efficiency, resilience and service outcomes.
- Understand the Partner’s operating model, contractual scope and operational objectives, and support Partners to achieve strong, sustainable performance within the agreed framework.
- Act as the primary operational and platform liaison between the Partner and Ocado, ensuring Partner context, requirements, constraints and business case are clearly understood and appropriately prioritised for implementation.
- items.
- Pay and Schedule: Not mentioned. So we omit those sections.
- Also we might include "About Us" as a short paragraph? The instruction: do not repeat job title; we can include About Us as a paragraph maybe under a heading? There's no heading for About Us in the list; we could just include as a
- for any list of duties/requirements/benefits. So we need to create a list for responsibilities. We'll parse sentences into list items.
- Requirements/Qualifications/Skills: The "About You" section lists experience and skills. Could be considered Requirements or Qualifications or Skills. We need to decide which sections to include. The posting has "About You" with bullet-like items (though not bullet). We can treat as Requirements (or Skills). Since we have multiple possible sections, we should prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section? But we have headings for Requirements, Qualifications, Skills. We need to include only when posting has real specific content for it. The "About You" includes experience, familiarity, skills, self-motivated, organised, ability to think strategically, understanding of project management frameworks, experience cross-functionally, business management experience and commercial awareness. That's a mix of requirements and skills. Could split into Requirements (experience, familiarity, understanding of project management frameworks, business management experience) and Skills (stakeholder, relationship building, networking, self-motivated, organised, eye for detail, strategic thinking, etc). But we need to avoid thin sections. Perhaps we can make one section "Requirements" and include all as list items. Or "Skills". The instruction: Prefer a few substantive sections over many thin ones. So better to have one section, maybe "Requirements" (or "Skills") containing all. Which heading is more appropriate? The content is about experience and skills; could be "Requirements". We'll choose "Requirements". We'll not include Qualifications or Skills separately.
- Benefits: "What We Offer" includes benefits list. That's Benefits section. We'll create