Experience: 7-12+ years overall; 4+ years of strong AEM/EDS or comparable modern enterprise web architecture experience preferred.
Required Technical Skills-Strong hands-on AEM Edge Delivery Services knowledge and enterprise implementation experience.
Expert HTML5, CSS3 and modern JavaScript/web architecture skills.
EDS blocks, block modeling, composition, authoring and content architecture.
Universal Editor and Document-Based Authoring understanding.
Git/GitHub, CI/CD and engineering governance.
REST/JSON integration architecture and security considerations.
Performance/CWV, SEO, accessibility/WCAG and scalable front-end architecture.
Automated testing, browser testing, monitoring and production troubleshooting.
We are seeking an AEM Edge Delivery Services Technical Lead to provide technical ownership for enterprise digital implementations.
The role combines solution architecture, EDS design, engineering standards, integrations, performance, accessibility, CI/CD, technical
mentoring and delivery leadership. The Technical Lead partners with architects, product owners, UX, developers, QA, DevOps and
business stakeholders to make practical, scalable technical decisions.
Core Responsibilities
Own the technical implementation approach for enterprise EDS projects and workstreams.
Lead technical discovery, solution design and EDS architecture decisions.
Define reusable block, content-model and implementation patterns.
Establish coding, review, testing, accessibility, performance and security standards.
Determine appropriate authoring approach, including Universal Editor and/or Document-Based Authoring.
Lead integration architecture for APIs, Adobe services and third-party systems.
Guide developers through complex technical issues and conduct design/code reviews.
Identify technical risks, dependencies and mitigation strategies; support estimation and release planning.
Architecture & Technical Leadership
Define EDS architecture, project structure, reusable block strategy and content-modeling principles.
Translate business and experience requirements into scalable technical designs and non-functional requirements.
Decide what belongs in authored content, block implementation, APIs, Adobe services or edge functionality.
Establish integration, caching, performance, security and accessibility patterns.
