AEM Architect

Our requirements

• 10+ Years Total Experience: With a minimum of 5 years in an AEM Architect or Lead Developer role.
• Java Expertise: You must be an expert in Java (J2EE) within the OSGi context. You understand thread safety inside and out (handling Singletons correctly) and can identify memory leaks in heap dumps.
• AEM Mastery: Deep, hands-on expertise in AEM (specifically AEM as a Cloud Service), OSGi, Sling, JCR/Oak, and Dispatcher.
• Integration Architecture: Proven ability to design robust, fault-tolerant integrations between AEM and third-party systems using modern APIs (REST/JSON).
• CI/CD & DevOps: Experience setting up and managing pipelines in Cloud Manager or Jenkins. You understand the full lifecycle from commit to production.
• Technical Stack: AEM as a Cloud Service, Expert Java, OSGi (R7+), Apache Sling, JCR/Oak, Dispatcher & CDN Caching (Fastly/Cloudfront), REST/SOAP Integrations, Maven, Git Flow, CI/CD.

Optional

• Adobe Certified Master - Architect certification.
• Experience designing Headless CMS architectures using GraphQL/Content Fragments.
• Experience migrating legacy on-premise AEM instances to AEM as a Cloud Service.

Your responsibilities

• Low-Level Design & Ticket Breakdown: Translate business requirements into detailed Low-Level Design Documents (LLDs). You are responsible for:
• Defining the exact JSON structure and API contracts that Frontend will consume.
• Breaking large features into small, technical Jira tickets with clear acceptance criteria.
• Collaborating with BAs to ensure technical reality matches business intent.
• Strategic Development: While you won't be coding every day, you are expected to stay "hands-on." You build the Proof of Concepts (POCs), the complex OSGi services, and the core frameworks that the rest of the team builds upon.
• Architectural Blueprinting: Design the overall system architecture, including content models, workflows, and integrations (CRM, Commerce, DAM).
• Technical Governance: Define and enforce AEM development standards. You run the code reviews and security audits. If code is sloppy or inefficient, you reject it with constructive feedback.
• Performance Engineering: Lead application optimization. Instead of tweaking server settings, you focus on efficient caching strategies (Dispatcher/CDN), optimizing expensive queries, and ensuring Java code is free of memory leaks.

This is how we organize our work

This is how we work on a project

• Clean Code
• code review
• active monitoring
• issue tracking tools
• performance tests
• regression tests
• test automation
• unit tests

Job Overview:

What Success Looks Like in This Role:

• The "Blueprinter": You don't just say "build a component." You provide the team with a blueprint including the specific Sling Model logic, the JSON output structure, and the dialog requirements—before they write a single line of code.
• Anticipating the Cliff: You look for hidden traps. You actively explore the codebase to identify risks (like API bottlenecks or legacy debt) and flag them before they impact the timeline.
• Ownership of "Done": To you, a task is not done when the code is written. It is done when it is verified in Staging, performance-tested, and doesn't break existing functionality. You act as the gatekeeper of quality.
• The "Force Multiplier": You make the team better. You actively mentor senior and mid-level devs through code reviews and pair programming. You don't just fix their code; you teach them why it needed fixing.
• The Final Line of Defense: You are the escalation point for the "impossible" bugs. When a complex issue arises, you have the analytical skills to trace it across the entire stack (AEM, Dispatcher, CDN, APIs).