Digital Delivery Manager – AEM

Cheil USA/Digital Experience

 

Digital Delivery Manager - AEM

Project Manager, Digital Experience

Location: Plano, Texas

Working model: On-site at the Cheil office, five days per week

Employment type: Full-time

Position Summary

Cheil USA is seeking an experienced, client-facing, and hands-on Digital Delivery Manager - AEM / PM, Digital Experience to lead the delivery of web, mobile app, e-commerce, product, promotional, and evergreen digital experiences across a complex enterprise ecosystem.

This role owns digital initiatives from intake and requirements validation through prioritization, implementation, quality assurance, stakeholder approval, publishing, and post-launch validation. The role will coordinate business stakeholders, content authors, publishers, creative teams, QA, product teams, and technical partners across multiple locations and time zones.

This is not a purely administrative project-management position. The successful candidate must have practical Adobe Experience Manager experience and be comfortable working directly in AEM when needed. They should be able to navigate authoring environments, review pages and components, perform simple content updates, validate staging output, identify common content or configuration issues, and support publishing activities.

The ideal candidate combines strong stakeholder leadership with practical digital-experience and publishing knowledge. They can challenge incomplete requirements, translate business requests into executable plans, establish priorities, coordinate distributed teams, identify risks, and verify delivery outcomes directly rather than relying exclusively on status reports from others.

Key Responsibilities

Project and Stakeholder Leadership

• Serve as a primary operational partner to business, marketing, product, e-commerce, creative, legal, UX, technology, and delivery stakeholders across multiple business areas and workstreams.

• Own digital initiatives from intake and requirements validation through implementation, QA, stakeholder approval, go-live, and post-live validation.

• Translate business objectives, creative assets, product information, and source materials into clear briefs, acceptance criteria, dependencies, milestones, owners, and delivery plans.

• Evaluate incoming requests for completeness, feasibility, business impact, urgency, technical dependencies, and operational risk.

• Challenge unclear, incomplete, conflicting, or technically impractical requests and align stakeholders on an executable path before work begins.

• Facilitate decisions and communicate scope, priorities, risks, trade-offs, dependencies, and required stakeholder actions.

• Build trusted stakeholder relationships while maintaining clear accountability, realistic commitments, and transparent communication.

• Provide concise, decision-oriented status updates to stakeholders and leadership.

AEM and Digital Experience Operations

• Work directly in Adobe Experience Manager to review implementation and support delivery when operationally necessary.

• Navigate AEM authoring, preview, staging, approval, and publishing environments with confidence.

• Perform simple content and page updates when needed, including copy, links, images, metadata, page properties, and existing component configurations.

• Review the selection, configuration, placement, and behavior of AEM components against approved requirements and creative references.

• Validate page structure, content accuracy, links, assets, metadata, responsive behavior, accessibility considerations, and general publishing readiness.

• Support or execute publishing activities when necessary, following the appropriate approval, scheduling, and release controls.

• Review digital experiences across relevant devices, breakpoints, markets, and environments.

• Identify inconsistencies between approved requirements, creative references, authored content, staging output, and live behavior.

• Distinguish content-authoring issues from asset, product-data, workflow, integration, component, or platform defects.

• Partner with AEM authors, publishers, QA, product teams, creative teams, and technical teams to resolve content and platform-related issues.

• Support rollback, hotfix, and post-launch validation activities for urgent or business-critical releases.

Workflow and Delivery Management

• Manage JIRA-based workflows and operational queues, maintaining accurate ownership, status, priority, due dates, dependencies, comments, blockers, and decision records.

• Coordinate local, nearshore, offshore, and global delivery teams across multiple time zones.

• Establish clear handoffs, escalation paths, acceptance criteria, and delivery ownership across distributed teams.

• Balance competing requests using business impact, launch criticality, due dates, capacity, complexity, readiness, and operational risk.

• Monitor queue health, ticket aging, throughput, SLA performance, blocked work, rework, quality trends, and launch readiness.

• Proactively identify risks, remove blockers, and escalate issues early with evidence, impact, options, a recommended action, and a clear owner.

