Ricardo Yanez

About

I never really stopped being a software engineer.

My responsibilities grew from implementing software to shaping systems, technical direction, and engineering work. The hands-on part never disappeared.

A widening scope

  1. Software Engineer
  2. Senior Software Engineer
  3. Software Architect
  4. Lead Software Engineer

The work today

What changed, and what did not.

Over time, I took on more responsibility for architecture, technical decisions, system design, mentoring, development coordination, infrastructure, and operation.

I still write and review code, investigate failures, design solutions, and build proofs of concept. Staying close to implementation keeps my decisions tied to the system the team actually has to maintain.

I am most interested in the decisions that survive contact with production: clear boundaries, explicit trade-offs, useful diagnostics, and changes that another engineer can understand later.

Background

From legacy systems to cloud platforms.

I have been building software since 2006. I started with desktop and business systems in Venezuela, later worked remotely with teams in Costa Rica, and continued my career in Chile.

That path has taken me through legacy migrations, financial software, integrations, distributed workflows, cloud infrastructure, and engineering leadership. It is why I care as much about changing a system safely as I do about designing the next one.