A career spent building software systems — and, over time, deciding how those systems should be structured.

I am a software engineer based in Medellín. The work started in systems analysis and internal platforms, moved through backend and ecommerce engineering, and now sits at the intersection of architecture, technical leadership, and product delivery.

That progression is the point. Analyst, then systems coordinator, then senior developer, development coordinator, senior backend engineer, technical lead, and head of research and development. Each step added a different constraint: correctness, operations, delivery, coordination, then the shape of the system itself.

Most of the work has been backend-heavy: PHP platforms (Laravel, Symfony, and earlier CakePHP and Yii), Python workers for high-throughput processing, relational data models (PostgreSQL, MySQL, Oracle), and JavaScript frontends (React, Next.js, Vue.js). More recent platform work has included hexagonal / DDD services, Redis Streams, an API gateway, containerized delivery with Docker and Kubernetes, and infrastructure involving Google Cloud, Redis, Memcached, and process supervision.

I have led development teams, made technical decisions, managed budget for a private ERP, coordinated custom platforms for a trade federation, and shipped on international ecommerce products — including payment integrations and third-party store connections. The through-line is not a framework list. It is judgment about how to design software that other people have to operate, extend, and live with.