Job Url: https://www.linkedin.com/jobs/search/?currentJobId=4326806729&distance=25.0&f_AL=true&f_TPR=r3600&f_WT=2&geoId=103644278&keywords=software%20engineer&origin=JOB_SEARCH_PAGE_JOB_FILTER&start=25 Job Description: Full Stack Platform Engineer Orlando, FL · 39 minutes ago · 11 applicants Promoted by hirer · No response insights available yet Remote Matches your job preferences, workplace type is Remote. Contract Easy Apply Save Save Full Stack Platform Engineer at IMR Soft LLC Full Stack Platform Engineer IMR Soft LLC · Orlando, FL (Remote) Easy Apply Save Save Full Stack Platform Engineer at IMR Soft LLC Show more options Your profile is missing required qualifications Show match details Help me update my profile BETA Is this information helpful? Get personalized tips to stand out to hirers Find jobs where you’re a top applicant and tailor your resume with the help of AI. Try Premium for PKR0 Meet the hiring team Srikanth Ch 3rd Sr Technical Recruiter at IMR Soft LLC Job poster Message About the job Role name: Full-Stack Platform Engineer Work Location: Orlando (remote) Duration: Long term contract 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 Content stack 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 Cloud flare 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 CDNcaching/revalidation. 2+ years hands-on with headless CMS and Content stack 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-control headers and confirm edge caching/revalidation behavior. CMS and Launch operations (Content stack) 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 Content stack; 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 behaviour. Primary troubleshooting domains CDN cache headers/revalidation, stale content windows. Ingestion timing/field mapping issues across OVC/CVP/MPX into Content stack. Serverless endpoints/integrations for Insiders/Leadgen and related data paths. Optional QA partnership