Enrique Sevilla
  1. 01 / 06 · Commit

    Everything starts with a commit.

    Small, reviewable changes that land on the main branch.

  2. 02 / 06 · Build

    Build.

    Reproducible images with pinned versions.

  3. 03 / 06 · Test & scan

    Test and scan.

    Automated tests and secret scanning before anything ships.

  4. 04 / 06 · Deploy

    Deploy.

    One pipeline publishes to the cluster, no manual steps.

  5. 05 / 06 · Run

    Run.

    Deployments, replicas and services designed to scale and to be operated.

  6. 06 / 06 · Self-heal

    Self-heal.

    When a pod fails the platform replaces it, and observability tells you why.

Enrique Sevilla

José Enrique Sevilla Larrea (Enrique Sevilla): Software & DevOps Engineer

I build solutions to problems; technology is only a means.

9+ years building software

Connect on LinkedIn See my trajectory

Trajectory

From full-stack development to platform and DevOps engineering.

  1. FRQTAL

    Fintech

    DevOps Engineer & Sr. Backend Developer

    – Present

    • Design and operate Kubernetes infrastructure on GCP: autoscaling, ingress, persistent storage and private networking.
    • Own observability end to end (metrics, logs, traces) and secrets management with workload identity and KMS.
    • Build and harden backend services: authentication, sessions, payments and multi-chain transactions.
    • Take products from prototype to production-grade architecture, backed by automated tests and CI/CD.
    • Kubernetes
    • GCP
    • Helm
    • ArgoCD
    • GitLab CI
    • GitHub Actions
    • Grafana
    • Prometheus
    • Loki
    • Tempo
    • Node.js
    • TypeScript
    • PostgreSQL
    • Redis

  2. RedGps

    Vehicle and asset tracking

    Infrastructure Developer (SysAdmin)

    –

    • Automated recurring Linux operations with PHP and Bash scripts.
    • Monitored services with Nagios and Grafana; optimized MySQL queries.
    • Maintained and modernized legacy projects.
    • Linux
    • Bash
    • PHP
    • MySQL
    • Nagios
    • Grafana
    • Apache

  3. Puller Tech

    Backend Developer

    –

    Fullstack Web Developer

    –

    • Built the backend of the second version of a school management system, following clean-code practices.
    • Containerized services with Docker and Compose, added Redis caching and per-environment test data.
    • Documented APIs with Swagger and covered them with automated tests.
    • Laravel
    • PHP
    • Node.js
    • Docker
    • Redis
    • MySQL
    • PostgreSQL
    • AWS S3
    • Vue.js

  4. Grupo Mas Ecommerce

    Backend Developer

    –

    • Email automation with S3 attachments, project documentation and BI dashboards maintenance.
    • PHP
    • Zend
    • MySQL
    • Tableau
    • AWS S3

  5. Freelance

    Fullstack Web Developer

    –

    • Custom modules, legacy maintenance and landing pages for clients.
    • PHP
    • JavaScript
    • MySQL

  6. Innotecnia

    Software Engineer Jr

    –

    • Desktop business software: employee management with dynamic reports and a quoting tool.
    • Delphi
    • SQL Server

Selected work

Problems I have solved, told the way I would explain them to a colleague. Described in general terms; the details stay with the teams that own them.

Observability

One view of a fragmented infrastructure

Built with

  • Grafana
  • Prometheus
  • Loki
  • Tempo
  • ClickHouse
The problem
Infrastructure was spread across several providers and servers, each with its own logs and metrics. Understanding the health of the whole system meant checking many places, and nobody had the full picture.
What I did
Centralized metrics, logs and distributed traces in Grafana and Prometheus, with Loki, Tempo and ClickHouse behind them. Standardized structured log lines across services, connected the separate networks so everything reports to one place, and wired critical alerts to Telegram.
The outcome
A single source of truth to diagnose incidents. Bringing a new server or service into monitoring became a routine step, and the stack runs in production today.

