Ernesto Majó divided LACNIC's technology leadership

Ernesto Majó Split LACNIC’s Tech Job: One Chief for the Servers, One for the Horizon

Why it matters

A registry can put its best engineer in every meeting, or let someone else keep the machinery humming. Majó chose two desks and made the division public.

Sofia Ren25 October 2026Reading Time 2 minLast update: 25 October 2026

Ernesto Majó. LACNIC’s named photograph grounds the portrait; the racks and empty strategy table illustrate his 2025 split of technical jobs.

Summary

Ernesto Majó's 1 October 2025 announcement set a new LACNIC structure for 1 November: Carlos Martínez became Chief Technology Strategist and Juan Carlos Alonso took the CTO job.
Diego Mena received a separate strategy and organisational development unit. The practical test is whether operations, technical advice and risk decisions now have clear owners.

The old technology-chief job was carrying two very different calendars. One contains uptime, infrastructure and the next awkward service incident. The other contains standards meetings, global coordination and the slow business of developing future technical leaders. Ernesto Majó's answer was to give those calendars different desks.

In a 1 October 2025 announcement, LACNIC's executive director said a new functional structure would take effect on 1 November. Carlos Martínez, then CTO, would move into a newly created Chief Technology Strategist role. His brief covered advice to the executive director, support to operational departments, global technical coordination and the development of new technical leaders. Juan Carlos Alonso, then head of IT operations, would become CTO with responsibility for technical services.

There was a third chair. Diego Mena would lead a new Strategy and Organisational Development Unit as Chief Strategy Officer, with information security, transparency and risk management among its concerns. Carina García would take greater responsibility in administration and finance. The reshuffle was broader than a neat CTO swap, but the two technology roles reveal its central design choice: the person speaking for long-term technical direction need not be the person answerable for the machines at 03:00.

LACNIC's Spanish original states the assignments and effective date; its current Carlos Martínez author profile calls him Chief Technology Strategist. These records establish a public allocation of roles. They contain no before-and-after service figures, incident totals or decision-rights charter. The next evidence worth publishing is a service-accountability map showing who signs off when advice, engineering priority and risk appetite collide.