Systems Architect / Mission-Critical Systems / Brazil

Systems,
clearly.

I turn complex systems, difficult transitions and emerging technologies into clear paths forward.

Fernando Gomes
Sao Paulo / 2026
20+years building critical systems
R$10B+in financial assets supported
15k+monthly healthcare consultations
30+engineers led across continents

Selected work / 01-04

Complexity, made useful.

A selection of systems, transitions and decisions where architecture created measurable business value.

01

Healthcare / Data architecture

A shared language for fragmented healthcare data.

Designed a FHIR-based Health Lake at Hospital Sirio-Libanes, creating a reliable integration layer between clinical systems, partners and digital products.

OutcomeIntegration time reduced by 50%
DomainAWS / FHIR / Event-driven systems
02

Public infrastructure / Enterprise architecture

A technology roadmap built for national scale.

Architected the strategic technology roadmap for Caixa Loterias, balancing modernization, operational risk and an infrastructure designed for billions of annual transactions.

OutcomeDesigned for billions of yearly transactions
DomainCloud-native / Strategy / Systems design
03

Financial systems / Modernization

Modernizing the core without losing its rigor.

Built and evolved calculation, accounting and contract engines for Banco BV while establishing the architecture practice that guided its move from monoliths to distributed systems.

OutcomeR$10B+ in assets supported
DomainJava / Microservices / Financial systems
04

Applied AI / Public sector

Two days of paperwork. Thirty minutes.

Designed AI-agent workflows for the Brazilian Paralympic Committee that read, check and assemble accountability reports which used to take a team two full days.

Outcome2 days → 30 minutes
DomainPython / LLMs / Agent workflows

Operating principles

01

Architecture over hype.

Technology earns its place by improving the system, not the presentation deck.

02

Modernization without amnesia.

Legacy systems contain hard-won knowledge. The goal is to move it forward, not erase it.

03

Architecture is a business decision.

Availability, cloud cost, regulatory risk, delivery speed. If a design choice doesn't answer to one of these, it doesn't ship.

04

AI needs engineering, not magic.

Reliable AI comes from boundaries, verification and intentional workflow design.

Thinking in systems

Notes from the field.

All writing

Journey / 2005-Now

Two decades of building forward.

Full resume
  1. 2005EverMobileSoftware Engineer
  2. 2012CI&TSenior Java Developer
  3. 2017Banco BVTech Lead
  4. 2021Hospital Sirio-LibanesEngineering Lead
  5. 2024Stellula & The CollabFounding Engineer
  6. 2026PayPal (via Ambush)Software Engineer / Present

Start a conversation

Have a difficult system?
Let's make it clear.