Célio Crisólogo

ContextCrowdfunding platforms — Mohz and IOX — run via VPN — Venha Pra Nuvem, operating simultaneously within a larger portfolio of digital products.

RiskCrowdfunding involves third-party money and regulatory obligations: an integration failure, incomplete traceability or a poorly managed promotion between environments affects investors and issuers, not just the system.

RoleLeading the squad and the technical direction: architecture, observability, security and modernization discussed with product, QA, infrastructure and the client. Investigation of incidents and integration failures, with Sprint Reviews and Plannings used to turn technical findings into backlog priorities.

Perceived impactA standardized, auditable engineering cycle, with changes traceable from work item to production and a shorter distance between what is planned and what actually ships.

ContextA high-responsibility banking ecosystem at Itaú, with asynchronous transfer flows in continuous operation.

RiskAny instability affected traceability and the continuity of sensitive flows.

RoleIncremental evolution of Go services, focused on contracts, messaging and observability.

Perceived impactMore predictable operations, safer evolution and less friction for new technical cycles.

ContextCAIXA's banking platforms, with high demands for availability, compliance and operational security.

RiskCoupling and structural fragility raised the technical risk of evolving sensitive flows.

RoleDomain-driven architectural definition and technical governance for incremental modernization.

Perceived impactFewer fragilities, more predictable evolution and more stable support for operations.

ContextAdvisory work at Bradesco, Santander and Banco do Brasil to define architecture and prioritize modernization.

RiskLate or imprecise decisions raised continuity risk and amplified fragility in critical operations.

RoleTechnical risk mapping, definition of architectural paths and implementation guidance.

Perceived impactGreater architectural clarity for next steps, safer evolution and lower operational exposure during changes.

ContextIntegration between IBM's enterprise platforms and heterogeneous ecosystems, with high operational dependency across domains.

RiskUnstable interoperability increased rework and the risk of inconsistency in critical flows.

RoleStructuring API architecture and integration contracts with traceability and quality discipline.

Perceived impactMore stable flows across domains, less technical friction and evolution with less fragility.