Senior Software Engineer · Full-Stack Developer
Seven years building Ruby on Rails products from insurance, marketplaces and vacation rentals across the full surface of a feature: the API behind it, the interface on top, the mobile client where there is one, and the metrics that show how it behaved once it shipped. Four of those years were spent working inside other teams' codebases, which is a quick way to learn what makes software cheap or expensive to change.
Taking a feature from the product conversation through to its behavior in production — backend, interface, and the mobile client. Role-based access control, dynamic dashboard components, and customer-facing work on marketplace, insurance and rental platforms.
discovery → backend → UI → mobile → production
Contributing to the calls that are expensive to reverse: service boundaries in a twelve-service architecture, when a workload belongs in a different data store, and the long-range engineering decisions a distributed team has to live with afterwards.
service boundaries · data modeling · trade-off analysis
Seven years with product managers and designers, four of them in a consulting setting where the job is to understand someone else's product quickly, argue for the right technical shape, and stay accountable for delivery.
PM & design collaboration · technical planning · code review
REST API design and backend services across microservice architectures communicating over AWS infrastructure, delivered with test coverage.
REST · microservices · AWS · Sidekiq
Logging, monitoring and metrics that shorten time-to-detection on production issues, plus the newer LLM-shaped version of the same problem: tracking token usage, latency and cost per request.
metrics · LLM cost tracking
Keeping product velocity from decaying. Framework and dependency currency, clearing known CVEs, and the performance work that stops a codebase becoming the reason a feature takes three weeks instead of three days — the subject of most of my published writing.
upgrades · CVE triage · performance · dependency health
Published on the FastRuby.io engineering blog, 2022–2026. Posts marked Ruby Weekly were picked up by the newsletter — the badge links to the issue. Grouped by the kind of judgment each piece calls for rather than by technology, because that is the part that transfers.
Weighing a change honestly before committing to it — including the ones that turn out not to be worth doing.
Turning technical risk into terms someone outside engineering can act on.
Putting a number on a decision — latency, tokens, bytes shipped, allocations.
The failures that give you nothing to go on, and how to corner them anyway.
Reading what is coming in Ruby and Rails early enough to plan around it.
Compatibility tables Ruby developers still link to when planning an upgrade.
Most recent first
OmbuLabs / FastRuby.io · Remote (Philadelphia, USA)
Youse Seguros · São Paulo, Brazil
TemporadaLivre · Remote, Brazil
Zimobi · Remote, Brazil
Highlighted = daily
Le Wagon
500-hour intensive program in Ruby on Rails, React, and full-stack fundamentals.
Federal University of Paraíba (UFPB)
Portuguese native. English fluent — seven years working daily with US-based teams.