Job Description & Details
This contract role is a classic lift-and-shift content infrastructure project where you will be ripping out a legacy WordPress monolith and wiring up Contentful on Azure. If you enjoy building clean headless architectures without getting bogged down in CSS or frontend layout tweaks, this is a straightforward migration gig where you get to own the backend plumbing.
What You'll Actually Be Doing
Your primary objective is to take existing WordPress sites and translate their data structures into scalable Contentful content models and types. You'll be collaborating heavily with an internal marketing team and frontend devs who have already built the UI, meaning your job is to make sure the data flows smoothly via APIs, webhooks, and custom Azure-backed integrations. You will spend your days architecting reusable content blocks and automated publishing workflows so non-technical stakeholders can push updates without breaking the layout.
The Core Tech Stack
Contentful is non-negotiable here; they are explicitly asking for four-plus years of hands-on headless CMS experience, specifically building out models and templates from scratch. You will also need a solid grip on Microsoft Azure environments and backend API integrations, as you are responsible for making sure the new headless architecture actually communicates properly with the existing frontend application.
Interview Expectations
Expect the hiring team to grill you on how you handle complex content modeling migrations and map legacy relational structures into a headless paradigm. They'll likely ask you to whiteboard how you would set up automated webhooks and publishing workflows in Contentful to empower a non-technical marketing team, and they are secretly listening to see if you can translate business requirements into clean, scalable backend architecture without over-engineering it.
Application Advice
Your resume needs to heavily emphasize your Contentful credentials right at the top, specifically calling out keywords like headless CMS architecture, content modeling, API integrations, and WordPress migrations. Since this is an EST-aligned remote role with strict no-sponsorship policies, make sure your timezone availability and work authorization status are crystal clear to pass the initial ATS filter.