A large part of my job is making sure a system stays correct when thousands of people try the same thing, at the same time.

01 / Career

Career

Three companies, ~19 years of production code — each adding a different layer of scale, domain, or concurrency.

1. Senior Software Engineer · SOAP Health

   dez/2022 — atual

   AI healthcare company focused on clinical data interoperability (Remote — USA)

   • Built scalable full-stack features with Node.js, Remix, and TypeScript.
   • Integrated with US EHR systems via secure APIs.
   • Refactored database models with Prisma and PostgreSQL, improving API response time.
   • Node.js
   • TypeScript
   • Remix
   • React
   • PostgreSQL
   • Prisma
   • Docker

2. Software Engineer · UNIFOR (NATI)

   jul/2012 — dez/2022

   Innovation center managing large-scale academic ecosystems

   • Architected a reusable enterprise framework in Java/Spring Boot, adopted institution-wide.
   • Solved critical enrollment bottlenecks by implementing a Redis-backed queue to process thousands of concurrent student requests.
   • Designed a generic repository layer and custom ORM using Java Reflection, cutting boilerplate by 40%.
   • Managed complex institutional business rules with Oracle PL/SQL.
   • Java
   • Spring Boot
   • Oracle DB
   • PL/SQL
   • Redis
   • Design Patterns

3. Software Developer · M. Dias Branco

   jan/2007 — jun/2012

   Latin America's largest food manufacturer

   • Developed ERP modules in Java for logistics and manufacturing.
   • Built a background job scheduler for asynchronous report generation.
   • Optimized tax calculation logic via PL/SQL, cutting processing time from 8 days to 2.
   • Java
   • Oracle EBS
   • PL/SQL
   • SQL
   • OO Design

02 / Stack

Technical stack

03 / Projects

Featured projects

Pinned repositories on my GitHub — from observability labs to a betting domain built with correctness as priority number one.

• TicketFlow

  Simulated ticketing platform used as an observability and resilience lab: an Express monolith and the same journey rewritten as microservices, with distributed tracing (Jaeger/OpenTelemetry), metrics via Prometheus/Grafana, and incident runbooks.

  • TypeScript
  • Express
  • OpenTelemetry
  • Prometheus
  • Grafana
  View repository→

• Betting Platform

  Foundational phase

  Operational core of a real-money betting platform — accounts, wallets, markets, odds, and settlement — built from the first commit with a focus on correctness, auditability, and safe concurrency. Structured as a poly-repo: this repository holds local infrastructure, CI/CD, and architecture docs, while the actual Rails application lives in the backend submodule, versioned independently. A direct evolution of what was learned building janza-bet, currently in its foundational phase: pipeline, containers, and quality gates already running ahead of the betting domain itself.

  • Rails 8 (API-only)
  • Ruby
  • PostgreSQL
  • Solid Queue/Cache/Cable
  • Docker
  • Brakeman/RuboCop
  View repository→backend (Rails API)→

• Janza Bet

  Bankroll manager for sports betting built in Rails 8: accounts ('books'), bets, deposits/withdrawals, and daily balances, with a cumulative profit chart. First end-to-end Rails product — authentication, tests (RSpec), and Kamal deploy — that laid the groundwork for Betting Platform.

  • Ruby on Rails
  • Hotwire
  • MySQL
  • TailwindCSS
  View repository→

• Backend Journey

  A structured 12-month path toward senior/staff backend engineering — publicly versioned as a study journal: observability, reliability, database performance, race conditions, and event-driven architecture.

  • Markdown
  • Structured study
  • TicketFlow as hands-on project
  View repository→

04 / Now

What I'm studying or building right now.

• ›

  Working through a self-directed 12-month path toward staff engineer — currently in the Reliability Engineering module. [backend-journey]

• ›

  Evolving TicketFlow as a hands-on observability lab: distributed tracing, metrics, and alerting. [ticketflow]

• ›

  Building the Betting Platform in Rails with correctness and safe concurrency as priorities from the first commit, applying what matured in janza-bet. [betting-platform]

05 / Contact

Contact

Open to talk about distributed systems, backend architecture, or opportunities involving real scale and concurrency.