About the job

• Cloud Architect - AWS
• Location: Geelong
• Hybrid, 3 days per week in office
• 6 months Contract with view to extend
• VIC Government organisation
• Attractive daily rate

About the Role

Client is strengthening its enterprise cloud foundations as part of a broader hybrid and multi-cloud strategy. The Principal AWS Landing Zone Architect will own the target architecture and provide hands-on technical leadership through implementation, assurance and transition into operations.

The role requires someone who has previously built enterprise AWS landing zones at scale and can translate security, compliance, networking, identity, delivery and operational requirements into a practical platform that product teams can consume safely.

What success looks like in the role

• A clear, approved target architecture covering account structure, organisational units, identity, connectivity, security, logging, observability, resilience, cost governance and service operations.
• A governed multi-account foundation using AWS Organizations and AWS Control Tower, with repeatable account vending and workload onboarding.
• Automated platform deployment and configuration using infrastructure as code, version control, peer review and CI/CD controls.
• Security controls that are embedded by default, with central visibility, evidence collection and integration into enterprise security operations.
• A pragmatic operating model with clear ownership, support boundaries, lifecycle management, exception handling and measurable service outcomes.
• Reusable patterns and documentation that enable delivery teams to adopt AWS without recreating foundational controls for every workload.

Key accountabilities

Architecture ownership

• Lead discovery across architecture, cyber security, identity, network, platform, operations, risk, procurement and delivery stakeholders.
• Define the end-state AWS landing zone architecture, architecture principles, decision records, standards and implementation roadmap.
• Design the multi-account and organisational unit model, management account boundaries, delegated administration model, service control policies and control inheritance.
• Make and document practical trade-offs between AWS-native capabilities, enterprise tooling and third-party controls.
• Ensure the platform can evolve without redesign as workload demand, regulatory obligations and operating arrangements change.