Apply strong engineering expertise to shape architectural patterns, guardrails and technical direction.
Provide pragmatic architectural guidance aligned to real‑world delivery and operational needs.
2. Policies & Standards:
Author and maintain engineering policies, standards and technical guidance.
Ensure standards are outcome‑focused, implementable and aligned to organisational and regulatory requirements.
Support architectural assurance and governance activities.
3. Adoption & Enablement
Drive understanding and adoption of engineering policies and standards across delivery teams.
Work with engineering, platform, security and delivery teams to embed standards into tools, pipelines and ways of working.
Identify and remove barriers to adoption.
4. Communication & Engagement
Translate complex technical concepts into clear, accessible guidance for varied audiences.
Support communications, briefings and enablement materials to promote consistent implementation.
Build strong relationships across architecture, engineering and delivery communities.
5. Continuous Improvement
Monitor evolving engineering practices and technologies.
Review and improve existing standards based on delivery feedback and outcomes.
Contribute to raising engineering maturity across the organisation.
Key Deliverables:
Engineering policies, standards and technical guidance
Reference architectures, patterns and guardrails
Adoption and communication materials
Architectural assessments and recommendations
SKILLS AND EXPERIENCE:
Essential:
-Strong engineering background with experience in building and operating production systems.
-Proven ability to write clear, actionable technical policies and standards.
-Experience influencing cross‑team engineering practices.
-Excellent written and verbal communication skills.
Desirable:
-Experience in complex or regulated delivery environments.
-Familiarity with Agile, DevOps and CI/CD practices.
-Understanding of security, resilience and operational design.
-Experience supporting architectural governance forums.
Ways of Working:
-Enables teams rather than constraining them.
-Balances architectural rigour with delivery pragmatism.
-Focuses on adoption and outcomes, not documentation alone.
