1

On Call Ovc Jobs (NOW HIRING)

On Call Ovc information

See salary details

$10

$17

$25

How much do on call ovc jobs pay per hour?

As of Jun 10, 2026, the average hourly pay for on call ovc in the United States is $17.91, according to ZipRecruiter salary data. Most workers in this role earn between $15.38 and $19.23 per hour, depending on experience, location, and employer.
What are the most commonly searched types of Ovc jobs? The most popular types of Ovc jobs are:
Infographic showing various On Call Ovc job openings in the United States as of June 2026, with employment types broken down into 1% As Needed, 79% Full Time, and 20% Part Time. Highlights an 94% Physical, 1% Hybrid, and 5% Remote job distribution, with an average salary of $37,257 per year, or $17.9 per hour.
Full-Stack Platform Engineer (Contentstack Launch + Next.js)

Full-Stack Platform Engineer (Contentstack Launch + Next.js)

eTeam

Los Angeles, CA

Other

Posted 4 days ago


Job description

JD:
Role Name: Full-Stack Platform Engineer
Work site: Los Angeles, US (Onsite)
Contract
Full-Stack Platform Engineer (Contentstack Launch Next.js) - FocusFeatures and UAA/UPAH Scale: At client location LA
About the role
You will be the primary engineer developing, operating, and troubleshooting two high-visibilitycontent sites built on a shared stack: Next.js/React delivered via Contentstack Launch withSSR and CDN caching/revalidation. Editorial changes publish into time-based cache windowsrather than instantly.
Backend/platform scope spans: title/asset ingestion from OVC with assets from CVP/MPXinto Contentstack (in a separate AWS account) for UAA/UPAH, plus AWS serverless featuresand mParticle integration for Focus Features, with DataDog planned and Cloudflare beingdecommissioned.
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 CDNcaching/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 productionintegrations (e.g., mParticle).
  • 2 years production monitoring/alerting and incident response (e.g., DataDog plannedadoption).
  • Experience with media title/asset ingestion flows (OVC, CVP/MPX ? CMS) and coordinatingacross 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 triggerpage-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 freshnesswith 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) andmaintain mParticle integration paths.
  • Observability, reliability, and releases
  • Implement/maintain monitoring and alerting (DataDog planned), create runbooks, leadincident response across frontend/Launch, ingestion, and serverless paths.
  • Own CI/CD via Contentstack Launch; coordinate release timing with cache revalidation andingestion 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 Contentstack Launch operations and page-level cache invalidationflows.
  • Experience operating AWS serverless features and data integrations (including mParticle formembership features).
  • Demonstrated ownership of ingestion pipelines for media metadata and assets into a CMS(OVC/CVP/MPX ? Contentstack).
  • 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.