Stewardship Services Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications? Actually they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include only sections with real specific content. The posting includes: description (role leads operational excellence...), then "Accountabilities" which is responsibilities. Then "Requirements". Then "Benefits". Also mention "Travel occasionally..." but that's also in description and benefits. Pay: Starting salary range $67,000–$77,000 per year. So we need a Pay section. Schedule? Not explicit; remote work within continental US, occasional travel less than 10%. Could be schedule? Not explicit hours. Probably not include Schedule if not stated. Skills? Could be derived but not explicit list; maybe we can include Skills if there is explicit list: they mention proficiency with CRM, ticketing platforms, Microsoft Office, Google Workspace, XML, FTP, etc. That's skills. Could create Skills section. Qualifications? Might overlap with Requirements; but we can keep Requirements and maybe Qualifications not needed. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. The posting has: description (About the role). Accountabilities (Responsibilities). Requirements (list). Benefits (list). Pay (salary). Skills (proficiency with tools). Could also include Schedule? Not explicit; remote work location and travel but not schedule. So omit Schedule. We must not repeat job title as heading. No Job ID. Remove boilerplate: "This position is listed on behalf of a partner company..." etc. Also remove "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc. Also remove "Our partner is looking for a Stewardship Services Manager based in United States." That's maybe part of description but we can keep substantive info about role. However the first sentence "This position is listed on behalf of a partner company, who manages all applications and next steps." is boilerplate; we should drop it. Keep the rest: "Our partner is looking for a Stewardship Services Manager based in United States." That's maybe okay but it's somewhat generic; but we can keep as part of About the role? Might be considered filler. Safer to start About the role with the description: "This role leads operational excellence across digital stewardship services, ensuring reliable, high-quality delivery for participants and partners." etc. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting except boilerplate/navigation/legal/EEO etc. Let's extract substantive paragraphs. Original text: "This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Stewardship Services Manager based in United States. This role leads operational excellence across digital stewardship services, ensuring reliable, high-quality delivery for participants and partners. You will oversee service workflows, support operations, vendor coordination, and initiatives that improve efficiency and customer satisfaction. The position combines technical and product knowledge with process improvement, data analysis, and stakeholder management. You will collaborate closely with Product, Technology, Operations, and Participant Success teams to resolve complex issues and improve service experiences. The role also provides opportunities to influence product enhancements through participant feedback, service metrics, and root-cause analysis. As a people-focused leader, you will coach team members, encourage continuous learning, and help guide teams through operational change. The position is remote within the continental United States, with occasional travel of less than 10% primarily to Michigan and New York offices." Then "Accountabilities" list: - Maintain strong technical and product knowledge of digital stewardship services and related publishing and archiving processes. - Oversee daily support operations and content workflows to ensure consistent, accurate, and high-quality service delivery. - Identify, design, and implement workflow and process improvements that increase operational efficiency and participant satisfaction. - Partner with Product, Technology, and Operations teams to resolve complex issues and improve cross-functional communication. - Collaborate with Participant Success teams to support participant onboarding, communication, training, and operational alignment. - Build and maintain effective vendor relationships, providing training and operational support as needed. - Monitor vendor performance and ensure adherence to established quality and service standards. - Track content workflows through JIRA and analyze operational data to identify trends, root causes, and improvement opportunities. - Conduct regular data analysis and prepare performance reporting for internal stakeholders. - Monitor service performance against established KPIs and use findings to inform operational decisions. - Gather, assess, and communicate participant feedback to support service enhancements and product development. - Lead cross-functional process design initiatives and implement tactical improvements with measurable outcomes. - Identify systemic problems affecting multiple teams or workflows and coordinate solutions across relevant stakeholders. - Provide coaching, mentoring, and guidance to team members while fostering accountability, collaboration, and continuous learning. - Represent the Stewardship Services function in cross-departmental initiatives and ensure participant and partner perspectives are incorporated into decision-making. - Use data-driven recommendations and clear communication to influence stakeholders and build alignment around improvements. - Champion accessibility requirements and incorporate digital accessibility best practices into daily service delivery. - Help teams navigate operational change while maintaining service quality and positive participant outcomes. - Uphold organizational values centered on belonging, evidence, speed, teamwork, and trust. - Travel occasionally, generally less than 10%, with a primary focus on visits to offices in Michigan and New York. Then "Requirements": - Bachelor’s degree in a related field or equivalent professional experience. - 5+ years of experience in customer service, professional services, participant-facing operations, or a comparable environment. - Experience working in SaaS, digital content, publishing, archiving, or other technology-enabled service environments is valuable. - Demonstrated experience managing vendor relationships and maintaining quality and performance standards. - Proven ability to lead process improvements and cross-functional operational initiatives. - Strong analytical and problem-solving skills, including the ability to interpret operational data and make data-informed decisions. - Exceptional written and verbal communication skills, with the ability to explain complex information clearly and concisely. - Strong stakeholder management and collaboration skills across teams and organizational levels. - Demonstrated project and time management capabilities, with the ability to balance competing priorities and deadlines. - Experience coaching, mentoring, and developing team members. - Proficiency with CRM and ticketing platforms such as Zendesk and JIRA. - Working knowledge of Microsoft Office and Google Workspace. - Comfort working with XML and FTP. - Ability to lead cross-functional process design and translate improvements into measurable operational outcomes. - Strong ability to identify and solve systemic issues that affect multiple teams, workflows, or service areas. - Ability to influence stakeholders through clear, persuasive, data-driven recommendations. - Strong organizational skills and attention to detail in an operational environment. - Ability to collaborate effectively, communicate change, and maintain focus on customer and participant outcomes. - Commitment to accessibility best practices and inclusive service delivery. - Must be able to work and reside within the continental United States and be legally authorized to work without immigration sponsorship. Then "Benefits": - Starting salary range of $67,000–$77,000 per year. - Compensation may vary based on job-related knowledge, skills, and experience. - Medical, dental, and vision insurance plans. - Employer-paid retirement contribution of 10%. - Paid parental and caregiver leave. - 22 days of paid time off. - 11 paid holidays. - Up to 12 sick days. - Wellness benefits. - Remote work within the continental United States. - Occasional travel, generally less than 10%, primarily to Michigan and New York offices. - Benefits may be updated at the employer’s discretion over time. Then there is "How Jobgether Works" etc which we must remove. Thus we need sections: About the role (the introductory paragraph after removing boilerplate). Responsibilities (the Accountabilities list). Requirements (the list). Benefits (list). Pay (salary range). Skills (maybe we can extract from requirements: proficiency with CRM, ticketing platforms, Microsoft Office, Google Workspace, XML, FTP). But those are already in Requirements; we could keep them under Requirements. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Skills into Requirements or omit separate Skills section. Since they gave example headings but we can decide to include only those with real content. The posting does not have a separate "Skills" heading; but we could still create a Skills section if we extract skill list. However that would be creating a section not originally present; but allowed? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings if appropriate. It doesn't forbid creating a Skills section if we have skill content. However they also say "Prefer a few substantive sections over many thin ones." So maybe better to keep Requirements and Benefits and Pay and About the role and Responsibilities. That's 5 sections. Pay we can separate from Benefits because salary is specific. Could also include Pay within Benefits but they said separate Pay section if posting actually states them. The posting states salary range under Benefits list; but we could still make a Pay section for clarity. However that would be thin (just one line). Might be considered thin. Better to include Pay within Benefits? But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state salary range, so we can create Pay section. It's not thin if we also include compensation may vary line. That's two lines. Could be okay. We also need to ensure we don't include filler like "commensurate with experience", "not specified", etc. We have none. We must output only HTML fragment, no /, no markdown. Thus produce something like:

