I'm Corentin, a DevOps & Cloud engineer based in Barcelona. I help teams stop running cloud “by hand”: reproducible infrastructure with Terraform and clearer cloud spend (FinOps) on GCP and AWS. Side consulting available outside my full-time role (~10–15 h/week, async-first).
Cloud engineer (~3 years). Technical referent on multi-cloud infra, Terraform standardization, CI/CD and cost-aware operations. Strong at handoffs and mentoring (teaching background). FR / EN / ES.
I don’t take energy-flexibility / demand-response style projects (employer conflict).
Catalan: Intermediate - B2Side consulting · deliverables & milestones · ~10–15 h/week · async-first
1–2 weeks · cloud + Terraform readiness review, basic risks and FinOps findings, plus a 30/60/90 roadmap.
Entry: from ~1.200–1.500 €
2–4 weeks · modular Terraform, environments, CI basics and a documented handoff your team can own.
Entry: from ~2.500–3.500 €
10–15 h/month · async reviews, small FinOps/IaC improvements, one short sync per week max. Not 24/7 on-call.
Entry: from ~900–1.100 €/month
Need a different shape? Fixed-scope project, short B2B contract, or a hybrid next to Terraform / FinOps / platform IaC (GCP or AWS). We define deliverables, hours and price together.
Not full-time staffing · no energy-flexibility work
Context: teams can see cloud spend in native consoles, but still lack an execution layer for waste, ownership, and next actions.
Problem: cost reviews stay reactive; opportunities are not ranked, owned, or easy to demo without live billing credentials.
Actions: built a Google Cloud–first accelerator: CSV → metrics/snapshot, public Pages product story, local Grafana evidence pack, adapters and runbooks for later multi-cloud.
Outcome: portfolio-ready FinOps narrative visitors can click through; same path usable as a client starting template.
Stack: GCP · Python · Prometheus · Grafana · GitHub Pages
Context: AWS Kubernetes baselines are often rebuilt from scratch per engagement, with uneven security and ops defaults.
Problem: time-to-first-cluster is slow; private networking, IRSA, Karpenter, and platform add-ons rarely land as one coherent accelerator.
Actions: shipped a template-first Terraform landing zone: remote state, private VPC, EKS + OIDC, Karpenter, ALB / External Secrets, CI validate, milestone-tracked roadmap.
Outcome: reusable AWS EKS starting point — configuration-driven onboarding, validated IaC without requiring a live (paid) cluster for proof.
Stack: AWS · EKS · Terraform · Karpenter · Helm · GitHub Actions
Context: B2B SaaS product infra growing faster than the IaC layout.
Problem: duplicated Terraform, weak conventions, hard to scale environments safely.
Actions: refactored toward reusable modules; defined shared infra/code conventions; improved environment layout and handoffs for eng teams.
Outcome: clearer ownership, faster reuse of modules, platform easier to extend without copy-paste drift.
Stack: GCP · Terraform · CI/CD
Context: high-traffic digital platform on AWS + GCP + Kubernetes.
Problem: infra questions and incidents bounced across teams; scaling was partly manual.
Actions: acted as technical point of contact; automated provisioning/scaling with Terraform & CloudFormation; coached teams on day-to-day platform practice.
Outcome: less operational toil, more repeatable scaling, single clear escalation path for infra.
Stack: AWS · GCP · Kubernetes · Terraform · CloudFormation
Context: engineering org needing faster, safer cloud changes.
Problem: pipelines and provisioning slowed delivery; uneven automation quality.
Actions: hardened Jenkins pipelines; automated AWS resources with Terraform/CloudFormation; documented repeatable flows for the team.
Outcome: more predictable deploys and provisioning; foundation for later multi-cloud platform work.
Stack: AWS · Jenkins · Terraform · CloudFormation · Linux
Want something similar for your team? See Services or contact me.
Focused on cloud / DevOps roles that back the consulting offer.
May 2025 - Present
Cloud DevOps on GCP with Terraform — platform reliability, automation and cost-aware infrastructure. Standardize infra conventions, improve CI/CD and environments, act as technical referent for engineering teams.
April 2023 - April 2025
Multi-cloud DevOps referent (AWS/GCP/Kubernetes), including internship transition into the role. Automated provisioning and scaling with Terraform and CloudFormation; improved CI/CD (Jenkins) and day-to-day platform reliability for engineering teams.
2018 - 2023
5-year IT Expert program (software engineering). Later years included web/app and DevOps foundations; pedagogic assistant experience.
2021 - 2022
One-year exchange. Coursework included software/AI electives; career path continued in software / DevOps.
Let's look at your project — a short 15-minute call, or by email.