Senior software engineer · São Paulo, Brazil · Works in English
Heavy software, running on light hardware
5+ years shipping production software · Software engineer at Conceptu · Technical leadership
I build web and mobile products end to end, from architecture to deploy, with a focus on performance on real devices. I take part in architecture decisions, review PRs and mentor the engineers around me.
Most software fails long before the code does. It fails at the decision.
So I work the other way around. The riskiest assumption gets built first, in week one, while changing your mind is still cheap. Everything after that is craft.
Focus: Where I go deep
Models that run where the user already is
Detection and language models executed on the device through WebAssembly, ONNX Runtime and TensorFlow.js. No server round-trip, no data leaving the device, and a memory budget that does not negotiate.
Performance on hardware nobody would choose
Profiling and cutting until React and React Native apps stay responsive on low-end devices. Budgets are measured on the real device, not assumed on a laptop.
Architecture a team can keep shipping on
Trade-offs written down before the code, reviews that teach instead of gatekeep, and CI/CD boring enough that nobody thinks about it.
Selected work
Brazilian Election Polls Tracker 2010–2026
Interactive dashboard that collects 1,370 opinion polls from 52 pollsters with a Python web crawler and shows how vote intentions changed in every Brazilian election from 2010 to 2026.
Python · Web Scraping · BeautifulSoup · Pandas · D3.js · JavaScript · HTML · CSS
Code Forge RPG
An RPG adventure where you forge your skills in Python, TypeScript, and C++ through quests and challenges, featuring an innovative lesson checker running 100% on the front-end with WebAssembly.
reat · wasm · python
Trinta Outubros: Halloween 30th Birthday Invitation
An interactive, horror-movie-themed party invitation built for guests of all ages. It has a collaborative playlist, a costume picker and an add-to-calendar button.
React · TypeScript · Vite · Motion · Firebase Firestore · iTunes Search API · Storybook · Vitest · Playwright · CSS Modules
RK Barbearia
Overview A custom-built scheduling and management platform for barbershops. Moving away from rigid, off-the-shelf solutions, the system offers complete real-time autonomy to clients, while providing the owner with a robust administrative dashboard for operational and financial control.
React 19 · TypeScript · Firebase (Firestore & Auth) · Styled Components · Vite · Date-fns · Lucide React · React Hot Toast · Vite PWA
Inkflow
InkFlow is a minimalist, local-first, infinite-canvas application designed for deep work and creative thinking. It's built to get you out of the "analysis paralysis" of traditional todo lists and into a state of flow.
wasm · c++ · y.js · webrtc
PRINCESS QUEEN TO THE RESCUE
This game was developed by three friends for our first game jam, created in Godot with visuals and gameplay inspired by the NES. It wasn't perfect, but we delivered our best within the deadline and learned a lot in the process. It's a retro platformer focused on precision, simple challenges, and 8-bit aesthetics.
godot
Zelo Beta
Application for caregiver management still under development. Allows adding and removing caregivers, scheduling shifts, generating schedules, and accessing a patient by code. Developed with React, TypeScript, Styled Components, i18n (pt/en), and Firebase for testing.
react · firebase · i18n
Controle Bolso
Your personal financial assistant focused on accessibility. Organize your finances with intuitive graphs and detailed analysis, all powered by the robust Firebase back-end.
react · firebase
Engineering Journal
Managing Multiple Git Accounts (Work and Personal)
· 4 min read
Every developer who has ever juggled a personal project, a job, and maybe a freelance project knows the pain: the accidental `git commit` with the wrong email. Using different credentials for each "identity" can be a hassle, but Git offers an elegant and automatic solution.
How I work: On a team
Before the code — Write the decision down
The constraint, the options and why one won. A one-page design note beats a long meeting, and it is still there when someone asks why six months later.
First week — Build the riskiest part first
Whatever could sink the feature gets a prototype and a benchmark before anything comfortable does. If it cannot work, the team learns that while it is still cheap.
Always — Leave the codebase easier to change
Tests where a break would hurt, PR feedback that explains the why, and documentation the next engineer actually reads.
Hiring for the hard part?
Email is the fastest way to reach me, and every message gets a reply.