About the role

This role leads operational excellence across digital stewardship services, ensuring reliable, high-quality delivery for participants and partners. You will oversee service workflows, support operations, vendor coordination, and initiatives that improve efficiency and customer satisfaction. The position combines technical and product knowledge with process improvement, data analysis, and stakeholder management. You will collaborate closely with Product, Technology, Operations, and Participant Success teams to resolve complex issues and improve service experiences. The role also provides opportunities to influence product enhancements through participant feedback, service metrics, and root-cause analysis. As a people-focused leader, you will coach team members, encourage continuous learning, and help guide teams through operational change. The position is remote within the continental United States, with occasional travel of less than 10% primarily to Michigan and New York offices.

Responsibilities

• Maintain strong technical and product knowledge of digital stewardship services and related publishing and archiving processes.
• Oversee daily support operations and content workflows to ensure consistent, accurate, and high-quality service delivery.
... etc all items.

Requirements

• Bachelor’s degree in a related field or equivalent professional experience.
...

Benefits

• Medical, dental, and vision insurance plans.
• Employer-paid retirement contribution of 10%.
• Paid parental and caregiver leave.
• 22 days of paid time off.
• 11 paid holidays.
• Up to 12 sick days.
• Wellness benefits.
• Remote work within the continental United States.
• Occasional travel, generally less than 10%, primarily to Michigan and New York offices.
• Benefits may be updated at the employer’s discretion over time.

Pay