Skip to content
Wunderman Thompson

Technical Lead with Contentful

Katowice, Poland; Poznań, Poland; VML Enterprise Solutions PolandPoland
Staff · Freelance
POSTED 27 OCTVERIFIED 53M AGO
Apply Ask
Pay · H-1B filings
$99k
median · n=4 · FY26
Open for
7d
since 27 Oct
H-1B · FY26
8
3 PERM
Hiring · 30d
378
−2 net · open roles
TypeScriptReactAWS

Who We Are

VML is a global creative company that combines brand experience, customer experience, and commerce to create connected brands that drive growth. Guided by a Human First philosophy, VML is known for its innovative work for brands and consistently ranks among the world’s leading creative companies, including the WARC Creative 100. VML’s global network spans 55+ markets with principal offices in Buenos Aires, Kansas City, London, New York, São Paulo, Shanghai and Singapore.

VML is part of WPP, the trusted growth partner for the world's leading brands. Powered by exceptional talent and our agentic marketing platform WPP Open, WPP unites cutting-edge media intelligence and data solutions, creativity, production, enterprise solutions and expert strategic counsel.

For more information, please visit www.vml.com and follow along on LinkedIn #WeAreVML.

Contentful Technical Lead wanted to join a high-profile digital experience project for a major global brand.

The opportunity

This is a high-impact technical leadership role combining ownership of enterprise platform delivery, client-facing discovery and technical workshops with strong architectural influence and a balance between technical leadership and hands-on engineering.

You will help shape a modern, composable platform built around Contentful, React and an AWS-based integration and service layer, working closely with architects, engineers and client stakeholders. The project's technical landscape includes Contentful, AWS infrastructure, APIs and identity/profile services

A key part of the role is understanding Contentful as part of a wider technology ecosystem. You will make pragmatic technical decisions about what should be handled by Contentful out of the box, what belongs in the frontend or AWS middle layer, and how integrations with existing services should be designed.

The initial phase will focus heavily on technical discovery, turning requirements, existing architecture and integration constraints into clear technical decisions and an actionable implementation backlog.

What you’ll get to do

  • Lead technical discovery, facilitating client-facing workshops and translating business requirements into technical decisions.
  • Shape the overall implementation approach across Contentful, React, AWS services and enterprise systems.
  • Define clear boundaries between CMS capabilities, frontend functionality, integration/middleware services and backend business logic.
  • Decide where integrations should be implemented and define appropriate API and integration patterns.
  • Review and evolve Contentful content models, composition rules and reusable content patterns.
  • Shape the AWS-based integration and service layer connecting Contentful and the frontend with APIs, identity/profile services and other systems.
  • Turn discovery outcomes into technical scope, architecture and an actionable implementation backlog.
  • Lead engineers throughout delivery, providing hands-on guidance, code reviews and support with complex technical decisions.
  • Ensure strong engineering practices around security, performance, automated testing, CI/CD and observability.

These areas align with the planned technical discovery covering Contentful, AWS infrastructure, API contracts, profile services, security, CI/CD and integrations.

What you should have

  • Strong commercial experience with Contentful and headless CMS architectures.
  • Strong React and TypeScript experience in production-grade applications.
  • Good practical knowledge of AWS, particularly cloud-based services and integration layers.
  • Strong understanding of API design, middleware and system integration patterns.
  • Experience designing solutions where a headless CMS is part of a larger enterprise architecture, rather than a standalone platform.
  • Ability to make sound architectural decisions about what belongs in the CMS, frontend, middle layer or backend services.
  • Experience integrating CMS platforms with APIs, identity/profile services and other enterprise systems.
  • Proven experience leading technical discovery, requirements analysis and solution design.
Source · Wunderman ThompsonFirst seen 2 NovOriginal ↗