Product Manager-Public Library Discovery

We need to output HTML fragment with sections: About the role? The posting includes intro about OCLC mission, then "Why join OCLC?" with benefits etc. Then "The Job Details Are As Follows" then description of role, responsibilities, qualifications, working conditions. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to extract content. Let's parse: - About the role: The description of the Product Manager role: "OCLC is seeking a Product Manager to lead product strategy and execution for Capira..." etc. That's about the role. So we can have

About the role

with paragraphs summarizing that content. - Responsibilities: There's a "Responsibilities" heading in the posting with bullet points: Product Strategy and Planning, Leadership and Management, Product Marketing Oversight and Consultation, Consultation on Portfolio Planning. We need to list duties as

• . Should preserve all substantive info. - Requirements/Qualifications: There's a "Qualifications" section with Minimum Required and Desired But Not Required. Also "Working Conditions". We need to decide which headings to use: Requirements, Qualifications, Skills. The posting includes qualifications (education, experience). Skills: communication, presentation, financial planning, understanding product lifecycle, etc. Could put under Skills. But we need to avoid thin sections. Perhaps combine Qualifications and Skills into one? But instructions: Use headings as appropriate. We can have

  Qualifications

  for education/experience requirements, and

  Skills

  for skills/competencies. Or we could have only Qualifications and include skills inside. But better to follow headings. - Benefits: The posting includes a "Why join OCLC?" paragraph with benefits: comprehensive Total Rewards package, competitive compensation, best-in-class health coverage, retirement plans with generous company contributions, commitment to well-being, walking meetings, patio lunch, hybrid work environment (3 days on-site), free use of on-site fitness center, gym sports, group exercise classes, game room, onsite catering and cafeteria subsidized, health and wellness events, work environments with individual and team spaces and latest technology tools, paid parental leave and adoption assistance, tuition reimbursement and Public Service Loan Forgiveness eligibility, company-subsidized pricing on local tickets and memberships. Also maybe mention "competitive compensation". Pay: they mention competitive compensation but not specific numbers. According to rule: do NOT create Pay section unless posting actually states them (specific numbers or range). It says "competitive compensation that reflects your unique contributions—performance, experience, and skills". That's vague, not a specific number. So we should not create Pay section. Schedule: they mention hybrid work environment: three days a week on-site, occasional additional days based on business needs. That's schedule info. So we can create Schedule section with that detail. - Benefits: we have many benefits listed; we can create Benefits section with those. - About the role: we have description. - Responsibilities: we have bullet points. - Qualifications: we have Minimum Required and Desired But Not Required. - Skills: we have communication, presentation, financial planning, understanding product lifecycle, etc. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format them. We need to ensure we don't omit any substantive info. Let's extract all substantive sentences. Original text: "Together we make breakthroughs possible. At OCLC, we build technology with a purpose: to connect libraries and make knowledge accessible worldwide, because we believe that what is known must be shared. Our teams work with complex global datasets, AI and machine learning, hybrid cloud solutions, and other technologies that connect people and organizations to the information they need. We value the power of unique perspectives and experiences to unlock innovation. At OCLC, your ideas matter, whether you have two years of experience or 20. You’ll learn, create, and problem-solve with technologists, product developers, librarians, researchers, marketing pros, and support teams around the world. Why join OCLC? OCLC is consistently recognized as a best place to work by several independent programs. We recognize and reward people and results with a comprehensive Total Rewards package. This means competitive compensation that reflects your unique contributions—performance, experience, and skills—along with exceptional benefits, including best-in-class health coverage, retirement plans with generous company contributions, and a commitment to your overall well-being. We know the best ideas don’t always happen at a desk. Take a walking meeting around our 100-acre campus or enjoy lunch on the patio. We’re committed to your success—both personally and professionally. Hybrid work environment: For many roles, three days a week on-site, with occasional additional days based on business needs. Free use of our on-site fitness center, gym sports, group exercise classes, and game room Onsite catering and cafeteria subsidized by OCLC Health and wellness events Work environments with individual and team spaces and the latest technology tools Paid parental leave and adoption assistance Tuition reimbursement and Public Service Loan Forgiveness eligibility Company-subsidized pricing on local tickets and memberships Join us in transforming how people everywhere access information and be part of a mission-driven team that makes a global impact. The Job Details Are As Follows OCLC is seeking a Product Manager to lead product strategy and execution for Capira, OCLC's public library discovery and engagement platform. This role will drive enhancements that help libraries deliver seamless digital experiences for their patrons, from resource discovery and account management to community engagement. Working closely with engineering, UX, and library partners, the Product Manager will balance customer needs, market trends, and business priorities to advance Capira's roadmap and support OCLC's commitment to innovation in public libraries. Produces product strategy, roadmaps, annual product plans, business cases, and monthly product reviews, launch plans, white papers, product presentations, market messaging, event support, competitive write-up and user personas. Contributes to the production of: Portfolio business plans, strategies, roadmaps, metrics, and operational plans; portfolio progress plans and reviews; user requirements and functional specs Responsibilities Product Strategy and Planning Oversees market analysis and develops product strategy and business case. Defines strategic product goals.Produces product roadmapCollaborates on release plans with DevelopmentCollaborates with finance in the production of product budgets and forecastsDevelops pricing strategies and product positioning plans which contribute to maximizing product profitability Leadership and Management Provides leadership to cross-functional product workgroups. Leads Product management meetings. Resolves conflicts and drives consensus.Facilitates collaboration and communication and secures commitment between Development and Product Management and other divisional workgroups towards achievement of common goals.Develops and monitors progress on product roadmap Product Marketing Oversight and Consultation Assists in the development of strategies for customer acquisition and retention; manages relationships with user groups and assists sales team in generation of marketing and awareness plans.Understands how and when to commission market research in order to develop and maintain expertise in markets served, alternative services, new technology, and related standards.Can generate appropriate information for market sizes by sector / territory and can generate market penetration statistics.Provides training and support to the sales and support team; may assist in significant sales calls.Analyses reasons for OCLC product wins and losses against competition and can provide meaningful information to aid product planning.Will work to define and rationalize user personasWill produce market/sector white papers Consultation on Portfolio Planning Provides input into portfolio business plans, roadmaps, strategies, metrics, and progress reports and reviews Qualifications Minimum Required Bachelors Degree or equivalent experience2 to 4 years experience in library services or library management systems2 to 4 years experience in product, project or program management2 to 4 years experience in supporting online/database services, preferably in the library fieldWell developed communication and presentation skillsStrong understanding of the Product Management Lifecycle modelDemonstrated ability with Financial planning and financial forecasting Desired But Not Required Experience in managing staff or team leadershipExperience leading cross functional workgroupsKnowledge of OCLC products and services Working Conditions: Normal office environment. ADA/EAA: The above statements cover what are generally believed to be principal and essential functions of this job. Specific circumstances may allow or require some people assigned to the job to perform a somewhat different combination of duties." We need to exclude boilerplate like "Working Conditions: Normal office environment. ADA/EAA: ..."? The ADA/EAA statement is likely boilerplate; but it's part of working conditions. Might be considered boilerplate but it's about the job description. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The ADA/EAA statement is legal boilerplate; we should remove it. Also "Working Conditions: Normal office environment." might be considered generic but it's substantive? It's a statement about working conditions. Might keep but it's generic. However we have schedule and benefits sections; we could include a short note about working environment under maybe "Working Conditions" but we don't have that heading. We could incorporate into Benefits or Schedule? Probably better to include a short paragraph under maybe "About the role" or separate "Working Conditions" but we don't have that heading. Since we only allowed headings list, we could put that info under Benefits? Not ideal. Perhaps we can include a short

  after the headings for any leftover meta. But instructions: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

  • for any list of duties/requirements/benefits, and

    for prose. 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. Thus we can have a short

    for minor metadata like "Working Conditions: Normal office environment." after the sections. Or we could incorporate into Benefits? Probably better to have a short

    after sections for any leftover. Now we need to ensure we don't create Pay or Schedule sections unless posting actually states them. Schedule: they state hybrid work environment: three days a week on-site, occasional additional days based on business needs. That's schedule info, so we can create Schedule section. Pay: they mention competitive compensation but not specific numbers; rule says do NOT create Pay/Schedule/Benefits sections unless posting actually states them. For Benefits, they do state benefits (list). So Benefits section is okay. Now we need to decide on Requirements vs Qualifications vs Skills. The posting has "Qualifications" heading with Minimum Required and Desired But Not Required. Also within that they list skills like communication, presentation, understanding product lifecycle, financial planning. Those could be considered skills. But we could put them under Qualifications as part of the bullet list. However we have separate Skills heading allowed. To avoid thin sections, maybe combine Qualifications and Skills into one Qualifications section that includes both experience/education and skills. But the instruction says "Prefer a few substantive sections over many thin ones." So we could have Qualifications section that includes both the experience/education requirements and the skills. Then we wouldn't need a separate Skills section. That seems reasonable. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Schedule. We need to ensure we include all substantive info. Let's extract content for each. About the role: Should include the introductory paragraphs about OCLC mission and the specific role description. The "Why join OCLC?" part is more about benefits/culture; but we already have Benefits section. However the "Why join OCLC?" includes some culture statements like "OCLC is consistently recognized as a best place to work..." etc. Those are more about benefits/culture; could go under Benefits or About the role? The Benefits section already covers benefits; but the culture statements like "best place to work", "recognize and reward people", "commitment to your success", "walking meeting", "