• Lead recurring delivery reviews and ensure decisions and follow-up actions are documented.

• Ensure urgent requests do not bypass necessary requirement, QA, approval, and release controls without a documented risk decision.

• Coordinate publishing windows, launch dependencies, contingency plans, and post-launch support.

Quality and Continuous Improvement

• Uphold digital-experience quality standards covering content accuracy, brand consistency, UX, responsive behavior, accessibility, legal requirements, links, assets, functionality, and platform behavior.

• Coordinate internal QA, stakeholder review, release approval, publishing, and post-live validation.

• Confirm that acceptance criteria are satisfied before recommending approval or publishing.

• Identify recurring process and quality gaps and implement practical improvements to intake, routing, documentation, authoring, QA, workflow discipline, and reporting.

• Use operational data, stakeholder feedback, and recurring delivery issues to recommend improvements.

• Contribute to publishing guidelines, checklists, workflow documentation, onboarding materials, and team enablement.

Required Qualifications

• 5–7 years of experience in digital project management, digital experience delivery, digital content operations, web production, e-commerce operations, or a related field.

• Demonstrated ownership of complex digital initiatives from intake and requirements validation through publishing and post-launch validation.

• Demonstrated hands-on experience using Adobe Experience Manager in an authoring and publishing environment.

• Ability to independently navigate AEM, review pages and components, perform simple content changes, validate staging output, and support publishing activities.

• Practical understanding of AEM pages, templates, components, assets, links, metadata, page properties, workflows, preview/staging, and publishing concepts.

• Strong client-facing and stakeholder-management experience, including the ability to challenge assumptions, negotiate priorities, facilitate decisions, and manage expectations.

• Advanced working knowledge of JIRA or a comparable enterprise workflow platform, including queue management, ticket hygiene, dependencies, reporting, and escalation.

• Strong understanding of digital QA and release readiness, including content accuracy, links, responsive behavior, accessibility, legal requirements, analytics considerations, and post-live validation.

• Experience coordinating distributed teams across multiple functions, locations, and time zones.

• Excellent written and verbal communication, with the ability to produce concise briefs, status updates, recommendations, decisions, and escalation messages.

• Strong organization, attention to detail, judgment, and ownership in a fast-paced and matrixed environment.

• Ability to operate effectively in both structured and ambiguous situations without waiting for perfect information.

• Ability to work on-site at the Cheil office in Plano, Texas, five days per week.

Preferred Qualifications

• Experience supporting large-scale consumer electronics, retail, e-commerce, or comparable enterprise digital ecosystems.

• Experience with AEM Sites, Assets/DAM, Content Fragments, or comparable Adobe Experience Cloud capabilities.

• Experience supporting product-detail pages, product-information workflows, merchandising, promotional campaigns, mobile app content, and evergreen digital experiences.

• Familiarity with product information management, commerce platforms, content fragments, mobile CMS tools, or product-data workflows.

• Experience working with content authors, publishers, QA, creative, UX, product, engineering, and agency teams.

• Familiarity with Confluence, operational dashboards, capacity planning, and delivery-performance metrics.

Success in This Role

• Business requests enter delivery with validated requirements, clear acceptance criteria, correct routing, and realistic timelines.

• The PM can independently inspect AEM implementation and identify issues without relying exclusively on publishers or QA.

• Simple content changes and urgent operational interventions can be handled directly when appropriate.

• Stakeholders receive clear ownership, timely decisions, proactive risk communication, and transparent trade-offs.

• Digital experiences are delivered accurately and on time, with fewer preventable blockers, handoff failures, and quality-related rework cycles.

• Operational queues remain current, visible, and actionable across teams and time zones.

• Content, UX, functional, and publishing issues are identified before launch whenever possible.

• Intake, authoring, QA, publishing, and reporting processes continuously improve.

Working Model

This is a full-time, on-site position based at the Cheil office in Plano, Texas. The Digital Delivery Manager – AEM is expected to work in the office five days per week. The role regularly collaborates with teams in North America and other global time zones. Occasional schedule flexibility may be required for critical launches, urgent escalations, publishing windows, or cross-region handoffs.