Product Manager
- for any list of duties/requirements/benefits. Use
for prose. We must not include markdown fences. Just raw HTML. Let's extract content. About the role: The Overview paragraph(s). Let's capture: "Overview: Product Manager Paramount is seeking a Product Manager to join our Product Design & Development team, reporting to the Product Lead. This team sits under the HR Product team whose focus is to optimize the digital ecosystem that powers all HR processes and drives strategic operational change across the company. The Product Design & Development team is primarily dedicated to designing, building, and scaling AI-driven tools, automations, and solutions that enhance efficiency, improve decision-making, and deliver elevated experiences to our employees and internal stakeholders — thoughtfully applying AI to pain points and growth opportunities to streamline operations and empower our organization through intelligent automation and enablement. Our goal is to solve complex business problems, design innovative solutions, and transform the way we deliver HR Operations across all functions. Our ideal candidate is great at communication, highly organized, detail oriented, critical thinker, tech savvy, and driven to learn." We could keep that as prose in
. Might split into multiple paragraphs but okay. Responsibilities: The bullet list after "Responsibilities include but are not limited to:" then a paragraph describing. Let's extract each responsibility sentence. From text: "We are seeking a mid-level Product Manager to partner closely with the Product Lead in spearheading the HR technology roadmap forwardIn this role, you will take meaningful ownership of project delivery from intake to launch — ensuring solutions are impactful, running ceremonies and driving progress across cross-functional teams, and keeping stakeholders informedYou will own your own product areas over time, as you build domain expertiseThis is an early-stage product practice — and a rare opportunity to shape how product management is practiced from the ground upThe right candidate is a self-starter, brings structure to ambiguity, earns trust quickly, and operates with confidence and authority across engineering, design, and business stakeholdersHelp to drive the product roadmap through defining priorities, sequencing work, and making well-reasoned tradeoffs that reflect both business value and technical feasibilityHelp with project delivery end-to-end — from stakeholder intake through launch — ensuring active workstreams are tracked, blockers are surfaced early, and the right people are aligned at every stageHelp collect feedback, analyze user insights and engaging HR stakeholders directly, asking the right questions, and translating complex business needs into structured PRDs, user stories, acceptance criteria, and actionable Jira ticketsHelp to create process maps and prototypes to help communicate product design and functionality based on gathered requirements and user feedbackRun and continuously improve sprint ceremonies — standups, sprint planning, backlog grooming, and retrospectives — in close coordination with engineers and platform developers, modeling agile best practices for the teamChampion change management and adoption for product deployments by helping to create training documents and monitoring usage to ensure tools and solutions are embraced, not just deployed" It's a run-on but we can split into logical items: - Partner closely with the Product Lead in spearheading the HR technology roadmap forward. - Take meaningful ownership of project delivery from intake to launch — ensuring solutions are impactful, running ceremonies and driving progress across cross-functional teams, and keeping stakeholders informed. - Own your own product areas over time, as you build domain expertise. - Shape how product management is practiced from the ground up (early-stage product practice). - Operate as a self-starter, bringing structure to ambiguity, earning trust quickly, and operating with confidence and authority across engineering, design, and business stakeholders. - Drive the product roadmap through defining priorities, sequencing work, and making well-reasoned tradeoffs that reflect both business value and technical feasibility. - Manage project delivery end-to-end — from stakeholder intake through launch — ensuring active workstreams are tracked, blockers are surfaced early, and the right people are aligned at every stage. - Collect feedback, analyze user insights and engage HR stakeholders directly, asking the right questions, and translating complex business needs into structured PRDs, user stories, acceptance criteria, and actionable Jira tickets. - Create process maps and prototypes to help communicate product design and functionality based on gathered requirements and user feedback. - Run and continuously improve sprint ceremonies — standups, sprint planning, backlog grooming, and retrospectives — in close coordination with engineers and platform developers, modeling agile best practices for the team. - Champion change management and adoption for product deployments by helping to create training documents and monitoring usage to ensure tools and solutions are embraced, not just deployed. We'll put each as
- .
Requirements: Combine Basic Qualifications and Additional Qualifications.
Basic Qualifications list:
- 3-5 years of experience in product management, preferably within enterprise technology, HR technology, or a large matrixed organization
- A true self-starter — someone who sees what needs to be done, does it, and raises the bar for how the team operates
- You don’t wait to be told; you identify the gap, propose the solution, and lead by example
- Experience using visualization tools (PowerPoint, Canva, etc.), process mapping tools (Lucid Chart, etc.), and prototyping tools (Figma, Lovable, etc.)
- Remarkable written and verbal communication skills, with the ability to produce clear PRDs, crisp stakeholder updates, and documentation that others can build from
- Experience running agile ceremonies (sprint planning, standups, retrospectives, backlog grooming) and managing delivery in tools such as Jira, Confluence, Asana, or similar
- Proven ability to manage multiple concurrent projects and shifting priorities without losing quality, momentum, or stakeholder trust
- Experience with UI/UX and product design, preferably in productivity tools that leverage AI and align to business objectives
- Ability to measure adoption, run user feedback sessions, and evaluate the user journey and determine opportunities for improvement
- Bachelor’s degree in Business, Information Systems, Computer Science, or a related field
Additional Qualifications:
- Familiarity with AI-powered tools and automation platforms and genuine curiosity about how they apply to productivity and operations
- Prior experience in a consulting or client-facing role that required translating ambiguous business needs into structured, actionable deliverables
- Working knowledge of HR processes and systems across functions like Compensation, Talent Acquisition, Learning & Development, and HR Operations
We'll combine into one Requirements section (or maybe Qualifications). The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "Requirements" for qualifications. We'll list as
- .
Benefits: list from posting:
- medical, dental, vision
- 401(k) plan
- life insurance coverage
- disability benefits
- tuition assistance program
- PTO (or as dictated by CBA)
- bonus eligible
- Attractive compensation and comprehensive benefits packages (maybe redundant)
- Generous paid time off
- Opportunities for both on-site and virtual engagement events
- Unique opportunities to make meaningful connections and build a vibrant community, both inside and outside the workplace
- Access to life at Paramount (link) but we should not include links? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Links are substantive? Might be considered navigation? Probably we can keep them as part of benefits description but not as separate list items? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Links to benefits and life-at-paramount might be considered navigation? They are not boilerplate; they are informational. However they are URLs. Might be okay to keep as plain text? But we should not include markdown. We can include them as plain text within
. But better to keep benefits as list items without URLs. The "Check out our full list of benefits here: https://www.paramount.com/careers/benefits" is a link; could be considered navigation? It's a call to action. Might be considered application instruction? Not exactly. Safer to omit the link and just keep the benefit description. We'll list benefits as: - medical, dental, vision - 401(k) plan - life insurance coverage - disability benefits - tuition assistance program - paid time off (PTO) - bonus eligibility - attractive compensation and comprehensive benefits packages - generous paid time off (maybe duplicate) - opportunities for on-site and virtual engagement events - opportunities to make meaningful connections and build a vibrant community inside and outside the workplace We might combine similar items. Pay: Salary range: $110,000 - 147,600. Also note that starting pay depends on factors. We'll include that as prose. Schedule: Not present, omit. Now produce HTML:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Pay
...
Make sure no extra whitespace? It's fine. Now craft the prose. About the role paragraph: combine overview sentences. Let's write:Paramount is seeking a Product Manager to join the Product Design & Development team, reporting to the Product Lead. This team sits under the HR Product team, which focuses on optimizing the digital ecosystem that powers all HR processes and drives strategic operational change across the company. The Product Design & Development team is dedicated to designing, building, and scaling AI‑driven tools, automations, and solutions that enhance efficiency, improve decision‑making, and deliver elevated experiences to employees and internal stakeholders by applying AI to pain points and growth opportunities. The goal is to solve complex business problems, design innovative solutions, and transform the way HR Operations are delivered across all functions. The ideal candidate is great at communication, highly organized, detail‑oriented, a critical thinker, tech‑savvy, and driven to learn.
That seems good. Responsibilities list: we need to ensure each item is a complete sentence. Let's craft list: - Partner closely with the Product Lead in spearheading the HR technology roadmap forward.
- Take meaningful ownership of project delivery from intake to launch — ensuring solutions are impactful, running ceremonies and driving progress across cross‑functional teams, and keeping stakeholders informed.
- Own your own product areas over time as you build domain expertise.
- Help shape how product management is practiced from the ground up in this early‑stage product practice.
- Operate as
- .
Benefits: list from posting:
- medical, dental, vision
- 401(k) plan
- life insurance coverage
- disability benefits
- tuition assistance program
- PTO (or as dictated by CBA)
- bonus eligible
- Attractive compensation and comprehensive benefits packages (maybe redundant)
- Generous paid time off
- Opportunities for both on-site and virtual engagement events
- Unique opportunities to make meaningful connections and build a vibrant community, both inside and outside the workplace
- Access to life at Paramount (link) but we should not include links? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Links are substantive? Might be considered navigation? Probably we can keep them as part of benefits description but not as separate list items? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Links to benefits and life-at-paramount might be considered navigation? They are not boilerplate; they are informational. However they are URLs. Might be okay to keep as plain text? But we should not include markdown. We can include them as plain text within