What are the responsibilities and job description for the Senior Product Manager, Web Platform position at Planet Pharma?
Description
The Role
We are looking for a product-minded strategist to lead the web platform requirements for Client's patient-facing portal. This person will define what web owns in the patient experience across brand.com, gene.com, and our portfolio of 80 brand websites, drive vendor integration for patient services, and serve as the voice of the web across patient services, marketing, IT, compliance, and external vendors.
This is not a build role. This is a define, align, and drive role. You will work across multiple teams to shape how patients interact with affordability tools, enrollment tracking, copay assistance, and treatment journey content, all rendered within our branded web experience using our enterprise design system.
What You Will Do
Define The Patient Web Experience
Required
Client is building a connected patient experience that spans affordability, enrollment, treatment journey tracking, and education, all within our branded web platform. This role is the bridge between patient strategy (what patients need) and web platform (how we build it). The decisions made in this role will shape how patients interact with clients across 40 brands.
The Role
We are looking for a product-minded strategist to lead the web platform requirements for Client's patient-facing portal. This person will define what web owns in the patient experience across brand.com, gene.com, and our portfolio of 80 brand websites, drive vendor integration for patient services, and serve as the voice of the web across patient services, marketing, IT, compliance, and external vendors.
This is not a build role. This is a define, align, and drive role. You will work across multiple teams to shape how patients interact with affordability tools, enrollment tracking, copay assistance, and treatment journey content, all rendered within our branded web experience using our enterprise design system.
What You Will Do
Define The Patient Web Experience
- Own the web platform requirements for the patient-facing portal in collaboration with patient services, data science, and CX teams
- Define what web builds vs what the vendor provides. The vendor is a data source, not the front-end. Patients stay in the branded experience.
- Map seven web touchpoints to specific API contracts and data sources: copay checker, enrollment tracker, prior authorization transparency, chatbot, education hub, consent center, and specialist/treatment locator
- Define the embed architecture: vendor affordability data rendered inside AEM brand pages using our enterprise design system
- Represent web platforms in governance decisions. Architecture decisions about the patient experience should not happen without the team that builds the patient experience.
- Translate patient journey phase definitions into web component requirements. Other teams define what the phases mean, you define how they render.
- Work with data teams on the semantic layer approach for real-time vs batch data in the portal
- Align with CMLR on modular approval pathways for portal content that currently sits outside our compliance process
- Coordinate with brand teams to ensure portal components are adopted, not bypassed
- Attend vendor discovery sessions as the web platform representative
- Facilitate alignment across patient services, marketing, IT, compliance, CX, and external vendors
- Diplomatically push back when decisions are made without web platform input
- Operate in ambiguity: PRDs are drafts, vendor capabilities are being discovered, org structure is evolving
- Provide clear recommendations with rationale, not just options
- Ensure portal components work across brands using the enterprise design system
- Spec the SSO/authentication approach (deep link, federated auth, or full integration)
- Define consent collection UX and how it syncs across systems
- Establish portal analytics: what we track, how it feeds back to patient strategy OKRs (call deflection, time to first treatment, enrollment rates)
Required
- Experience designing patient-facing digital experiences in pharma or healthcare
- Understanding of patient access programs: copay, enrollment, financial assistance, prior authorization workflows
- API-first architecture thinking. Can define data contracts between vendor platforms and web components without needing to write the code.
- Strong stakeholder management across marketing, IT, compliance, and external vendors
- Proven ability to facilitate alignment across competing priorities and diplomatically push back when needed
- Comfort operating in ambiguity with evolving requirements and org structures
- Bachelor's degree in business, technology, operations, science, marketing, related field, or equivalent experience
- 8-10 years of experience in digital product management, with at least 3 years in pharma or healthcare? to the Required section?
- Experience with AEM or enterprise CMS platforms (does not need to code, needs to understand what is possible)
- Familiarity with patient identity and consent management in healthcare (HIPAA, SSO, consent orchestration)
- Experience with Salesforce Health Cloud, CRM platforms, or patient engagement platforms
- Has worked on cross-brand or portfolio-level digital programs, not just single-brand campaigns
- Experience with design systems and component-based architecture
- Pharma/biotech industry experience with understanding of MLR/CMLR review processes
Client is building a connected patient experience that spans affordability, enrollment, treatment journey tracking, and education, all within our branded web platform. This role is the bridge between patient strategy (what patients need) and web platform (how we build it). The decisions made in this role will shape how patients interact with clients across 40 brands.