~/camilo $ whoami
JoseCamiloJogaGuerrero.
I'm a DevOps & Cloud Engineer who builds and runs Kubernetes platforms on AWS and Azure. My work centers on Infrastructure as Code, GitOps delivery, and observability — turning sprawling, manually-managed environments into automated, self-service platforms teams can run themselves.
Building systems that scale.
Hello! I'm José Camilo (please call me Camilo), a Computer Science Engineer drawn to DevOps and cloud since the start of my career. I build efficient, scalable, automated infrastructure — and I care about the platform being something teams can actually run themselves.
I've taken environments from manually-managed servers and console-clicked clusters to managed Kubernetes platforms on AWS and Azure, with GitOps delivery, Infrastructure as Code, and observability built in. The part I enjoy most is the consolidation work — collapsing sprawl into something simple and self-service.
Where I've worked.
DevOps Engineer
INSPYR Global Solutions
- Operate a multi-region Azure platform of 300+ services on AKS, with releases driven by Azure DevOps pipelines and PowerShell
- Led consolidation of every alert and dashboard into a single alerts-as-code repository and GitOps release pipeline spanning all environments and regions
- Maintain and extend the Bicep infrastructure platform, shipping new services through what-if and release pipelines
- Enabled managed data infrastructure for developer teams — Azure Synapse and Databricks with Unity Catalog governance, deployed entirely as code
- Drive an in-flight migration of AKS clusters onto Cilium and replace manual incident remediation with self-healing automation
- Led a self-service web app giving developers audited, PII-masked access to Azure SQL and MongoDB across environments — gated by a one-click admin approval queue — plus self-service Kubernetes operations (workload restarts, resource and replica changes) for load-testing teams
Co-founder & CTO
KODEPULL SRL
- Co-founded the company in 2025 — it delivers enterprise-grade engineering to businesses without enterprise budgets
- Own the entire technical side as CTO: architecture, infrastructure design, platform and vendor decisions, and the quality bar every project ships under
- Lead hands-on engineering and technical delivery across web, custom software, cloud, and mobile work
- Scale specialist engineers, designers, and partners onto each engagement based on what the work actually needs
- Partner with the CEO on technical strategy, keeping delivery mapped to real business outcomes
DevOps Engineer
FL Betances & Asociados
- Embedded in a banking institution's core DevOps team, supporting 50+ engineering teams and a continuous automation backlog
- Maintained and extended an in-house deployment framework on Azure DevOps — YAML templates that detect project type, target environment, and required policy checks
- Ran nightly deployment operations across all teams, tracing failed deploys through ArgoCD and AKS to the policy or template at fault
- Built Power Automate flows for the approval, notification, and ticket-lifecycle processes around DevOps work
- Led an internal Terraform module library that let teams self-provision cloud resources within bank policy; handed off near-complete at contract end
DevOps Consultant
Arctiq
- Designed and led the migration of 60+ applications from a hand-built Rancher setup to a managed AWS EKS platform — FluxCD, GitLab CI, and Terraform
- Consolidated branch-per-team sprawl into per-team namespaces, cutting 5–8× of redundant deployed surface
- Rolled out SSO-based access with AWS Identity Center and Entra ID, retiring IAM users in favor of assumed roles and OIDC for pipelines
- Built observability from zero — OpenTelemetry instrumentation with Grafana, Loki, and distributed traces across every application
- Led Terraform workshops moving dev teams to self-service infrastructure; promoted to local team mentor
- Embedded SOC2 compliance into delivery — automated CI/CD checks, IaC policy, and merge-request gating on GitLab across lower and production environments
- Standardized resource governance with Kubernetes LimitRanges across every environment, and documented the EKS architecture as code with D2 diagrams
- Led a week-long Azure enablement workshop for a client team — from cloud fundamentals and governance through networking, compute, data and AI, and operations
Things I've built.
EKS Platform Migration
Designed and led the migration of 60+ applications from a hand-built Rancher setup to a managed AWS EKS platform, with FluxCD for GitOps delivery and Terraform for the cloud underneath.
Multi-Cloud Infrastructure as Code
Modular Terraform and Bicep platforms for AWS and Azure — networking, compute, storage, and security — with a plan or what-if check running on every change.
Observability from Zero
Built observability for a platform that started with none — OpenTelemetry instrumentation feeding Grafana, Loki, and distributed traces, with dashboards and alerts on every application.
Alerts-as-Code Pipeline
Consolidated every alert and dashboard into a single repository and a GitOps release pipeline that deploys and reconciles them across all environments, regions, and severities.
Self-Service Infrastructure Portal
A Vue.js and .NET portal that lets developers self-provision repositories, manage permissions, and request infrastructure through approved templates and guardrails instead of tickets.
Distributed Kubernetes Homelab
A multi-node K3s cluster on personal hardware running GitOps delivery, observability, and secrets management behind an Envoy Gateway and Cloudflare Tunnel — it hosts this very site.
Credentials & certs.
A separate site for the writing.
Opinions, the K3s lab, and cert guides — kept off the portfolio so they can grow on their own at blog.cjoga.cloud.
This is where I write things down.
A working handbook — opinions, the K3s lab that runs cjoga.cloud, the consulting work that pays the bills, and cert guides for the certs I think are worth your time. Nothing here is for sale. Read whatever's useful.
Honest cert guides — my experience, my tips, and the runbooks I'd hand to a friend.
New pages land when they're ready, not on a schedule. If something here is wrong, or you want to talk about the work, email is the right channel.
Explore my infrastructure.
A live, read-only terminal connected to the K3s cluster powering this site. Browse namespaces, inspect pods, and poke around — it's your shell.
Get In Touch
My inbox is open. Questions about the work, the lab, or a role — email gets answered.
Phone: +1 (809) 881-7982