AEM Lead
Remote
- Experience
- 6–9 years
- Employment
- Full-time
- Work mode
- Remote
- Salary
- Not disclosed
- Deadline
- Apply by 1 Nov 2026
- Posted
- 2026-08-25
Required skills
| Skill | Experience | Level |
|---|---|---|
| Java 8/11+ | 5+ years | Intermediate |
| AEMaaCS architecture | 3+ years | Intermediate |
| Java (All Versions) | 6+ years | Intermediate |
| JavaScript | 1+ years | Intermediate |
| Adobe Experience Manager - AEM | 6+ years | Intermediate |
| Open Service Gateway Initiative - OSGi | 5+ years | Intermediate |
| Sling | 4+ years | Intermediate |
| Cloud Migration | 3+ years | Intermediate |
| Dispatcher | 3+ years | Intermediate |
| Java EE | 5+ years | Intermediate |
| Java 21 | 5+ years | Intermediate |
| AEM Assets | 4+ years | Intermediate |
| SPA | 3+ years | Intermediate |
About the role
AEM Lead — Job Description
Hands-On | Cloud Migration | SPA | DAM
Overview
We are seeking an experienced AEM Lead who genuinely loves to code and solve problems. This is a
hands-on role — you will be responsible for enhancing and modifying the Adobe Experience Manager platform,
with strong emphasis on AEM Sites, MSM-based eCommerce implementations, Digital Asset Management
(DAM), and an upcoming migration to AEM as a Cloud Service (AEMaaCS). You will collaborate with
cross-functional teams to deliver robust, scalable digital solutions, while staying actively involved in writing and
reviewing code rather than purely overseeing it.
Key Responsibilities
• Write, build, and ship AEM code daily — components, templates, OSGi services, workflows, and Groovy
scripts — while staying hands-on rather than purely delegating.
• Collaborate with business analysts, project managers, and client stakeholders to analyze requirements and
develop tailored AEM technical solutions.
• Design, implement, and customize AEM Assets (DAM) features, including metadata schemas, asset
processing workflows, folder structures, and governance models.
• Develop AEM components, templates (static/editable), dialogs, OSGi services and workflows, and Groovy
scripts for content migration, bulk operations, and administrative tasks.
• Architect and manage Multi-Site Manager (MSM) configurations for large-scale, multi-locale eCommerce
sites, including live copies, rollout configs, and blueprint/inheritance models.
• Lead and execute migration from AEM 6.5 (AMS/on-prem) to AEM as a Cloud Service (AEMaaCS) —
including content migration, code refactoring for cloud compatibility, repoinit scripts, and immutable
repository restructuring.
• Build and support SPA-based AEM implementations using the AEM SPA Editor framework (React
preferred), ensuring smooth integration with AEMaaCS cloud authoring and Sling-based backend
architecture.
• Leverage Apache Sling features specific to AEMaaCS: resource resolution, Sling Models, Sling Servlets,
and cloud-aware content architecture.
• Extend and integrate AEM with third-party systems (eCommerce platforms, CRM, PIM) ensuring seamless
client experiences on cloud infrastructure.
• Optimize AEM application performance including dispatcher configurations, CDN setup and caching
strategies (cache invalidation, edge configurations, TTLs), query optimization, and efficient code.
• Provide production support and issue resolution for live AEM environments (author, publish, dispatcher,
CDN) and authoring support to client teams.
• Participate actively in code reviews, ensure adherence to coding standards, and advocate best
development practices.
• Diagnose, troubleshoot, and resolve issues across AEM environments and related custom applications.
Experience
• Minimum 8+ years of hands-on experience in Adobe Experience Manager (AEM) development, with
proven experience on AEM Sites and MSM-based eCommerce projects.
• Demonstrated experience (or strong readiness) with AEM as a Cloud Service (AEMaaCS), including cloud
migration planning and execution.
• Must genuinely enjoy hands-on coding and problem-solving — this is a builder role, not a purely
architectural or oversight position.
• Proven experience handling production issues/incidents and providing authoring support directly to client
teams in live AEM environments.
Core Technical Skills
Java & OSGi
• Strong proficiency in Java — JDK 8/11+ required; Java 21 (LTS) proficiency mandatory for cloud
readiness (virtual threads, records, sealed classes, pattern matching).
• Solid understanding of Java EE concepts (JSP, Servlets) and OSGi (Apache Felix).
• Hands-on experience writing and maintaining Groovy scripts within AEM (e.g., via the Groovy Console) for
data manipulation and automation tasks.
• Solid grasp of Object-Oriented Programming (OOP) principles and Sling Models.
AEM Architecture & Cloud
• Deep understanding of AEM architecture including Apache Sling, JCR, OSGi framework, and dispatcher
caching.
• Hands-on experience with AEMaaCS architecture: immutable /apps & /libs, mutable /content, Cloud
Manager pipelines, and environment-specific configurations.
• Proficiency with repoinit (Repository Initialization) scripts for automated content/node structure setup in
AEMaaCS.
• Experience restructuring on-prem AEM 6.x codebases (ui.apps, ui.content separation, package filters) to
comply with AEMaaCS repository constraints.
• Familiarity with AEMaaCS-specific services: Asset Compute Service, Content Distribution, Unified Shell,
and Adobe I/O Runtime integrations.
• Strong command of dispatcher configuration (caching rules, filters, virtual hosts) and CDN integration (e.g.,
Akamai, CloudFront, Fastly).
AEM Sites & MSM Skills
• 8+ years of experience on AEM Sites implementations, including complex MSM-based eCommerce
projects spanning multiple locales/regions.
• Experience configuring live copies, rollout configurations, and managing content inheritance across
blueprints.
• Experience migrating Sites content and configurations from AEM 6.5 to AEMaaCS including page
structure, templates, and editable template policies.
AEM Assets (DAM) Skills
• Extensive experience configuring and customizing AEM Assets including asset ingestion, metadata
management, and asset renditions.
• Practical experience with DAM functionalities: Smart Crops, Content Fragments, Experience Fragments,
Folder Metadata Schemas, and Asset Collections.
• Familiarity with Dynamic Media (Scene7) concepts and Scene7 API integration.
• Experience with AEMaaCS Content Hub / Assets as a Cloud Service including Asset Compute
microservices, cloud-native rendition processing, and Brand Portal integration.
Frontend & SPA Skills
• Strong foundational knowledge of front-end technologies: HTML5, CSS3, JavaScript (ES6+).
• Hands-on experience with SPA-based AEM projects using the AEM SPA Editor framework — React
preferred.
• Deep understanding of how Sling-based backend resource resolution integrates with SPA routing and
component mapping in AEMaaCS cloud environments.
• Experience adapting SPA implementations for AEMaaCS: Remote SPA, client-side routing with Sling
Model Exporters, and cloud-aware component model binding.
• Practical exposure to AEM's CoralUI/GraniteUI libraries for authoring interfaces.
Tools & Practices
• Proficient in version control systems, specifically Git.
• Familiarity with build automation tools (Maven, npm, webpack).
• Experience with Adobe Cloud Manager — pipeline setup, environment promotion, and deployment
strategies.
• Working knowledge of CDN configuration and management as part of overall AEM performance strategy.
• Comfort with AEMaaCS developer tools: RDE (Rapid Development Environment), Cloud Manager
developer console, log streaming, and OSGi configuration overlays.
AEMaaCS / Cloud Migration Requirements
Given our upcoming migration to AEM as a Cloud Service, candidates must demonstrate proficiency in the
following areas:
• Repository Migration: Experience using the AEM Modernization Tools and Best Practices Analyzer (BPA)
to assess and remediate on-prem codebases for cloud compatibility.
• Content Transfer Tool (CTT): Hands-on experience using CTT for migrating content from AEM 6.5 to
AEMaaCS, including extraction sets and ingestion strategies.
• Code Refactoring: Converting static templates to editable templates, refactoring custom OSGi configs,
removing deprecated APIs flagged by AEMaaCS deprecation scans.
• Cloud Manager Pipelines: Setting up and managing full-stack, frontend, and config pipelines;
understanding of quality gates (SonarQube, dispatcher validation, unit test coverage).
• Environment Architecture: Understanding of AEMaaCS environment tiers (Dev, Stage, Production), RDE
workflows, and environment-specific OSGi configurations.
• Index Definitions: Authoring and deploying custom Oak index definitions compatible with AEMaaCS
constraints (oak:index nodes under /oak:index).
• Sling Context-Aware Configurations: Migrating R