Ruby on Rails Engineer
I turn legacy codebases into clean, scalable systems — and ship new ones with Rails 8.
class LegacyMonolith < ApplicationService
def call
extract_service_objects
add_test_coverage # RSpec, first
ship_without_downtime
end
end
#=> onboarding: 2 weeks → 4 daysTools I reach for
Dots mark how deep I go — green is daily, amber is solid, gray is familiar.
Backend
Databases
Testing
Frontend
DevOps & Infra
Observability
Specialties
Where I create the most leverage on a Rails team.
Legacy Modernization
Decommissioning Rails 4.2 monoliths and introducing Interactors, Service Objects, and proper test coverage — without breaking production.
Onboarding: 2 weeks → 4 daysTest-Driven Development
RSpec before code. Every critical path covered. Reduced production bugs by 25% at Big Data Health by introducing TDD to a previously untested codebase.
25% fewer production bugsBackend API Design
RESTful APIs built for scale — clean separation of concerns, token-based auth, and optimized PostgreSQL queries serving 10,000+ users.
25% faster API response timeWhere I've shipped
Four years of Rails across healthcare, SaaS, and product studios — remote-first.
SaaS platform for employee performance management and team development. Working on modernization of legacy modules and backend reliability.
- Led the full decommissioning of the legacy goals module — removed orphaned routes, controllers, scripts, and DB artifacts while keeping CI and migration stability across all active tenants.
- Improved data reliability for HR decisions by fixing critical review/reporting inconsistencies (import duplication and identifier/job-role mismatches) affecting all tenants.
- Reduced feedback moderation false positives by ~35% by refactoring logic to token matching and adding batch retrieval to feedback pipelines.
- Accelerated investigation of unfamiliar legacy modules by ~40% by integrating Claude Code for legacy code analysis and automated test generation.
Ruby on RailsPostgreSQLRSpecGitHub ActionsSidekiqRedisLarge-scale public healthcare management platform with a multi-engine Rails architecture — surgery scheduling, inpatient admission, TISS billing, immunizations, and electronic health records.
Healthtech company. Led a Rails 4.2 legacy modernization initiative, introducing Interactors, Service Objects, and proper test coverage across critical business logic.
US-based product studio. Built and maintained scalable backend services in Ruby on Rails serving 10,000+ active users across multiple client products.
Developed and deployed internal systems in Ruby on Rails to support academic and administrative workflows for the institute.
Selected work
Production Rails — from a flagship SaaS to a fault-tolerant payments API.
BJJ Admin Core
Full back-office SaaS for martial arts academy management
Problem · BJJ academies lack affordable management software — most rely on spreadsheets and manual billing, leading to revenue leakage and admin overhead.
Solution · Built a full back-office SaaS with automated overdue billing via background jobs, LGPD-compliant digital health records, and a PWA-ready interface — owner and teacher roles with proper permission scoping.
- LGPD-compliant student registration with digital health records
- Automated overdue billing via Solid Queue background jobs
- Role-based access control (owner / teacher) with Pundit
- CI pipeline with RSpec, Brakeman, and RuboCop
- PWA-ready with offline support
- Dockerized and deployable via Kamal
Finance App
Real-time personal finance management with Rails 8 + Hotwire
Problem · Most finance apps are either too complex (heavy SPA) or too simple (no real-time feedback). This explores how Rails 8 + Hotwire can deliver a snappy, modern UX without a separate frontend.
Solution · Leveraged Turbo Frames for instant UI updates, Stimulus for lightweight interactivity, and custom category color-coding — with secure Devise auth and Docker-ready deployment via Kamal.
Payment System API
Multi-gateway payment API with automatic fallback
Problem · Single payment gateway integrations create a reliability risk — if the provider goes down, transactions fail entirely.
Solution · Implemented a dual-gateway architecture with automatic fallback, JWT-based auth, role-based access control, and webhook handling. Frontend built in React with real-time status updates.
Who I am
I'm a Ruby on Rails engineer based in Brazil (UTC-3), working remotely with international teams. Over the past 4 years I've shipped production backends across healthcare, SaaS, and fintech.
I care about clean, well-tested code — turning tangled legacy systems into something maintainable. I write tests first, keep business logic out of controllers, and ship with confidence on Rails 8 + Hotwire.
- 4+
- Years of experience
- 6+
- Production Rails apps
- 2w → 4d
- Fastest onboarding cut
- UTC-3
- Timezone
Let's work together
Open to remote Rails roles. Drop a message or book a call.