Security

Secrets and identity, without exposed keys

Built with

  • Workload Identity
  • Secret Manager
  • KMS
  • IAM
The problem
Secrets lived where the code ran: environment variables, long-lived access keys, and signing keys that servers could read. A single compromised machine would have exposed everything.
What I did
Moved cluster workloads to Workload Identity so they reach cloud services without key files, stored secrets in Secret Manager with per-secret grants and loaded them at runtime, and delegated transaction signing to KMS so private keys never reach application code.
The outcome
No static cloud keys on servers, secrets readable only by the identities that need them, and signing keys that stay inside KMS. Rolled out across QA and production.

Architecture

From fragile prototypes to a base that can change safely

Built with

  • Node.js
  • TypeScript
  • React
  • Jest
The problem
Products built quickly had grown into monolithic entry files and a scattered frontend, with gaps in validation, authorization and session handling.
What I did
Audited the code, then moved the backend to hexagonal, domain-sliced modules and the frontend to feature folders. Added input validation to every route, uniform error handling and integration tests per domain, and closed the injection and session-hijacking paths the audit found.
The outcome
Smaller entry points, tested domains and sessions that can be revoked server-side: a codebase that is safer and faster to change.

Data

A database that enforces its own consistency

Built with

  • PostgreSQL
  • Migrations
The problem
The schema had grown organically: inconsistent primary keys, lists of entities hidden in JSON columns, text identifiers where real types belonged, and columns nobody used.
What I did
Planned the change as small, reversible phases: restructured tables, split composite columns into proper relations, added real keys and constraints, and removed unused fields only after verifying nothing read them.
The outcome
Deployed to production with a prior backup and an integrity check. The schema is now consistent and enforced by the database itself.

Real-time

Video calls that hold up in the real world

Built with

  • WebRTC
  • TURN
  • Redis
  • Socket.IO
The problem
Calls failed across restrictive networks and could not scale past a single server instance.
What I did
Used Redis as the socket adapter so several instances share state, deployed a TURN relay with rotating credentials for networks that block direct connections, and fixed a resource leak in the media server.
The outcome
Reliable video calls with screen sharing running in production, with relay behaviour verified end to end.

Stack

What I work with day to day. Frontend at a functional level; backend and platform are my strengths.

Cloud & platform

  • GCP
  • AWS
  • Kubernetes
  • Docker
  • Helm
  • ArgoCD
  • nginx
  • Linux

CI/CD

  • GitLab CI
  • GitHub Actions

Observability

  • Grafana
  • Prometheus
  • Loki
  • Tempo
  • ClickHouse

Backend

  • Node.js
  • TypeScript
  • PHP
  • Laravel
  • REST APIs
  • Swagger

Data

  • PostgreSQL
  • MySQL
  • MongoDB
  • Redis

Security

  • IAM
  • Secret Manager
  • KMS
  • Workload Identity
  • TLS

Testing

  • Jest
  • Playwright

Frontend

  • React
  • Vue.js

Education

B.Sc. in Computer Science Engineering

BUAP · 2013 – 2018

Degree conferred in 2023 by thesis: an interactive prototype for learning Spanish accentuation rules, presented at CONTE 2023.

Speaker at CONTE 2023 and guest workshop instructor at university events.

Certifications & training

  • EGEL-ICOMPU (Ceneval): satisfactory performance, outstanding result in computer systems selection.
  • Courses: DevOps (Docker, Kubernetes, CI/CD), DevSecOps with GitLab, Grafana, and large-scale systems design.
  • AWS Training: Cloud Practitioner Essentials.

Let's talk

The best way to reach me is LinkedIn.

Open LinkedIn
This site ships the way I work
git push origin main
main -> main
gh run watch
✓ secrets scan  ✓ build  ✓ smoke test  ✓ deploy
curl -sI https://jesevilla.dev/en/ | head -1
HTTP/2 200