KEY RESPONSIBILITIES
*Platform assessment and architecture review. Evaluate the current AEM as a Cloud Service implementation. Distinguish standard platform practice from over-customization or unnecessary complexity. Assess long-term maintainability and recommend simplification, stabilization, or remediation where warranted.
* Support model and transition planning. Define what support work can reasonably be performed internally, by contractors, or by a vendor. Develop a credible transition approach. Identify the skills and roles required for the future-state team.
* Documentation and knowledge transfer. Identify gaps in existing platform documentation. Establish documentation standards. Guide knowledge transfer between the current vendor and future support resources so that critical knowledge lives in the organization rather than in individuals.
* Cross-functional collaboration. Work with stakeholders across product, UX, and engineering teams.
* Architecture support. Evaluate and define component, template and experience architecture. Translate business requirements into technical architecture, workflows and content models.
* Governance and supportability. Recommend guardrails to ensure future enhancements align with sound AEM practice. Advise leadership on architectural tradeoffs, technical debt, and the long-term implications of platform decisions.
* Stakeholder communication. Serve as a trusted technical advisor to CODE PA leadership. Translate architectural complexity into clear, actionable guidance for executive, procurement, and operational audiences.
* Risk and decision support. Surface platform risks and operational dependencies with clear analysis and decision points. Help leadership weigh the cost of maintaining the current model against alternatives.
* Vendor and contractor oversight. Evaluate current vendor responsibilities and provide technical input into future contractor or vendor scopes, labor categories, and accountability expectations.