Role Overview
The Senior DevOps Engineer is responsible for designing, implementing, and continuously improving Inventeer’s cloud infrastructure and deployment platforms on Google Cloud.
This is a senior individual contributor role, partnering closely with Engineering leadership and platform/security stakeholders to deliver complex infrastructure initiatives, enforce security-by-default standards, and enable product teams with reliable, scalable, and opinionated platform capabilities.
The role is delivery-focused: success is measured by systems shipped, automation created, and platform leverage gained—not by constant reactive operations.
Key Responsibilities
Infrastructure & Cloud Platform
- Advanced networking & architecture: Design and maintain resilient Google Cloud architectures, including Shared VPC (XPN) for multi-project network topologies, isolation boundaries, and security controls.
- Design, implement, and maintain Google Cloud architectures aligned with security, scalability, and cost-efficiency principles.
- Operate and evolve GKE clusters, including networking configuration, autoscaling, and security hardening.
- Kubernetes & service mesh: Implement and operate Istio for traffic management, mTLS, policy enforcement, and service discovery across microservices.
- Own infrastructure lifecycle management through Infrastructure as Code (Terraform), ensuring consistency, auditability, repeatability, and environment parity.
Platform Enablement & Developer Experience
- Provide a standardized “paved road” for Inventeer teams to deploy services safely and efficiently.
- Build and maintain reusable Terraform modules, baseline patterns, and golden paths that enforce governance and security by default.
- Intelligent autoscaling: Implement KEDA for event-driven autoscaling beyond CPU/RAM metrics, enabling real-time reaction to application demand.
- Partner with Product/Software Engineering teams to support infrastructure needs without creating operational bottlenecks—enablement over gatekeeping.
Release Engineering & GitOps
- Design, implement, and maintain CI/CD pipelines using GitHub Actions.
- Own GitOps workflows using ArgoCD, ensuring predictable, traceable, and synchronized deployments.
- Improve deployment reliability, rollback strategies, and release confidence across environments.
- Advanced deployment strategies: Implement Argo Rollouts (e.g., canary and blue-green) to improve reliability and reduce deployment risk.
Security & Reliability
- Apply DevSecOps practices across infrastructure and CI/CD pipelines.
- Collaborate with security/compliance stakeholders to implement WAF, DDoS protection, secrets management, and vulnerability mitigation.
- Support audit-readiness initiatives (e.g., SOC 2) by ensuring infrastructure controls are enforceable, testable, and auditable.
Required Technical Skills
- Strong hands-on experience with Google Cloud Platform, including:
- VPC networking, peering, routing, and Shared VPC (XPN)
- IAM and least-privilege design
- GKE and managed GCP services (e.g., Cloud SQL)
- Kubernetes & mesh: Advanced experience with GKE, Helm, and Istio (VirtualServices, Gateways, Sidecars, mTLS).
- Advanced experience with Terraform, including module design and state management.
- Practical experience with GitOps tooling, including ArgoCD.
- Fluency with GitHub Actions and progressive delivery tooling: Argo Rollouts (including Analysis Templates).
- Observability: Experience operating an observability stack including Prometheus Operator, Thanos, and Loki.
- Experience implementing KEDA for event-driven autoscaling.
- Solid understanding of networking fundamentals (DNS, VPNs, load balancers, HTTP/gRPC).
Nice to Have
- Experience operating in regulated or audited environments (SOC 2, GDPR, PCI-DSS).
- Experience with cost management / FinOps strategies within GCP.
- Knowledge of load testing and stress testing methodologies.
Behavioral Expectations
- Hands-on execution: Comfortable designing architecture and implementing it directly in code.
- Technical communication: Explains infrastructure and security decisions clearly to non-infrastructure engineers.
- Operational discipline: Values documentation, standards, and repeatable processes as part of engineering quality.
- Leverage mindset: Builds systems that reduce future work and increase team velocity (automation-first, opinionated defaults).