Product Manager, Platform Services
About the role
and put the overview paragraph(s). The overview includes: "The Product Manager, Platform Services at CJ is responsible for shaping and executing the long-term strategy..." etc. We'll keep that. - Responsibilities: There's a "Responsibilities" section with bullet points. We'll output- for each bullet.
- Qualifications: There's a "Qualifications" section with bullet list (numbered). We'll output
- .
- Benefits: Additional Information includes many benefits: flexible time off, paid holidays, company-sponsored team-building events, employee referral program, annual recognition awards, hybrid work arrangements, parental bonding leave, backup care options, employee discount program, International SOS program, Business Resource Groups, plus earlier mention of competitive salaries, 401K matching, wellness programs, comprehensive medical/dental/vision coverage. Also mention "Hybrid role requiring 3 days a week in office." That's schedule? Actually schedule is hybrid: 3 days a week in office. So we can have a Schedule section with that detail. Also Pay section with compensation range.
We need to avoid boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove lines like "If you require accommodation..." and EEO statement. Also remove "Compensation Range: ..."? Actually we need to include Pay section, so we keep that but format as
. Also remove "The Company anticipates the application deadline..." etc. That's application instruction? It's not exactly instruction but maybe considered boilerplate; we should drop it. Also remove "Temporary roles may be eligible..." etc. That's benefits detail but maybe we can keep as part of Benefits? It's about medical coverage for temporaries; could be considered benefits but it's specific. However it's somewhat boilerplate; but we can keep if it's substantive. The instruction says: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The temporary roles line is not exactly those; it's about benefits. Might keep. 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 those we remove as per instruction. Let's extract sections: Company Description: Welcome to Our World ... (paragraph). This is about company, not role. Could be part of About the role? Might be separate "About the company". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". Could we put company description under About the role? Might be okay as it's context. But the instruction: "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." It doesn't forbid adding other headings not listed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we should use those headings only. So we should not add a heading like "Company Description". Instead we could fold that content into a short
under About the role or maybe under Overview. Probably best to put company description as a paragraph under About the role before the overview. Thus About the role section will contain: company description paragraph(s) + overview paragraph(s). We'll combine. Responsibilities: as given. Qualifications: as given. Benefits: compile all benefits and perks from Additional Information and also earlier mention of competitive salaries etc. But salary goes to Pay section. Benefits: flexible time off without accrual, generous number of paid holidays, company-sponsored team-building events, employee referral program, annual recognition awards, hybrid work arrangements for optimal work-life balance, parental bonding leave, backup care options for children and elders, employee discount program, International SOS program for global support, Business Resource Groups, competitive salaries (but that's Pay), 401K matching, wellness programs, comprehensive medical, dental, and vision coverage. Also mention "We equip our teams with advanced tools, training and career development opportunities". That's also a benefit (training, career development). Also "We work in an enthusiastic, collaborative team setting that values outstanding performance." That's culture, maybe not benefit. But we can include as part of Benefits? Might be okay. We need to avoid filler like "competitive salaries" if we put in Pay. So we will put salary in Pay. Schedule: hybrid role requiring 3 days a week in office. Pay: compensation range USD $88,540.00 - USD $127,155.00/Annually. We also have "This is the pay range the Company believes it will pay for this position at the time of this posting." That's part of Pay description. We should not include "Consistent with applicable law..." etc. That's legal boilerplate; remove. Also remove "The Company anticipates the application deadline for this job posting will be 10/23/2026." That's application instruction/boilerplate; drop. Also remove "If you require accommodation or assistance with the application or onboarding process specifically, please contact USMSTACompliance@publicis.com." That's application instruction; drop. Also remove "All your information will be kept confidential according to EEO guidelines." That's EEO boilerplate; drop. Also remove "Temporary roles may be eligible to participate in our freelancer/temporary employee medical plan through a third-party benefits administration system once certain criteria have been met." That's benefits detail but maybe not boilerplate; it's specific about temporary roles. Could keep under Benefits as a note. Also "For regular roles, the Company will offer medical coverage, dental, vision, disability, 401k, and paid time off." That's benefits; keep. Now we need to ensure we don't repeat info. We'll craft sections. Let's draft HTML:
About the role
Company description paragraph(s)...
Overview paragraph(s)...
Responsibilities
- ... each bullet from Responsibilities section (the bullet points start with "This role plays a critical part..." then bullet list after "The Product Manager Will Lead...". We need to capture all bullet points. The text after "The Product Manager Will Lead" includes many bullet-like sentences each starting with a capitalized phrase. We'll need to split them.
Let's extract bullet points from Responsibilities:
- This role plays a critical part in ensuring CJ operates as a unified platform. By defining and evolving the shared capabilities, experiences, and standards used across product domains, the Product Manager will help reduce duplication, improve customer experience, strengthen platform scalability and performance, and enable product teams to deliver new capabilities more efficiently.
- The role will also help shape CJ’s evolution toward an AI-enabled platform by defining the shared experience, ecosystem strategy, and governance through which domain-specific agents and MCPs can be discovered, trusted, and used consistently across CJ.
- The Product Manager Will Lead The Definition, Prioritization, And Execution Of CJ’s Platform Services Strategy And Roadmap Across The Following Core Pillars
Then sub-bullets:
* Identity, Access & Organization – Lead the strategy and evolution of CJ’s shared identity and access capabilities, including authentication, authorization, SSO, MFA, user identity, roles and permissions, user and company relationships, organizational access models, and other shared access capabilities.
* Shared Platform Experience – Define and evolve the common experiences that span the CJ platform, including global navigation, homepage and dashboard frameworks, cross-application experiences, search, notifications, user preferences, and other shared capabilities that create a cohesive customer experience.
* Design System & Experience Standards – Partner with UX and engineering to drive the evolution and adoption of CJ’s shared design system, UI and interaction standards, accessibility requirements, responsive experiences, and browser and device policies across product domains.
* Globalization & Localization – Lead the shared framework for delivering CJ experiences globally, including translations, locale behavior, regional formatting, currencies, dates, time zones, and other localization capabilities.
* Platform Configuration & Communications – Define shared capabilities for platform configuration, customer entitlements, feature enablement, preferences, notifications, alerts, announcements, and other common communication experiences.
* Shared Platform Integrations – Oversee third-party integrations that extend shared CJ platform capabilities and serve multiple areas of the business, while establishing clear ownership boundaries between shared platform integrations and integrations specific to individual product domains.
* Platform Performance & Experience Health – Partner across product and engineering teams to establish platform performance expectations, identify systemic experience issues, define platform health metrics, and prioritize improvements to the responsiveness, reliability, and overall quality of the CJ experience.
* AI Experience & Agent/MCP Ecosystem – Lead the vision for CJ’s shared AI experience and ecosystem, including the Agent Library, agent discovery, shared conversational experiences, AI governance, and the cross-platform strategy for Model Context Protocol (MCP). Establish the standards, discoverability, lifecycle expectations, and governance that enable domain product teams to build and operate their own agents and MCPs consistently across CJ. Domain product teams retain ownership of the business capabilities, agents, and MCP implementations specific to their respective areas.
* Cross-Platform Strategy & Governance – Establish and maintain the strategic roadmap for Platform Services, ensuring alignment with CJ’s broader product strategy, organizational priorities, and customer needs. Drive adoption of shared platform capabilities and standards across product domains to improve consistency, reduce duplication, and accelerate product development. Define and track platform adoption, performance, and experience-health metrics to measure success and inform future investment. Stay informed of emerging platform, identity, AI, and interoperability trends and translate relevant developments into opportunities for CJ’s platform strategy.
We need to preserve all that. We'll format as
- for each top-level bullet. The sub-bullets could be nested
- inside. That's okay.
Now Qualifications: list numbered items. We'll convert to
- . Qualifications text: "The ideal candidate will have significant experience defining and delivering shared platform capabilities within a complex product organization. Key qualifications include: 10+ years of product management experience, preferably within SaaS, enterprise platforms, commerce, advertising technology, or other complex technology environments. Demonstrated experience defining and executing platform product strategy across multiple product domains and engineering teams. Strong technical foundation, with an understanding of identity and access management, authorization, platform architecture, shared services, integrations, and modern web application architectures. Demonstrated ability to identify opportunities for reusable platform capabilities and drive their adoption across multiple product teams. Strong understanding of emerging AI product patterns, including AI agents and interoperability approaches such as Model Context Protocol (MCP), and the ability to translate evolving technologies into pragmatic product and platform strategies. Experience working closely with UX and engineering to deliver consistent, scalable, accessible, and high-performing customer experiences. Excellent communication, influence, and stakeholder management skills, with demonstrated ability to drive alignment and resolve ambiguous ownership across teams. Strong analytical and problem-solving abilities, with experience using data and product metrics to prioritize investments and measure platform success. Experience with Agile methodologies and modern product management practices. A Bachelor's or Master’s degree in Computer Science, Engineering, Business, or a related field is preferred." We'll make each as
- . Now Benefits: compile list. From Additional Information: - Flexible time off without the hassle of accrual
- inside. That's okay.
Now Qualifications: list numbered items. We'll convert to
- for each top-level bullet. The sub-bullets could be nested
- ... each bullet from Responsibilities section (the bullet points start with "This role plays a critical part..." then bullet list after "The Product Manager Will Lead...". We need to capture all bullet points. The text after "The Product Manager Will Lead" includes many bullet-like sentences each starting with a capitalized phrase. We'll need to split them.
Let's extract bullet points from Responsibilities:
- This role plays a critical part in ensuring CJ operates as a unified platform. By defining and evolving the shared capabilities, experiences, and standards used across product domains, the Product Manager will help reduce duplication, improve customer experience, strengthen platform scalability and performance, and enable product teams to deliver new capabilities more efficiently.
- The role will also help shape CJ’s evolution toward an AI-enabled platform by defining the shared experience, ecosystem strategy, and governance through which domain-specific agents and MCPs can be discovered, trusted, and used consistently across CJ.
- The Product Manager Will Lead The Definition, Prioritization, And Execution Of CJ’s Platform Services Strategy And Roadmap Across The Following Core Pillars
Then sub-bullets:
* Identity, Access & Organization – Lead the strategy and evolution of CJ’s shared identity and access capabilities, including authentication, authorization, SSO, MFA, user identity, roles and permissions, user and company relationships, organizational access models, and other shared access capabilities.
* Shared Platform Experience – Define and evolve the common experiences that span the CJ platform, including global navigation, homepage and dashboard frameworks, cross-application experiences, search, notifications, user preferences, and other shared capabilities that create a cohesive customer experience.
* Design System & Experience Standards – Partner with UX and engineering to drive the evolution and adoption of CJ’s shared design system, UI and interaction standards, accessibility requirements, responsive experiences, and browser and device policies across product domains.
* Globalization & Localization – Lead the shared framework for delivering CJ experiences globally, including translations, locale behavior, regional formatting, currencies, dates, time zones, and other localization capabilities.
* Platform Configuration & Communications – Define shared capabilities for platform configuration, customer entitlements, feature enablement, preferences, notifications, alerts, announcements, and other common communication experiences.
* Shared Platform Integrations – Oversee third-party integrations that extend shared CJ platform capabilities and serve multiple areas of the business, while establishing clear ownership boundaries between shared platform integrations and integrations specific to individual product domains.
* Platform Performance & Experience Health – Partner across product and engineering teams to establish platform performance expectations, identify systemic experience issues, define platform health metrics, and prioritize improvements to the responsiveness, reliability, and overall quality of the CJ experience.
* AI Experience & Agent/MCP Ecosystem – Lead the vision for CJ’s shared AI experience and ecosystem, including the Agent Library, agent discovery, shared conversational experiences, AI governance, and the cross-platform strategy for Model Context Protocol (MCP). Establish the standards, discoverability, lifecycle expectations, and governance that enable domain product teams to build and operate their own agents and MCPs consistently across CJ. Domain product teams retain ownership of the business capabilities, agents, and MCP implementations specific to their respective areas.
* Cross-Platform Strategy & Governance – Establish and maintain the strategic roadmap for Platform Services, ensuring alignment with CJ’s broader product strategy, organizational priorities, and customer needs. Drive adoption of shared platform capabilities and standards across product domains to improve consistency, reduce duplication, and accelerate product development. Define and track platform adoption, performance, and experience-health metrics to measure success and inform future investment. Stay informed of emerging platform, identity, AI, and interoperability trends and translate relevant developments into opportunities for CJ’s platform strategy.
We need to preserve all that. We'll format as
- .
- Benefits: Additional Information includes many benefits: flexible time off, paid holidays, company-sponsored team-building events, employee referral program, annual recognition awards, hybrid work arrangements, parental bonding leave, backup care options, employee discount program, International SOS program, Business Resource Groups, plus earlier mention of competitive salaries, 401K matching, wellness programs, comprehensive medical/dental/vision coverage. Also mention "Hybrid role requiring 3 days a week in office." That's schedule? Actually schedule is hybrid: 3 days a week in office. So we can have a Schedule section with that detail. Also Pay section with compensation range.
We need to avoid boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove lines like "If you require accommodation..." and EEO statement. Also remove "Compensation Range: ..."? Actually we need to include Pay section, so we keep that but format as