Senior Backend Engineer | Tech Lead · SRE & Automation | Agentic AI
CDMX, Mexico · English B1 · B2 technical reading/writing
Senior Backend Engineer and Tech Lead with 10+ years in Python, SQL and AWS. I help make operations reliable and automated — blameless post-mortems, monthly uptime/downtime tracking, runbooks and n8n automations that cut manual work — and I build software with Spec-Driven Development (SDD/OpenSpec) and AI agents (Claude Code). Previously, technical lead of international GK POS rollouts across Latin America.
I work AI-native: Generative AI is the central copilot of my SDLC, not an afterthought. My practice is Spec-Driven Development (SDD/OpenSpec) — the spec is the source of truth, and every change flows through versioned artifacts before a line of code is written.
Requirements and verifiable scenarios drive the work. AI generates specs, analyzes code statically and proposes implementations against the contract — shortening review cycles.
Claude (Anthropic), Gemini and OpenAI across the loop: specs, analysis, debugging, RCA & post-mortems and technical documentation — plus an AI Skill in progress to classify and route tickets, with human review when confidence is low.
Agentic workflows with RAG and AI agents. This very site ships structured JSON-LD and a /llms.txt so agents and LLMs can read my profile directly.
★ 100% built with Spec-Driven Development (SDD/OpenSpec) — the spec is the source of truth in every project.
An educational platform I built as a hobby and use to practice technologies and AI: Spec-Driven Development with Claude Code (subagents, skills and hooks), real-time multiplayer games, Supabase Auth and Postgres with RLS, and CI tests.
Multi-business digital loyalty (mobile-first QR, nothing to install) with all the business rules in PostgreSQL: multi-tenant RLS, PL/pgSQL RPC, anti-replay QR tokens and feature flags. 100% SDD/OpenSpec with 5 specialized AI agents.
Self-hosted observability stack (Grafana + Docker) with a single pane over three sources: AWS serverless (Lambda invocations/errors/duration + S3) via CloudWatch, local Docker containers (CPU/memory/health), and Trackion's tickets & SLA. Automated collection with n8n + a read-only IAM role. 100% SDD/OpenSpec.
Multi-tenant, white-label SaaS for EV charging-station operators: live station status over WebSocket (polling fallback), tenant isolation via PostgreSQL Row-Level Security (RLS), RBAC (superadmin/org_admin/operator/viewer) + SSO (OIDC), analytics (uptime, kWh, CSV export), an auditable state scheduler and an installable PWA. 100% SDD/OpenSpec.
White-label serverless help desk: end-to-end ticketing (categorize, prioritize, assign, history; open→in_progress→resolved→closed), admin-managed catalogs, and an open API-integration module (generic inbound webhooks + outbound domain-event dispatch) to plug any external system without touching the core. Grafana tickets & SLA dashboards. 100% SDD/OpenSpec; runs locally via Docker.
ETL middleware that automates master-data integration into GK Software retail systems: watches directories, transforms Excel → GK XML across four interfaces (stores, operators, promotions) and transmits via SFTP/FTP — with a Flask web panel (config, operation, audit), a scheduler and SQLite auditing. Re-engineered under SDD/OpenSpec: idempotent single-pass pipeline, pooled SFTP/SQLite connections, and security hardening (parameterized/whitelisted SQL, secrets out of the repo).
Notes from building AI-native: Spec-Driven Development, Docker and observability — drawn from real projects. Project deep dive: Fidello.
The full flow (proposal → specs → design → tasks → apply → verify → archive) on a real change of this repository: 8 specs, 8 design decisions, 47/47 automated checks and a CV calibrated to exactly one page.
Read ↗Why I treat the spec as the contract and code as its current implementation — the artifact flow (proposal → specs → design → tasks → apply → archive), and why it shortened my review cycles.
Read ↗From an always-on EC2 to a reproducible local stack (Grafana + PostgreSQL + n8n): $0 idle, idempotent, and still cloud-aware over a read-only IAM role.
Read ↗One pane over three sources: AWS serverless (CloudWatch), local Docker containers, and application data (tickets & SLA) — correlating infra and business signals.
Read ↗An honest inventory, not a keyword list. Own = built end-to-end and operationally owned · Build = solutions I assemble recurrently · Operate = fluent for diagnosis and operations, not building the platform · Learning = directed study, no operational depth yet.
Built it end-to-end; if it breaks, they call me.
I assemble solutions with these on a recurring basis.
Fluent for diagnosis and operations; I don't build the platform.
Directed study; no operational depth yet.
| Spanish | Native |
| English | B1 — Intermediate (reading, writing & technical communication) |
Instituto Tecnológico de Orizaba · 2006 – 2011
Orizaba, Veracruz, Mexico
Quick Learning · In progress
Online
Looking for job opportunities? Let's talk!
Or send me a message:
A real mini-terminal. Type help and press Enter. 😉