Back to Jobs

AEM Cloud Developer

Not Disclosed

Job Description & Details

This is a heavy-duty Adobe Experience Manager Cloud Service contract where you will be deep in the trenches building components, templates, and custom OSGi bundles. You'll need to hit the ground running with AEMaaCS architecture, meaning if you're still relying on legacy on-premise AEM patterns without cloud-native best practices, this gig is going to expose that real quick. It's a solid 6 to 10-month run for someone who actually knows how to bridge Java backend logic with modern front-end integration.

What You'll Actually Be Doing

Your day-to-day will be a mix of spinning up custom HTL/Sightly components, wrestling with Sling servlets, and making sure your OSGi bundles don't tank the system's performance. You will be building out workflows, integrating APIs, and hooking AEM up to various martech tools and CDNs while collaborating closely with UX and DevOps teams. Expect to spend a decent amount of time debugging rendering issues, optimizing Dispatcher caching, and ensuring your code passes the rigorous quality gates required for a cloud deployment.

The Core Tech Stack

To survive here, you need absolute fluency in AEM as a Cloud Service, Java, J2EE, OSGi, and Sling. The team expects you to be completely comfortable writing custom OSGi services, managing content repositories via JCR/CRX, and building out responsive front-ends using HTML5, CSS3, and modern JavaScript. Knowing your way around Maven and Git is a given, but having hands-on experience with external system integrations like Azure AD or Mulesoft, plus Adobe Analytics and Target, will be what actually sets your code apart.

Interview Expectations

The hiring managers are going to probe deeply into your cloud-native migration experience, so be ready to explain how you handle dispatcher caching and CDN configurations when things go sideways in production. They will likely ask you to walk through a scenario where an OSGi bundle fails to activate due to service dependencies, and they'll be listening closely to see if your debugging methodology is systematic or just trial-and-error. They want to see that you truly understand the immutability constraints of AEMaaCS compared to older versions.

Application Advice

Before you hit submit, make sure your resume aligns word-for-word with your LinkedIn profile, because any discrepancies will instantly disqualify you according to their strict screening rules. You'll want to heavily feature exact keywords like AEMaaCS, OSGi, HTL/Sightly, and Dispatcher optimization right at the top of your experience bullets so you easily clear their automated ATS filters.