My specialty
Observability
Knowing at all times what is happening inside the systems and getting an alert before a problem reaches users.
Tools:PrometheusGrafanaLokiMimirAlloyELK
Open to new opportunities
Jose Miguel
Izarra Guerra
DevOps Engineer · specialised in observability
Valencia, Spain · working remotely
I make sure a company's applications run smoothly, get updated quickly and safely, and that any problem is caught before a customer notices it.
This is what I do. Click any box to learn more. continuous monitoring
profile
About me
I started out building applications. Today I build the bridges that get that software to its users and keep it running without surprises.
I'm a DevOps Engineer at a technology consultancy, working for different clients across the three major clouds: AWS, Azure and Google Cloud. My specialty is observability: making sure a team always knows what is happening in its systems and can react before a failure affects its customers.
I'm curious and self-taught. In a field where what you learned yesterday may be obsolete tomorrow, my greatest skill is learning fast: if a tool comes out that improves a process, I'm probably already trying it in my home lab.
- Valencia · remote
- Spanish & English
- Scrum
- Azure certified
areas
What I do
The areas from the diagram, explained.
Multi-cloud
Cloud
I design infrastructure on the three major clouds, ready to grow and to withstand failures.
Tools:AWSAzureGoogle Cloud
Infrastructure as code
Everything reproducible
I describe infrastructure in files so it is created automatically, can be reviewed and is always the same.
Tools:TerraformAnsiblePuppetCrossplane
Secure automation (CI/CD)
Release without fear
I automate the path from code to users, with security checks at every step.
Tools:GitHub ActionsGitLab CIAzure DevOpsSonarQubeVault
Containers
Applications that adapt
I run the platforms where applications live, which grow or shrink on their own depending on demand.
Tools:KubernetesHelmDocker
FinOps
Cost savings
I right-size cloud resources so the company only pays for what it really needs.
Techniques:AutoscalingSpot instances
cases
Projects
What the problem was, what I did and what changed.
One system to monitor many clients' platforms
- The challenge
- Every client had its own systems (servers, databases, applications…) and there was no common way to monitor them.
- What I did
- I designed a central platform that receives data from all of them, keeping each client's data separate and protected.
- Result
- Custom dashboards and automatic alerts for every client from a single place, ready to grow.
With:GrafanaMimirLokiAlloyKubernetes
Complete infrastructure for a fintech, from scratch
- The challenge
- An online financial-management company needed its entire cloud infrastructure, ready for production and for growth.
- What I did
- I built it from scratch on Azure, entirely as code: servers, databases, storage, secure access, API management, automated releases, monitoring and email delivery.
- Result
- A secure, scalable platform for financial operations that can be rebuilt identically at any time.
With:TerraformAzureKubernetesWSO2 API ManagerGitLab CIPrometheusLokiAmazon SES
Publishing code in any language, with no manual steps
- The challenge
- A technical-assessment platform needed to instantly publish the exercises candidates submitted, written in very different languages.
- What I did
- I designed an automated process: whenever someone uploads code, it is security-checked, packaged, deployed to the cloud and given its own web address.
- Result
- Every project goes live and becomes accessible without anyone having to step in.
6+ languages Java, React, Python, Node.js, Vue, .NET… through the same process
With:GitLab CIDockerKubernetesCloudflare
Declarative infrastructure for a multinational
- The challenge
- A multinational manages its Azure resources declaratively: it describes what it needs and the system creates it.
- What I did
- I maintained the templates that define that infrastructure and the workflows that create it automatically, making sure everything worked correctly.
- Result
- Cloud resources created automatically, consistently and in a reviewable way.
With:CrossplaneKubernetesGitOpsAzure
Paying only for what is used
- The challenge
- The cloud bill was high because resources were oversized all the time.
- What I did
- I made applications grow and shrink automatically with demand, and used cheaper machines where possible.
- Result
- Lower cloud spend without losing performance.
With:KubernetesAutoscalingSpot instances
career
Experience
- Feb 2025 — nowCurrent · remote
DevOps Engineer · CloudAPPi by WaimaGroup
I design and maintain critical infrastructure for several clients on AWS, Azure and Google Cloud, working in agile (Scrum) teams.
- Mar 2024 — Feb 2025Remote
DevOps Engineer · Waima Group
Multi-cloud infrastructure, release automation with built-in security and proactive monitoring for clients in different sectors.
- 2022 —Education
Higher Technician in Multiplatform Application Development · IES Benigasló
Where I come from: I started out building applications, so I speak the same language as development teams.
Certifications
- Microsoft Certified: Azure Administrator AssociateMicrosoft · October 2026
- API OwnerapIAddicts · April 2024
connect
Contact
Shall we talk?
If you're looking for someone to make your systems more reliable, easier to monitor and cost-efficient, get in touch. I reply within 48 hours.
Message me on LinkedIn