Remote - Full-Stack Platform Engineer with Contentstack Launch + Next.js Experience - CH

Role: Full-Stack Platform Engineer 

Duration: 12 Months
Location: Remote

Role and responsibilities:

Full-Stack Platform Engineer (Content stack Launch + Next.js) — Focus Features and UAA/UPAH Scale

About the role

You will be the primary engineer developing, operating, and troubleshooting two high-visibility content sites built on a shared stack: Next.js/React delivered via Contentstack Launch with SSR and CDN caching/revalidation. Editorial changes publish into time-based cache windows rather than instantly.

Backend/platform scope spans: title/asset ingestion from OVC with assets from CVP/MPXinto Content stack (in a separate AWS account) for UAA/UPAH, plus AWS serverless features and mParticle integration for Focus Features, with DataDog planned and Cloudflare being decommissioned.

Required years of experience:

• 7+ years professional software engineering for large-scale web platforms.
• 3+ years building and operating Next.js/React applications with SSR and CDN caching/revalidation.
• 2+ years hands-on with headless CMS and Contentstack Launch (content models, environments/builds, cache invalidation triggers).
• 2+ years’ operating AWS serverless workloads (e.g., Lambda, API Gateway) and production integrations (e.g., mParticle).
• 2+ years production monitoring/alerting and incident response (e.g., DataDog planned adoption).
• Experience with media title/asset ingestion flows (OVC, CVP/MPX → CMS) and coordinating across accounts/environments.

Key responsibilities

• Frontend (Next.js/React + SSR)
• Own SSR routes/components, performance, accessibility/SEO; manage cache-controlheaders and confirm edge caching/revalidation behavior.
• CMS and Launch operations (Contentstack)
• Evolve content models; manage Launch environments/builds and automations that trigger page-level cache invalidation after publish.
• Caching and freshness
• Tune time-based cache policies and revalidation for page types (e.g., titles, lists, search;typical windows around 5 minutes, configurable).
• Ingestion and data quality (UAA/UPAH)
• Maintain mappings/transforms from OVC/CVP/MPX into Contentstack; align data freshness with cache windows; coordinate with the separate AWS account.
• Serverless features and integrations (Focus Features)
• Operate and troubleshoot AWS serverless features (e.g., Insiders, Facebook Leadgen) and maintain mParticle integration paths.
• Observability, reliability, and releases
• Implement/maintain monitoring and alerting (DataDog planned), create runbooks, lead incident response across frontend/Launch, ingestion, and serverless paths.
• Own CI/CD via Content stack Launch; coordinate release timing with cache revalidation and ingestion cycles; support system simplification (e.g., Cloudflare decommission).

Minimum qualifications

• Proficiency with Next.js/React SSR and CDN caching/revalidation at scale.
• Hands-on expertise with Content stack Launch operations and page-level cache invalidation flows.
• Experience operating AWS serverless features and data integrations (including mParticle for membership features).
• Demonstrated ownership of ingestion pipelines for media metadata and assets into a CMS(OVC/CVP/MPX → Content stack).
• Solid monitoring/alerting, on-call participation, and incident response.

Preferred qualifications

• Introducing or maturing DataDog dashboards/APM/alerts; driving platform simplification (e.g., retiring secondary CDN components like Cloudflare).
• Strong collaboration with editorial teams on caching expectations and publishing workflows; tuning TTLs and revalidation behavior.
• Primary troubleshooting domains
• CDN cache headers/revalidation, stale content windows.
• Ingestion timing/field mapping issues across OVC/CVP/MPX into Contentstack.
• Serverless endpoints/integrations for Insiders/Leadgen and related data paths.
• Optional QA partnership
• Add a part-time QA to automate regression around SSR routes, cache headers/revalidation, CMS publishing/invalidation workflows, ingestion field mappings, and basic serverlessendpoint checks.