React + Next Program Manager

Program leadership for web experience delivery

• Drive end‑to‑end execution of initiatives that span the CMS, design system, and Next.js application layers.
• Translate business and content requirements into structured technical initiatives with clear milestones and measurable outcomes.
• Coordinate across engineering, design, content strategy, SEO, and marketing to ensure cohesive delivery.
• Manage dependencies across CMS schema changes, API integrations, front‑end components, and deployment workflows.
• Identify risks related to content migrations, breaking API changes, caching strategies, and release timing.

Technical partnership in a Next.js + headless CMS environment

• Participate in architectural discussions involving rendering strategies (SSR, SSG, ISR), routing, caching, and performance optimization.
• Understand CMS content modeling, API querying models (REST/GROG/GraphQL), and integration patterns well enough to challenge assumptions and unblock teams.
• Collaborate with engineering leads to ensure front‑end and CMS changes align with long‑term platform direction.
• Use analytics, Core Web Vitals, A/B testing data, and telemetry to guide prioritization and measure success.
• Support teams in adopting best practices for accessibility, SEO, and performance.

Communication and stakeholder alignment

• Produce clear written communication: program briefs, status updates, migration plans, and decision records.
• Ability to translate business and product requirements into structured delivery plans, epics, and tickets in Jira.
• Simplify complex technical issues—such as rendering tradeoffs or CMS schema impacts—for non‑technical stakeholders.
• Align engineering, design, and content teams around timelines, expectations, and quality standards.
• Facilitate decision‑making around content workflows, release processes, and cross‑team dependencies.

Operational excellence for web platforms

• Coordinate postmortems for production issues, including rendering failures, broken content, or CMS outages, and drive long‑term fixes.
• Improve processes around content publishing, preview environments, QA workflows, and deployment pipelines.
• Champion performance, reliability, and accessibility as core pillars of the web experience.
• Promote consistent use of design systems, component libraries, and CMS governance.