Job Description & Details
This is a heavy-hitting architecture and engineering role inside a massive financial institution, requiring you to wrangle multiple AEM digital experiences and establish reusable patterns. If you enjoy solving cross-application complexity and setting technical standards rather than just churning out components, this 12-month contract is right up your alley.
What You'll Actually Be Doing
You'll spend your days acting as the technical bridge between product owners, enterprise architects, and various development pods. Your main goal is to eliminate code duplication across teams by building robust, reusable AEM components, services, and integration patterns. Expect to review a lot of pull requests, troubleshoot thorny Dispatcher caching issues, and ensure that security and performance standards are aggressively met across the entire ecosystem.
The Core Tech Stack
You need absolute fluency in the AEM stack: Java, Sling, OSGi, JCR, HTL, and Content Fragments are your bread and butter here. Beyond that, the role demands a deep understanding of enterprise integration patterns, REST APIs, and Dispatcher caching strategies. Since you're driving quality across multiple teams, strong Git-based CI/CD workflows and automated testing knowledge are non-negotiable.
Interview Expectations
Expect the hiring team to test your deep architectural knowledge with a scenario like, "Walk us through how you would design a cross-application caching and invalidation strategy using the AEM Dispatcher for high-traffic financial pages." They want to see if you understand cache flushes at scale without bringing down the authoring environment. Another likely question will drill into your OSGi bundle design principles, specifically asking how you handle service versioning and dependency management when multiple independent apps rely on your shared services.
Application Advice
To make it past the ATS, your resume needs to explicitly feature keywords like "AEM Architecture," "OSGi," "Sling Models," "Dispatcher Caching," and "Content Fragments." Don't just list technologies; write out bullet points that highlight your experience in cross-team technical leadership, code reviews, and establishing engineering standards that reduced technical debt.