he second resource should be a senior engineer with deep practical experience in:
Terraform and reusable module development
GitHub and GitHub Actions
CI/CD for Azure infrastructure deployments
Reusable GitHub Actions workflows
Terraform testing and validation
GitHub repository and branching strategy
GitHub release strategy
Versioning and lifecycle management of GitHub Actions and reusable workflows
Automated Azure infrastructure deployments
Secure GitHub-to-Azure authentication and authorization
Appropriate handling of secrets, identities, and credentials
Designing controlled deployment patterns that allow developers to consume approved infrastructure automation without allowing them to introduce or execute their own Terraform modules or configuration outside the established framework
A major part of what we want to design is a model where developers have appropriate flexibility within sandbox settings, but infrastructure outside of sandbox is deployed through controlled GitHub Actions using standardized Terraform code and approved modules. We want this resource to help us design the GitHub security, release, versioning, and deployment model necessary to enforce that approach.
Engagement expectations
Both resources should be senior, hands-on engineers, not resources who primarily provide architectural guidance without doing the implementation. We expect them to participate directly in the design and development of the platform.
Our team will help define and prioritize sprint items, and we intend to have daily standups with the resources to maintain alignment and quickly address blockers and design decisions.
Just as importantly, we want knowledge transfer to be continuous throughout the engagement. We want our engineers working with these resources, participating in design decisions and code reviews, and understanding the rationale behind the Terraform, Azure, and GitHub patterns being established.
At the end of the engagement, the objective is to have a standardized Azure Landing Zone framework, reusable Terraform, a secure and repeatable GitHub Actions deployment model, and an internal team that fully understands and can own, support, and extend what has been built.Role & responsibilities