Cloud Platform Engineer

What this role is about

This is a Platform Engineering role, not "keep the lights on" Cloud Operations. You build,run and improve the infrastructure your product team owns on Google Cloud, using thecentrally managed Terraform modules and pipelines provided by the platform teams, andyou help improve them.

Good work here means secure defaults, reusable code and clear guardrails, not ticketresolution. The client is also building a Cloud Platform cluster in Bucharest, so you will bepart of a growing local team.

Key responsibilities

• Infrastructure on GCP: build, operate and further develop the product team'sinfrastructure on Google Cloud (GKE, Cloud Run, IAM, VPC, Load Balancing, DNS,Secret Manager).
• Infrastructure as Code: implement and maintain infrastructure with Terraform, usingcentrally managed modules and pipelines; contribute improvements back to theshared modules.
• CI/CD: build and operate application pipelines in GitLab CI/CD, including GitLabcomponents and runners across environments.
• Core platform components: integrate and use logging, secrets, IAM, VPC and DNS.
• Secure defaults: apply secure defaults for IAM, secrets, networking, TLS and policies.
• Operations: support day-to-day operations, including incident response,infrastructure maintenance and performance analysis.
• Collaboration: work with the other platform teams to use and improve sharedTerraform modules and policies; document standards and present designs inengineering reviews.
• Kubernetes: manage Kubernetes resources (deployments, RBAC, networking, policies,upgrades) and Helm releases, with GitOps delivery via Flux and Flagger.

Must-have requirements

GCP is the main cloud. Equivalent hands-on AWS experience is accepted wherever noted below.

• 4+ years in DevOps, Platform or Cloud Engineering, with hands-on productionownership, not only consuming infrastructure built by others.
• Landing zones: has set up, reworked or extended a GCP or AWS landing zone.
• Kubernetes: has configured, managed and improved GKE or EKS setups in production,including Kubernetes resources (deployments, RBAC, networking, policies, upgrades)and Helm releases. Experience with GitOps (Flux) and progressive delivery (Flagger).
• Serverless: knows Cloud Run and Cloud Functions (or AWS equivalents), includingtheir trade-offs.
• Secrets management: has integrated Google Cloud Secret Manager or AWS SecretsManager in a mid-to-large company setup.
• Cloud networking: has set up or reworked a cloud network on GCP and/or AWS (VPCdesign, routing, firewalls, private connectivity).
• Artifact management: has implemented Google Artifact Registry or AWS CodeArtifactin a mid-to-large company setup.
• GitLab: knows a cross-environment GitLab runner setup and has migrated use casesto GitLab CI/CD components or GitHub Actions.
• Terraform: productive use of Terraform with modular repositories, multipleenvironments, and plan/apply in CI/CD.
• Observability: monitoring and alerting with Datadog or GCP Monitoring.
• Fluent English, spoken and written.

Nice to have

• GCP landing zone tooling: Cloud Foundation Fabric (FAST), Enterprise FoundationBlueprint, or the terraform-google-modules project factory.
• Shared VPC, Private Service Connect, hybrid connectivity (HA VPN / Interconnect).
• Organization Policies, VPC Service Controls, Cloud KMS / CMEK, Security CommandCenter.
• Keyless CI/CD authentication via Workload Identity Federation.
• Cloud Armor in production.
• Datadog configured as code, Managed Prometheus / PromQL, SLO-based alerting.
• Dependency automation at scale (Renovate).
• Go or Python for internal platform tooling.
• GCP Professional certification (Cloud Architect, DevOps Engineer or NetworkEngineer).
• Experience in an enterprise platform team serving many product teams, or in retail / e-commerce.
• German language.

Don't tick every box? If you are strong on the must-haves, apply anyway. The nice-to-haves are things you can grow into, not gates.

Ways of working

• Strong team player, familiar with Scrum and agile ways of working.
• Strong communication skills to bridge a hybrid team split between Bucharest andGermany.
• Comfortable explaining designs and trade-offs to platform and product engineers.

What we offer

• Work on a large-scale, GCP-first enterprise platform with a mature platformengineering practice.
• An international team and a growing Cloud Platform cluster in Bucharest.
• Hybrid setup with a Bucharest office.
• Competitive package, depending on experience and contract type (B2B oremployment).
• Support from CloudHero, an AWS and cloud-native consultancy, and its community ofDevOps and platform engineers.

Who is likely to be a strong match

Engineers who can clearly explain platform components they personally designed, builtand operated: a landing zone, a network or IAM design, a reusable Terraform module, aCI/CD standard. They can discuss concrete cloud services, production incidents and thetrade-offs behind their decisions.

Who is probably not a fit

• Profiles that have only consumed infrastructure built by a dedicated DevOps orplatform team, without building or improving any of it.
• Mainly support, monitoring or ticket-based operations roles without design ownership.
• Candidates without hands-on production cloud experience.