Infrastructure Engineer (GCP/Kubernetes)

Location: Remote, based in the United Kingdom or European/Central European time zones. The role requires overlap with the US Bay Area team and coverage during EU hours and the start of the APAC business day.

Company

hirify.global is expanding its international engineering organization and building a follow-the-sun infrastructure model supporting distributed teams and regional customer deployments.

What you will do

• Serve as the primary infrastructure contact during EU working hours and support cross-regional coverage for APAC and EMEA.
• Build, scale, and optimize infrastructure for EMEA engineering teams and regional customer deployments.
• Manage system health, monitoring, alerting, and incident response for GCP-based workloads.
• Automate deployments, manage Kubernetes clusters, and build internal tooling for safe and efficient software delivery.
• Establish asynchronous workflows and handoff protocols with infrastructure teams to maintain continuous 24/7 coverage.

Requirements

• 5+ years of software engineering experience in a production environment.
• Bachelor’s degree in computer science, engineering, mathematics, or a related field.
• 3+ years of hands-on experience running and scaling workloads in Google Cloud Platform and managing production Kubernetes clusters.
• Proficiency in Python and Go for infrastructure automation, APIs, and operational tooling.
• Experience with Infrastructure as Code using Terraform or Pulumi, CI/CD pipelines, and observability tools such as Prometheus, Grafana, or Datadog.
• Availability in the London/BST/GMT or Central European/CET/CEST time zones, with overlap for US Bay Area collaboration.

Nice to have

• Experience with Google Kubernetes Engine.
• Experience hosting, serving, or orchestrating agentic AI systems and LLM workflows.
• Experience building and scaling modern data pipelines or stream-processing architectures.
• Experience working with early-stage technical companies.

Culture & Benefits

• Remote work within the required European and London time zones.
• Distributed engineering collaboration across the US, Europe, and Australia.
• Async communication and structured handoffs supporting continuous global infrastructure coverage.