Julio Gómez RiveraComplex systems. Recoverable, repeatable and governable.
I work across architecture, Platform Engineering, security and technical modernization: from understanding a system and making engineering decisions to validating that teams can operate it without depending on its architect.
TO RUN
From physical engineering to digital platforms.
My understanding of architecture began with electrical installations, industrial refrigeration and refrigeration systems aboard tuna fishing vessels, where engineering had to work under real operating conditions.
Computing entered my life early, driven by curiosity: programming, computers and networks in my teenage years. Over time, those two worlds converged into a career spanning networking, infrastructure, virtualization, identity, cloud and security.
Technologies change, but dependencies, operations, failures and decisions still matter. I therefore see a platform not as a product list, but as a complete system that must be understandable, protectable and able to evolve.
Abstractions change. Engineering principles do not.
My work has evolved from infrastructure and critical operations through identity and cloud to Platform Engineering and operational trust. The recurring challenge remains the same: understand the system, reduce uncertainty and leave something that teams can operate and evolve.
Systems → Critical operations → Infrastructure → Identity → Cloud → Platform Engineering → Operational trust
Systems and transformations I have helped design, recover or industrialize.
Throughout my career I have worked on projects where technology had to address real business, operational and transformation challenges, from critical infrastructure and enterprise environments to cloud platforms, identity and security.
Platform Industrialization
I contributed to redesigning and industrializing a multi-tenant AWS platform, separating foundations, runtimes and product workloads, with structural tenant isolation and infrastructure as code. Moving toward a more autonomous, reproducible operating model enabled Operations and DevOps teams to provision, deploy and manage environments with less reliance on specialist intervention.
Networking Architecture for Critical Infrastructure
Networking Architect on a specialized air traffic management platform. Responsible for network architecture and cross-functional collaboration with infrastructure teams on COTS integration, stack dependencies, laboratory environments and end-to-end validation. Application development and other disciplines retained their respective responsibilities.
Enterprise Identity Modernization
I contributed to the initial identity architecture covering federation and directory services, privileged access, authentication and identity governance, including architectural definition and proof-of-concept work.
IAM Architecture & MVP
I joined a broader technology transformation to address an IAM architecture gap: redesigning the solution, building a ForgeRock-based MVP and defining an integration model for legacy and mainframe systems.
IT Operations Management and Infrastructure Architecture
IT operations management and technical leadership in technology transformation projects for an international hotel group. Responsibility for infrastructure architecture, communications, technology services and modernization across corporate and hotel environments, aligning engineering decisions, operational continuity and business needs.
Architecture should reduce dependencies, not create them.
Understand the system before choosing the technology.
Make boundaries and responsibilities explicit.
Treat recovery and operability as architectural concerns.
Automate repeatable work without obscuring critical decisions.
Validate the end-to-end system, not just its components.
Transfer enough context and capability for teams to operate autonomously.
Secure Infrastructure by Design
I see architecture as a discipline connecting technology, security and operations. Building systems that work is not enough: they must remain understandable, adaptable, recoverable and maintainable over time.
Secure Infrastructure by Design is part of this approach. Security, identity and operational capability must be considered from the earliest design decisions.
Identity First is one of my core principles: knowing who or what interacts with a system, what it can do and under which conditions. From people to services and automation, identity provides the foundation for trust and control.
My goal is to design platforms that allow teams to work autonomously without sacrificing security, traceability or infrastructure governance.
Identity First. Identify people, services and automation before defining access and responsibilities.
Governable infrastructure. Understand responsibilities, changes and authority boundaries.
Operational resilience. Design to recover services and knowledge, not merely to keep them available.
Responsible automation. Accelerate operations without losing context, validation or traceability.
Cross-domain architecture. Consider networks, identity, platforms, people and operations as one system.