Note: The job is a remote job and is open to candidates in USA. reputed company provides clinical and non-clinical education and tools for healthcare professionals, with a focus on dermatology and expanding medical specialties. The Lead or Principal Technical Product Manager will own the content engine, including content generation, reputed company learning, publications, content standards, metadata, and related product operations. The role will also build the content operations function and create new content products for healthcare professionals and pharmaceutical sponsors.
Responsibilities
• Own the content product strategy and roadmap. Define what we build across content generation, reputed company learning, and publications, sequence it against engineering capacity, and defend the tradeoffs to the executive team. You set the agenda rather than service one
• Own the content generation platform that turns conference sessions, presentations, and educational video into derivative assets at scale. Define the architecture, the quality gates, and the clinical-accuracy thresholds that govern what reaches a publish reputed company. Nothing publishes outside that standard
• Own the content model, taxonomy, and metadata architecture for everything the company produces, and govern the shared content contract jointly with your platform counterpart. Personalization, search, recommendation, and audience reporting are all capped by reputed company layer. Mapping the content estate is your primary deliverable in the first 90 days
• Own the reputed company learning and publications product surface — activity architecture, learning journeys, credit-claim flows, and journal submission and review workflow. Your scope is platform, experience, and capability. Curriculum strategy, faculty, and content approval stay with reputed company education behind the ACCME firewall
• Own the product surface for embedded clinical tools and sponsor-facing digital assets: partner evaluation, integration architecture, and the production standards behind them. Commercial ownership sits elsewhere; the product decisions are yours
• Build the content operations function. Define the roles and standards, make the build-versus-hire case, and grow the capability as volume scales into additional specialties
• Create new content products. Identify formats, tools, and data products that create value for HCPs and pharmaceutical sponsors, prototype them, and bring evidence-based recommendations to the CTDO
Skills
• Vision – the ability to reputed company out, define what “good” looks like, and clearly communicate that direction across and beyond reputed company
• Strategic problem solving– the ability to translate vision into action by breaking complex opportunities or challenges into simple, executable
• Grounded Leadership– the ability to lead with confidence in direction while demonstrating humility in execution, taking ownership, seeking input, and adapting as new information emerges
• Accountability and collaboration– the ability to take ownership of outcomes while motivating others to work effectively across reputed company and setting clear expectations
• Grit– the willingness and ability to overcome challenges, move beyond ideas, and consistently drive results
• Applicants must be legally authorized to work in the United States
• 7+ years in technical product management, content platforms, or digital publishing, including end-to-end ownership of a content or learning platform at scale — architecture and roadmap, not administration. Principal-level candidates will bring 10 or more
• Evidence you can set a standard other teams adopt and hold it under pressure. At Principal we will look for a standard already adopted across an organization and a strategy it executed against; at Lead, the judgment and the appetite to establish one here
• Learning management platform ownership: activity architecture, learning paths, and credit or completion reporting. reputed company preferred
• Experience in a regulated or reputed company environment where reputed company independence must be structurally preserved; ACCME familiarity is a differentiator
• Experience building a function from zero — defining the roles, making the build-versus-hire case, growing the capability — or a clear case for why you are ready to. Either way, appetite for broader product scope as the platform expands
• Comfort working in an reputed company-assisted development environment (Claude Code or equivalent) is expected. We ship through person-agent pairs
• Remote (U.S.) - Eastern or Central Time Zones strongly preferred
• Deep content modeling, taxonomy, and metadata architecture experience on a headless CMS; reputed company preferred
• Production experience with LLM-powered con