Digital Workspace Product Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, legal, application instructions, cookie/navigation, etc. Must preserve all substantive info. We need to parse the posting. Key info: - Title: Digital Workspace Product Manager (but we don't repeat as heading) - Location: New York City CEO Office Location Hybrid (maybe location info) - Anticipated deadline: September 25, 2026 before 5pm EST. Position may close early if application limit is met. Apply promptly for full consideration. (application instructions - we should remove application instructions? The instruction says remove application instructions. So we should drop deadline and apply promptly lines. However location maybe part of "About the role"? Could be included in a short paragraph. - The Opportunity paragraph: description of role. - Role-Specific Responsibilities: includes description of product manager (digital workplace) owning suite of digital tools, etc. - Who We Are: description of CEO. - Who You Are: list of qualifications/experience requirements. - What You’ll Be Responsible For: detailed responsibilities bullet list. - Compensation And Benefits: salary range $98,000-$104,000, plus benefits description. - More About Us: mission statement etc. - Also there is a line: "We are a workplace that promotes continual learning and teamwork, offering lunch and learns, team outings, holiday gatherings and more for our staff." That's part of benefits. - Also "We recognize that salary is a part of the overall compensation package and also provide a comprehensive benefits package, including medical and dental coverage, as well as professional development opportunities to our staff. We also offer paid parental leave, participation in a retirement plan, sick and vacation leave, paid holidays and more." - Also "We are a workplace that promotes continual learning and teamwork, offering lunch and learns, team outings, holiday gatherings and more for our staff." - Also "More About Us" paragraph. - Also "Center for Employment Opportunities believes that everyone deserves the chance to shape a stronger future for themselves, their families, and their communities. People who are justice involved are highly encouraged to apply for vacant positions at all levels. CEO is committed to the CROWN Act, and creating an open space where our employees can present as their true authentic selves. All qualified applicants will be considered for employment without unlawful discrimination based on ..." That's EEO boilerplate; we should remove. - Also "Please note that due to the volume of resumes received, we are unable to contact each applicant regarding the status of each position or reply to candidates' inquiries via phone or email." That's application instruction; remove. - Also "IND 1" maybe some code; remove. Thus we need to produce sections: Potential sections: - About the role (maybe combine The Opportunity and Who We Are? Actually "About the role" could be the opportunity paragraph. Could also include location/hybrid info. - Responsibilities: could be Role-Specific Responsibilities + What You’ll Be Responsible For (maybe combine). But we need to avoid duplication. The posting has "Role-Specific Responsibilities" describing the digital workplace role, then "What You’ll Be Responsible For" with bullet list. Both are responsibilities; we can combine into one Responsibilities section. - Requirements / Qualifications / Skills: The "Who You Are" list includes experience, skills, certifications. Could split into Requirements (experience) and Skills (specific abilities) and Qualifications (certifications). But we prefer few substantive sections. Could make one "Qualifications" section that includes all the bullet points from Who You Are. - Benefits: include compensation and benefits description. - Pay: we have salary range; we could make a Pay section with salary range. - Schedule: not mentioned; no schedule info (hybrid maybe but not schedule). So we should not create Schedule section. Thus we will have sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. Must not include filler like "commensurate with experience". Ensure we don't create empty sections. Let's extract substantive content. About the role: From "The Opportunity At CEO, Product Managers own a portion of the organization’s technology ecosystem and staff user experience with a focus on ensuring efficient, compliant, and integrated systems that minimize user friction. Product Managers blend strategic product management, systems support, business process improvement, and change management to enable the organization to scale its impact across 650+ employees and 30+ sites. By defining and executing multi-year product roadmaps, Product Managers unify staff-facing applications, optimize workflows, and drive user adoption in alignment with organizational goals." Also location/hybrid: "New York City CEO Office Location Hybrid". Could include as a short paragraph. Thus About the role paragraph could combine those. Responsibilities: We have Role-Specific Responsibilities paragraph: "CEO has several Product Management roles with differing functional scopes, but with shared underlying responsibilities. The Product Manager (Digital Workplace) owns the suite of digital tools that connect, empower, and support staff across all sites. This includes user devices, enterprise collaboration tools, project management/workflow automation software (e.g., Monday.com), Google Workspace, and AI assistants This role unifies employee-facing applications to maximize productivity, streamline workflows and enable CEO to scale its impact. They focus on frontline non-profit operations, eliminating friction between central staff, office-based personnel, and mobile/frontline teams to improve communication, efficiency, and service delivery." Then "What You’ll Be Responsible For" bullet list: - Technology Strategy Support & Roadmap Execution - Own the multi-year product roadmap for assigned technologies, ensuring alignment with organizational goals and tech strategy in partnership with Senior Leadership. - Balance the specific daily needs of operational teams with the organization's overall need for consistent, accurate data and security. - Manage the complete product lifecycle from planning, co-leading implementations, and ongoing optimization through to eventual decommissioning or modernization. - Work with business and product leadership to prioritize backlogs and initiatives based on organizational capacity and impact. - Solutions Identification & Design - Lead internal product discovery, conducting deep dives to map workflows across departments and translate distinct stakeholder needs into technical specifications. - Dedicate time to understanding specific user needs (e.g., mobile/frontline vs. central staff; functional finance teams vs. general staff). - Lead solution identification and co-design processes in collaboration with internal stakeholders, technical teams, external implementation providers, and software vendors. - Implementation & Change Management - Serve as a bridge and functional translator between technical infrastructure/vendor teams and non-technical operational staff. - Co-lead organization-wide change management, designing role-specific onboarding materials, proactive communication strategies, and training programs to boost tool proficiency and adoption. - Establish robust feedback loops and user research practices to uncover system friction and continuously iterate on solutions. - Ongoing Governance & Operations Support - Partner with IT Leadership, Security, Compliance, Legal, and Finance to establish governance frameworks, user permission structures, data security levels, and change control protocols. - Manage vendor relationships, configuration partners, and implementation consultants, holding them accountable to project timelines and technical standards. - Create and maintain comprehensive documentation and Standard Operating Procedures (SOPs) to support sustainable maintenance and growth. - Define, track, and optimize system KPIs related to platform adoption, speed-to-close/operational metrics, data accuracy, and user satisfaction. - Audit and optimize data flows, system performance, and API connections to prevent data fragmentation. - Perform other duties as assigned. We need to preserve all substantive info; we can keep these bullet points as

  • . Might need to keep sub-bullets? The instruction says use
    • for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can keep flat list with each bullet as a line item; we could keep the headings as part of list items (like "Technology Strategy Support & Roadmap Execution" as a
    • with subpoints? Might be better to keep as
    • with the heading bold? But we cannot add extra formatting beyond HTML; we could use inside
    • . That's okay. However we must not invent content. We'll keep the headings as part of the list items. Thus we can produce a
      with each bullet as
      • . For sub-bullets, we could either make them separate
      • items indented? But we can't use CSS; we could just keep them as separate
      • items, but that would lose hierarchy. However the instruction didn't require preserving hierarchy, just preserve all substantive information. So we can flatten: each line that starts with a dash becomes a
      • . That includes the headings like "Technology Strategy Support & Roadmap Execution" as a line item, then its sub-bullets as separate items. That preserves all info. Thus we will produce a list:
      • Technology Strategy Support & Roadmap Execution
      • Own the multi-year product roadmap for assigned technologies, ensuring alignment with organizational goals and tech strategy in partnership with Senior Leadership.
      • Balance the specific daily needs of operational teams with the organization's overall need for consistent, accurate data and security.
      • Manage the complete product lifecycle from planning, co-leading implementations, and ongoing optimization through to eventual decommissioning or modernization.
      • Work with business and product leadership to prioritize backlogs and initiatives based on organizational capacity and impact.
      • Solutions Identification & Design
      • Lead internal product discovery, conducting deep dives to map workflows across departments and translate distinct stakeholder needs into technical specifications.
      • Dedicate time to understanding specific user needs (e.g., mobile/frontline vs. central staff; functional finance teams vs. general staff).
      • Lead solution identification and co-design processes in collaboration with internal stakeholders, technical teams, external implementation providers, and software vendors.
      • Implementation & Change Management
      • Serve as a bridge and functional translator between technical infrastructure/vendor teams and non-technical operational staff.
      • Co-lead organization-wide change management, designing role-specific onboarding materials, proactive communication strategies, and training programs to boost tool proficiency and adoption.
      • Establish robust feedback loops and user research practices to uncover system friction and continuously iterate on solutions.
      • Ongoing Governance & Operations Support
      • Partner with IT Leadership, Security, Compliance, Legal, and Finance to establish governance frameworks, user permission structures, data security levels, and change control protocols.
      • Manage vendor relationships, configuration partners, and implementation consultants, holding them accountable to project timelines and technical standards.
      • Create and maintain comprehensive documentation and Standard Operating Procedures (SOPs) to support sustainable maintenance and growth.
      • Define, track, and optimize system KPIs related to platform adoption, speed-to-close/operational metrics, data accuracy, and user satisfaction.
      • Audit and optimize data flows, system performance, and API connections to prevent data fragmentation.
      • Perform other duties as assigned.
      That preserves all. Qualifications: From "Who You Are": list of statements each ending with a period. Let's extract each sentence. "You have at least 5+ years of experience in digital product management, digital workplace management, or IT product ownership." "You have a track record of establishing product visions, maintaining roadmaps, prioritizing backlogs, and executing cross-functional tech deployments." "You have proven ability to translate complex operational needs into practical, intuitive technical workflows." "You have strong stakeholder management and change management skills with experience designing training and adoption strategies." "You have experience supporting distributed organizations with complex multi-site operational structures."