ironquill.tech/board

$ cat jobs/cloud-engineer-gcp-pilef-0c5984f8fead.json

Cloud Engineer (GCP)

Pilef·Worldwide·Remote·mid
pythonkubernetesterraformawsgcpazuredevopsci/cdgithub actions
Apply on linkedin → Get AI match score →
Listed as a remote role based in Spain. About us We're a small GCP consultancy working with clients across the world (focus on US and EMEA) on cloud architecture, migrations, Kubernetes, CI/CD and platform work. We're not a big consultancy and we don't work like one. Two things define how we operate: We're AI-native. We use AI tooling heavily and seriously. It's how a small team delivers what normally takes a much larger one. We build our own tools. Rather than solving the same problem repeatedly for different clients, we capture what we learn into internal tooling and reusable patterns. Everyone contributes to that, and everyone benefits from it. The role The title says Cloud Engineer, but the reality is broader. One week you might be designing a high level architecture, the next writing a small service, the next doing hands on DevOps work. We're looking for someone who moves comfortably across all of it and doesn't mind switching hats. You'll help build our internal tooling and knowledge base as much as you deliver with it. You use what you build, and what you build makes the next project faster. You'll get varied problems, real technical decisions, and room to grow fast. What matters most to us Read this part carefully, because it's where we differ from a normal cloud job. The things below are hard to teach, so we care about them more than your years on a CV. You work AI-native This is central to how we operate, and it's the hardest thing to pick up from scratch. We're looking for someone who already thinks and works this way. • You use AI coding tools daily (Claude Code, Codex, Cursor or similar) and know how to get good output from them, not just autocomplete. • You're familiar with the concepts around them: skills, MCP, agents, context engineering, prompt structure. You don't need to be an expert, but the vocabulary shouldn't be new to you. • You have a feel for where these tools are strong and where they quietly fail, and you verify rather than trust blindly. • You reach for automation and tooling instinctively instead of doing the same thing by hand twice. You're good with people, and honest Our business runs on trust, and trust is built in conversations. This matters as much as the technical side. • You're comfortable speaking up. You can hold a position, explain your reasoning, and defend a technical point without needing to be the loudest person in the room. • You can talk to anyone: engineers, managers, stakeholders who aren't technical. • You say "I don't know, let me find out" instead of improvising an answer. Confidently wrong is far more expensive than honestly uncertain, and clients can tell the difference immediately. You're autonomous • Comfortable in a small team. No layers, no handholding, ambiguity is normal. • Autonomous on execution, supported on direction. We'll make sure you know what we're aiming for and why, and we're there when you're stuck on something real. But we're not going to babysit the work. Take something ambiguous, work out what needs doing, use common sense, and come back with progress or good questions. If you need a detailed ticket to start, this isn't the right fit. English • Essential and close to native. All our clients are English speaking, so you need to be comfortable running a meeting, pushing back, and explaining a design in English. Spanish is a nice to have. The technical foundation We can teach GCP depth to the right person, so we care less about ticking every box here and more about a solid base we can build on fast. • Around 3 years working with cloud, with real hands on GCP. You've built and run things in production, not just studied them. • Strong development skills. This is an area where we want more depth on the team, so it counts for a lot. Python or Go for tooling and automation is a real plus. • Database experience is genuinely appreciated for the same reason. • Terraform or IaC experience, or a clear appetite to learn it properly. • Solid grounding in GCP networking and IAM is valuable, since it's where the hard problems live. Nice to have • Kubernetes / GKE • CI/CD (GitHub Actions, ArgoCD or similar) • GCP certifications • Exposure to other clouds (AWS, Azure) • Anything you've published: blog, OSS, talks What we offer • Real GCP work on live projects, with a path to client facing work as you grow into it • Room to grow into architecture, and we'll invest in that deliberately • A team that works AI-native rather than resisting it • Autonomy, no bureaucracy, and direct influence on how we build the company • Fully remote with flexible hours Show more Show less Seniority level Entry level Employment type Full-time Job function Engineering and Information Technology Industries IT Services and IT Consulting

Similar remote roles

Senior Backend Engineer (TypeScript / Python / Kubernetes)
Greenstep · Worldwide · senior
Senior DevOps Engineer / SRE (remote)
Nejo · Worldwide · senior
DevOps Engineer - Remote, Latin America
bluelight consulting · Worldwide · mid
Senior DevOps Engineer
Lemon.io · LATAM · senior
Senior DevOps Engineer
Lemon.io · Worldwide · senior
DevOps Engineer
Reactive Technologies Limited · Worldwide · mid
Senior Data Engineer Consultant
Sia · Worldwide · senior
Senior Data Engineer Consultant
Sia · Worldwide · senior