Platform Engineer @ Bizzdesign · DevOps / SRE · Cloud-Native · Containerization · Observability
· Trading and AI hobbies ·
- Currently working as a Platform Engineer at Bizzdesign, focusing on cloud-native platforms, Kubernetes and reliability.
- DevOps / SRE background in cloud-native and distributed systems.
- Experience building organization-wide observability and DevOps standards for multiple teams.
- Helped improve reliability, cost efficiency and developer experience through automation and better architecture.
- Strong interest in how AI/ML and trading systems intersect with reliability, latency and real-world infrastructure.
- Designing and running Kubernetes-based platforms for microservices.
- Building observability stacks with OpenSearch, Fluent Bit, Prometheus, Grafana and OpenTelemetry.
- Using Infrastructure as Code and GitOps to keep environments reproducible and auditable.
- Exploring AI / MLOps for anomaly detection, monitoring and automated operations.
- Learning more about trading infrastructure and SRE practices for low-latency, high-reliability environments.
-
Platform Engineer – Bizzdesign
Working on platform engineering for cloud-native workloads, reliability and developer experience. -
DevOps Architect / DevOps Engineer
Built observability platforms, standardised DevOps practices, operated analytics platforms and worked on multi-cluster Kubernetes and GitOps. -
Adjunct Lecturer
Supervised Master’s projects (cloud, orchestration, MLOps) and participated in academic committees. -
Software Engineer
Delivered monitoring, data/ML solutions and production systems with measurable business impact.
- 🧪 CKA – Certified Kubernetes Administrator
- 🧪 CKAD – Certified Kubernetes Application Developer
- ☁️ AWS Certified Solutions Architect – Associate
- ☁️ AWS Cloud Practitioner
- 🗣️ C1 English certification
- SRE mindset – SLIs, SLOs, error budgets, runbooks and postmortems as part of the process.
- Automation first – if it’s repeatable, it should probably be a pipeline or a script.
- Observability by default – logging, metrics and traces are design requirements.
- Pragmatic – boring, reliable solutions > over-engineered complexity.
- Teach & learn – mentoring, supervising projects and creating reusable patterns.
- LinkedIn: Mikel Vallejo del Moral