AEM & EDS Developer

ROLE OVERVIEW

\n

We are looking for a seasoned Senior AEM Backend & EDS Developer to architect, build, and maintain enterprise-

\n

grade digital experience platforms. You will drive the development of robust AEM backend components, lead AEM

\n

as a Cloud Service migrations, and spearhead the adoption of Adobe Edge Delivery Services (EDS) — including

\n

migrations from AEMaaCS to EDS — to deliver sub-second web experiences. You bring at least one live, production

\n

EDS site to your track record, and are comfortable owning delivery end-to-end across authoring, build, and CDN

\n

layers.

\n

\n

KEY RESPONSIBILITIES

\n

\n

AEM Backend Development

\n

%B8; Design and develop custom AEM components, templates, and workflows using Java/OSGi, Sling, and JCR.

\n

%B8; Build and maintain RESTful and GraphQL APIs backed by AEM Content Services and Sling Models.

\n

%B8; Architect content structures, DAM integrations, and replication topologies for high-availability environments.

\n

%B8; Implement and lead AEM as a Cloud Service (AEMaaCS) migrations — content migration, index definitions,

\n

cloud-native configurations, and feature flag management.

\n

%B8; Conduct code reviews, enforce best practices, and mentor junior and mid-level engineers on AEM

\n

development standards.

\n

Edge Delivery Services (EDS) Development &Migration

\n

%B8; Own and deliver production EDS sites end-to-end — from initial block library setup through to go-live and

\n

post-launch stabilisation.

\n

%B8; Lead end-to-end migrations from AEM as a Cloud Service to Adobe Edge Delivery Services, including content

\n

modelling, block library porting, and authoring workflow transition.

\n

%B8; Author and optimise block libraries using vanilla JS and CSS in alignment with EDS conventions.

\n

%B8; Integrate EDS with AEM authoring (Universal Editor, Sidekick) and third-party data sources via

\n

SharePoint/Google Drive pipelines.

\n

%B8; Monitor and improve Core Web Vitals — LCP, CLS, and INP — across EDS properties.

\n

%B8; Automate EDS build and deployment pipelines using GitHub Actions and AEM Cloud Manager.

\n

CDN & Infrastructure — Akamai

\n

%B8; Configure and manage Akamai CDN properties — caching rules, edge logic, and cache invalidation strategies

\n

for AEM and EDS environments.

\n

%B8; Implement Akamai EdgeWorkers and Property Manager rules to optimise content delivery and enforce

\n

security policies.

\n

%B8; Collaborate with infrastructure teams on Akamai WAF, DDoS mitigation, and origin shield configuration.

\n

%B8; Troubleshoot cache-related performance issues across Akamai and AEM Dispatcher layers.

\n

Architecture & Collaboration

\n

%B8; Define and document technical architecture for AEM + EDS hybrid and full-EDS implementations.

\n

%B8; Partner with front-end engineers, UX designers, and solution architects to translate business requirements

\n

into scalable solutions.

\n

%B8; Drive adoption of observability tooling (Adobe Experience Platform Debugger, RUM, Akamai mPulse) for

\n

production monitoring.

\n

\n

REQUIRED QUALIFICATIONS

\n

\n

%B8; 8+ years of hands-on AEM development experience (AEM 6.4/6.5 and AEM as a Cloud Service).

\n

%B8; 3+ years working with Adobe Edge Delivery Services or AEM Franklin/Helix.

\n

%B8; At least one demonstrable production EDS site shipped and live — be prepared to share the URL and discuss

\n

architecture decisions during the interview.

\n

%B8; Demonstrated experience leading AEMaaCS-to-EDS migration projects end-to-end.

\n

\n

AEM Backend Expertise

\n

%B8; Deep proficiency in Java (8+), OSGi/Felix, Apache Sling, and JCR/Oak.

\n

%B8; Strong command of AEM component development — HTL/Sightly, Sling Models, WCM Core Components.

\n

%B8; Experience with AEM Dispatcher configuration, CDN strategies, and caching policies.

\n

%B8; Hands-on with AEM Cloud Manager pipelines, environment configurations, and RDE (Rapid Development

\n

Environments).

\n

%B8; Hands-on experience with AEM Experience Fragments and Content Fragments for omnichannel content

\n

delivery.

\n

%B8; Proficiency in headless AEM delivery using Content Fragment models and the AEM GraphQL API — including

\n

persisted queries, filtering, and pagination.

\n

\n

EDS / Franklin Expertise

\n

%B8; Proven track record of building and shipping production EDS sites using block-based authoring.

\n

%B8; Deep understanding of AEMaaCS-to-EDS migration patterns — content model mapping, block porting,

\n

redirect strategy, and authoring workflow changeover.

\n

%B8; Proficiency in vanilla JavaScript (ES2022+), Web Components, and progressive enhancement patterns.

\n

%B8; Understanding of EDS metadata, redirects, sitemap generation, and indexing pipeline.

\n

%B8; Experience with EDS performance auditing using Lighthouse CI and PageSpeed Insights.

\n

Akamai & CDN

\n

%B8; Hands-on experience configuring Akamai Property Manager, caching behaviours, and origin failover rules.

\n

%B8; Working knowledge of Akamai EdgeWorkers for server-side personalisation and request routing.

\n

%B8; Familiarity with Akamai mPulse or equivalent RUM tooling for CDN-level performance monitoring.

\n

%B8; Understanding of CDN cache invalidation strategies in the context of AEM publish/replication workflows.

\n

DevOps, Tooling

\n

%B8; Strong Git workflows, branching strategies, and code review practices.

\n

%B8; Experience with CI/CD pipelines — GitHub Actions, Jenkins, or Adobe Cloud Manager.

\n

%B8; Comfortable with Docker-based local development environments (AEM SDK).

\n

%B8; Familiarity with unit and integration testing — JUnit 5, Mockito, AEM Mocks (io.wcm).

\n

\n

NICE TO HAVE

\n

%B8; Adobe Certified Expert (ACE) — Sites Developer or Backend Developer certification.

\n

%B8; Experience with headless AEM delivery via Content Fragments + GraphQL.

\n

%B8; Knowledge of Adobe Launch (Tags) and Target integration.

\n

%B8; Exposure to React/Next.js-based front-end stacks consuming AEM APIs.

\n

%B8; Contributions to open-source AEM or EDS projects.

\n

For this JD, I would separate the skills into Mandatory, Strong Preference, and Good to Have so you can shortlist candidates quickly on Naukri.