Zeke Maldonado has been named acting Chief Information Officer of the Federal Emergency Management Agency, placing a former Department of Homeland Security IT operations leader at the top of FEMA's technology organization.

The appointment, as reported by ExecutiveGov, marks a transition that draws directly on departmental experience. Maldonado previously led IT operations at DHS, the parent department of FEMA.

What does the appointment change at FEMA?

FEMA's CIO role carries enterprise-wide authority over the agency's technology portfolio. The position oversees systems modernization, IT service delivery across disaster response operations, and the cybersecurity posture of the agency's networks and applications.

An acting CIO assumes the full range of those authorities on a temporary basis, including signature control over IT acquisition packages, the agency's cloud migration roadmaps, and the annual IT budget submission.

Federal agencies use acting designations most often when a permanent CIO has departed, when a new administration is reshaping senior leadership, or while a nominee clears the formal vetting process. The designation lets the agency maintain continuity in IT decision-making without interruption.

Why does the DHS background matter?

FEMA sits organizationally within DHS, alongside other component agencies such as Customs and Border Protection, the Secret Service, Citizenship and Immigration Services, and the Coast Guard. That structure means DHS enterprise IT decisions, shared services platforms, and cybersecurity controls routinely extend into FEMA operations.

A CIO who previously led IT operations inside DHS would already understand the shared infrastructure backbone, the department's enterprise architecture framework, and the cybersecurity oversight structures that govern component technology spending. That familiarity typically shortens onboarding and reduces friction during IT investment reviews, particularly during the budget formulation cycle when component agencies submit their IT spending plans to DHS headquarters.

How does FEMA's IT mission differ from departmental IT?

DHS headquarters IT functions primarily support policy, intelligence coordination, and departmental administration. The work runs on a relatively predictable cadence tied to the budget calendar and the congressional appropriations cycle.

FEMA's technology portfolio, by contrast, must remain operational during active disaster response, when personnel surge into regional offices and the agency coordinates with state emergency operation centers, federal partners, and voluntary organizations. System uptime requirements are measured against disaster declaration timelines, not business hours.

An acting CIO stepping in from DHS IT operations inherits a different mission tempo. The shift from steady-state departmental operations to disaster-coordinated response cycles shapes how technology investments, system uptime requirements, and cybersecurity incident response get prioritized.

What remains unknown?

The ExecutiveGov report does not state the effective date of the appointment, the identity of the predecessor Maldonado is replacing, or how long the acting designation is expected to last. Subsequent announcements would clarify whether a permanent nominee is already in process.

Federal IT leadership watchers will look for signs of an acting-to-permanent conversion, an interim period that often spans several months while formal selections clear review and, in some cases, Senate confirmation for senior agency roles.

What to watch next

Acting designations in federal agencies typically resolve in three patterns: a permanent appointment, an extension of the acting period, or a rotation to another leader. Each path reshapes the agency's IT strategic plan cadence, contract award timelines, and workforce planning.

CIO Monitor will track subsequent announcements, any published transition memos from FEMA's Office of the CIO, and the timing of permanent selection announcements.