We need Google Cloud Platform engineers with strong Terraform experience to migrate approximately 230 containerized .NET APIs from on-prem Cloud Foundry to Cloud Run, using Schwab-approved Terraform modules. The immediate Q4 focus is standing up the cloud infrastructure and migrating pilot applications, with some .NET application changes and deployment work as needed. – Don’t Submit traditional production-support/SRE engineers
Ideal Resource Profile
The strongest candidate would have Google Cloud Platform + Terraform + application modernization/deployment experience, ideally with .NET.
I would position the requirement as roughly 60–70% Google Cloud Platform/Terraform/cloud engineering + 20–30% application/.NET modernization + deployment, rather than an SRE/operations position.
The primary need is for Google Cloud Platform cloud/application engineers with strong Terraform skills, rather than traditional production-support/SRE engineers.
Current state: containerized APIs running on an on-prem Cloud Foundry PaaS.
Target platform: Primarily Google Cloud Run, rather than GKE.
Cloud Run configuration: Services will maintain minimum always-on instances rather than scaling completely to zero.
Infrastructure as Code: Engineers must use Schwab-provided Terraform modules created by the Cloud Architecture/Cloud Services teams. This is not free-form Terraform development; engineers will compose approved modules to implement the required architecture.
Application work: Some APIs may require .NET changes/refactoring to make them suitable for the Google Cloud Platform/Cloud Run environment.
Deployment: Engineers will help configure infrastructure and deploy/migrate applications into Google Cloud Platform.
Longer-term direction: Cloud Run is the initial target because its managed/PaaS operating model is closer to Cloud Foundry. GKE Autopilot may be considered later once approved at Schwab.
Approved compute options today: GCE, GKE and Cloud Run.
Never miss an opportunity! Create an alert based on the job you applied for.
