IT Systems Coordinator

Responsibilities

• Manage the IT systems function for a Mérida colonial boutique or four-star hotel: as the primary IT professional for a 50–200 room property, own the network infrastructure, PMS support, POS, guest Wi-Fi, IP telephony, CCTV, and the administrative systems — in a market where vendor support is less immediately accessible than CDMX or Guadalajara, the Mérida hotel IT coordinator is a more self-sufficient technical operator than their urban counterparts
• Manage the hotel's internet connectivity with Mérida-specific ISP reliability: Telmex fiber and alternate ISP options are available in Mérida but the redundancy architecture requires active management — the IT coordinator maintains the primary and backup internet connections (fiber primary, LTE backup) and the automatic failover that keeps guest connectivity operational during ISP outages
• Maintain IT hardware under Mérida's extreme heat conditions: the April–June heat season (38–42°C) creates thermal stress on IT hardware that is most severe in non-air-conditioned spaces (outdoor AV equipment, camera housings, network cabinets in service corridors) — the IT coordinator manages the heat-season hardware monitoring, the cooling maintenance for the server room, and the UPS battery health check before each heat season to prevent heat-accelerated battery degradation
• Support the hotel's European cultural tourism guest technology expectations: the Mérida boutique hotel's French and European guest profile may include guests accustomed to high-quality Wi-Fi in European urban hotels — the IT coordinator maintains the guest Wi-Fi performance at a standard that serves European guests with streaming and video calling requirements during their archaeological tourism stay
• Manage the Chichén Itzá high-season technology capacity: the archaeological high season (October–February) is the hotel's peak occupancy period — the IT coordinator prepares the technology infrastructure for peak concurrent users and validates the system performance before the season begins
• Coordinate vendor support from Cancún and CDMX for hardware and software issues beyond local resolution capability: the Mérida IT coordinator maintains the vendor contacts and the remote support relationships that provide access to technical expertise not locally available in the Yucatán market

Requirements

• IT systems coordinator or administrator experience; regional hotel or small enterprise preferred
• Self-sufficient IT operation in a limited vendor support market
• Connectivity resilience management (fiber + LTE failover)
• Heat-season hardware thermal management
• Spanish native; English functional for European guest technology support; French awareness an advantage

Benefits

• IMSS, aguinaldo, paid vacation + premium
• Transport subsidy MXN 500/month
• Staff meals
• Technology certification development
• Career development toward IT Manager in Mérida's growing hotel sector

Work environment

IT systems coordinator at a Mérida colonial boutique or four-star hotel. Self-sufficient hotel technology management with heat-season hardware thermal care, European guest Wi-Fi performance standards, Chichén Itzá season capacity planning, and remote vendor support coordination in Yucatán's growing hotel IT market.

About the role

The Mérida hotel IT coordinator who manages the April heat season preparation — who schedules the server room air conditioning unit's preventive maintenance on March 28 (before the heat season begins), who checks the UPS battery capacity after last year's heat season degradation, who adds additional ventilation to the network cabinet in the service corridor that runs at 38°C in May, who replaces the outdoor CCTV camera housing gaskets before the first 40°C day — who arrives at May 1 with an IT infrastructure that has been physically prepared for the heat it will face for the next 8 weeks — has done the preventive maintenance work that prevents equipment failure during the period when replacement parts from Cancún take the longest to arrive. The hardware that doesn't fail in May didn't fail because someone thought about April.