Job Title

We’re hiring AEM engineers for a multi-year digital transformation at a major enterprise client. AEM as a Cloud Service. Sites, Assets, Forms. Greenfield work alongside migration off legacy systems. Real budget, real users, no babysitting. About Power Commerce Power Commerce builds and operates digital platforms for category-leading brands. Our team has shipped work for Pepsi, Condé Nast, Fenty Beauty, Billie Eilish, and dozens of high-growth DTC and enterprise clients. We pair deep platform expertise with an agentic, AI-native delivery model — engineers who orchestrate, validate, and ship, not just write tickets. This hire sits inside a long-horizon engagement with an enterprise client replacing their incumbent agency of 14+ years. You’ll help define the new build, not maintain someone else’s mess. The Engagement Multi-property AEM as a Cloud Service implementation. Migration off legacy CMS platforms (AEM 6.x, WordPress, Prismic, BigCommerce surfaces). Tight integration with Adobe Target, GA4, Segment, Amplitude, Coveo search, and Azure-based translation tooling. Two seats — one Mid, one Senior. Both are core build roles, not maintenance, not staff aug filler. The Role You’ll architect, build, and ship AEM solutions across Sites, Assets, and Forms. The level you come in at depends on what you’ve actually shipped — we hire on demonstrated depth, not titles. Read both profiles below and apply at whichever level fits. Mid-level — 3–5 years building production AEM. You ship components, write clean Sling models, and don’t need someone holding the diff open for you. Senior — 6+ years and you’ve owned the architecture call. You’ve migrated platforms before. You know when to extend AEM and when to stop fighting it. You can mentor without making people feel small, and push back on a client architect without making them feel cornered. What you’ll do Build and maintain AEM components, templates, content models, and workflows on AEMaaCS Develop reusable Sling models, OSGi services, and HTL (Sightly) components Configure AEM Sites, Assets (DAM), and Forms — including authoring workflows, asset taxonomies, and adaptive forms Own (Senior) or contribute to (Mid) migrations from legacy CMS environments — content modeling, URL strategy, redirect maps, hreflang Implement and maintain dispatcher configs, CDN rules, and caching strategy• Integrate AEM with Adobe Target, Analytics, Customer Journey Analytics, Coveo, and CDP/CRM systems Translate Figma into accessible (WCAG 2.2 AA), performant front-end components Review code, mentor teammates, and represent engineering in client discovery (level-dependent) What you bring 3+ years (Mid) or 6+ years (Senior) hands-on AEM development, with real time on AEM as a Cloud Service Strong Java, Sling, OSGi, JCR, HTL — not just “familiar with,” but shipped with Comfort with Maven, Git, CI/CD pipelines, and Cloud Manager Working knowledge of Adobe Assets / DAM workflows and metadata schemas Front-end fluency: HTML5, CSS, JavaScript; React or similar a plus Senior candidates: at least one full migration to AEM under your belt, ideally from a non-Adobe CMS English fluent enough to write a clear PR description and disagree productively in a meeting Nice to have AEM Forms at scale — adaptive forms, Forms Data Model, document services Edge Delivery Services / Franklin experience Adobe Certified Professional, Expert, or Master credential Background with enterprise clients in regulated or accessibility-sensitive industries How We Work Remote-first, async-default. We measure output, not hours. Agentic delivery model — engineers orchestrate AI agents instead of grinding boilerplate. You’ll learn this on the job if it’s new to you. Small, senior teams. No layers between you and the call that matters. Direct feedback culture. We say what we mean and we mean what we say. Real ownership of architecture and shipping decisions inside your scope. Compensation Competitive against top agency benchmarks for your market and level. Final offer reflects depth and demonstrated impact, not a fixed band rubber-stamped from a spreadsheet. We discuss numbers in the first conversation, not the fifth. How to Apply Easy Apply works. In your application note, include 2–3 live URLs of AEM sites you've personally built or significantly contributed to, with a one-line note on your role.