Job Description:

• The role combines solution architecture, EDS design, engineering standards, integrations, performance, accessibility, CI/CD, technical mentoring and delivery leadership.
• The Solution Architect partners with architects, product owners, UX, developers, QA, DevOps and business stakeholders to make practical, scalable technical decisions and ensure successful implementation of enterprise EDS solutions.

Required Technical Skills:

• Strong hands-on AEM Edge Delivery Services (EDS) knowledge and enterprise implementation experience.
• Expert HTML5, CSS3 and modern JavaScript/web architecture skills.
• Strong understanding of EDS blocks, block modeling, composition, authoring and content architecture.
• Strong understanding of Universal Editor and Document-Based Authoring.
• Experience with Git/GitHub, CI/CD and engineering governance.
• Strong understanding of REST/JSON integration architecture and security considerations.
• Strong understanding of performance/Core Web Vitals (CWV), SEO, accessibility/WCAG and scalable front-end architecture.
• Experience with automated testing, browser testing, monitoring and production troubleshooting.

Core Responsibilities:

• Own the solution architecture and 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 the 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 and 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.
• Prevent unnecessary block proliferation through reuse standards, governance and design-system alignment.
• Review architectural trade-offs and maintain technical decision records where appropriate.
• Define performance budgets and Core Web Vitals objectives and review implementation against them.
• Establish technical SEO and accessibility requirements as part of the Definition of Done.
• Define CI/CD quality gates covering linting, tests, accessibility, browser validation and release readiness.
• Establish Git/GitHub branching, pull-request and code-review standards.
• Ensure unit, integration, end-to-end, accessibility, performance and regression testing are appropriately applied.
• Lead complex production investigations and drive root-cause remediation.
• Stakeholder & Team Leadership
• Lead architecture and technical discussions with architects, product owners, UX, business and engineering stakeholders.
• Mentor Senior Developers and establish consistent engineering practices across teams.
• Provide technical estimates, identify dependencies and communicate delivery risks.
• Explain technical trade-offs in business-friendly language and challenge unnecessary complexity.
• Evaluate relevant Adobe/EDS capabilities and recommend adoption where they provide measurable value.
• People management is not mandatory; the primary leadership responsibility is technical and architectural ownership.