I build the whole thing, not just the part that's fun
I design and ship full stack products end to end — from the first Figma frame to the production pipeline that keeps it online. Four years across enterprise apps, real-time platforms, and cloud infrastructure.
From chemistry lab to production deploys
I studied chemistry at the Federal Institute of Rio de Janeiro. That sounds like a detour, and it was — but it left me with a habit that has been more useful than any framework: form a hypothesis, measure it, and don't trust a result you haven't reproduced.
I started building for the web in 2021 at Trivod, delivering applications end to end inside a Scrum team and getting my first taste of distributed systems through RabbitMQ-based microservices. At Juicy Space I went deeper on the frontend: real-time features over WebSockets, performance budgets, bundle analysis, and automated testing as a default rather than an afterthought.
Since 2024 I've been at Mainnet Design, where the role expanded past writing code. I run requirements gathering with stakeholders, define timelines, and mentor junior and mid-level developers — while still shipping pixel-perfect interfaces from Figma, wiring REST, GraphQL, and gRPC integrations, and owning the AWS, Google Cloud, and Vercel infrastructure it all runs on.
The through-line is ownership. I'd rather understand the whole system — the data model, the interface, the pipeline, the monitoring — than be excellent at one slice and helpless at the boundaries.
Based in
Rio de Janeiro, Brazil
Working with distributed teams across timezones.
Education
Chemistry
Federal Institute of Rio de Janeiro (IFRJ)
Jul 2019 – Dec 2022
A scientific background that shaped how I approach engineering: hypothesis, measurement, iteration.
Languages
0+
Years shipping products
0
Companies
0
Documented case studies
0
Languages spoken
Principles I actually hold to
Not aspirational poster material — these are the four things that most reliably decide whether a project goes well.
Own the whole outcome
Requirements, architecture, UI, infra, monitoring. I don't hand off half a product and call it done.
Pixel-perfect is a baseline
If it left Figma at 16px with a 24px line-height, it ships that way. Designers should recognise their work.
Boring infrastructure, exciting products
Predictable pipelines, clean environments, and observable systems buy the freedom to move fast on the fun parts.
Teach while you build
Mentoring juniors and mid-levels compounds. Code review is the cheapest architecture lesson there is.
Four years, three teams, one throughline
Every role added a layer: shipping features, then owning systems, then leading the people who build them. Click any role to expand the detail.
What I did
- Led requirements gathering and timeline definition for new features across enterprise applications.
- Ran technical meetings with stakeholders to align feedback and adjust development strategy.
- Delegated tasks and mentored junior and mid-level developers, raising code quality and architectural standards.
- Built pixel-perfect interfaces from Figma with high fidelity to the design spec.
- Implemented secure auth with JWT, OAuth 2.0, and external identity provider integration.
- Integrated REST, GraphQL, and gRPC APIs to connect heterogeneous systems.
- Structured and managed SQL and NoSQL databases per project requirements.
- Configured DNS, managed Production/Staging/QA/Dev environments, and automated CI/CD pipelines.
- Provisioned and optimised cloud infrastructure on AWS, Google Cloud, and Vercel.
- Monitored servers and databases proactively for availability, performance, and stability.
What I did
- Developed full stack web applications with React, Next.js, TypeScript, Node.js, and SQL/NoSQL databases.
- Implemented real-time communication over WebSockets for chat, notifications, and live updates.
- Optimised performance through bundle analysis, code splitting, and lazy loading.
- Set up automated testing with Jest, Vitest, and Testing Library to protect coverage and quality.
What I did
- Built full stack applications from conception to deployment, with technical documentation and tests.
- Worked in Scrum: sprint planning, dailies, reviews, and retrospectives.
- Implemented microservice architectures with asynchronous communication via RabbitMQ.
- Collaborated directly with clients and stakeholders on requirements and expectations.
Started building for the web in 2021 — after a chemistry degree that taught me to test before I trust.
A process built to survive contact with reality
Most projects don't fail on syntax. They fail on unclear scope, a data model that couldn't bend, or a deploy nobody could reproduce. This is how I avoid those.
Understand before building
I start with the people who will use the thing. Requirements sessions, stakeholder interviews, and a written scope that everyone agrees on before a line of code exists.
- Stakeholder discovery sessions
- Success criteria written down
- Scope and timeline agreed upfront
Design the system, then the screen
Data model first, because that is what you cannot cheaply change later. Then architecture, then the interface — built from the Figma file at full fidelity.
- Data modelling and schema design
- Architecture and integration boundaries
- Pixel-perfect Figma implementation
Build in reviewable slices
Small, shippable increments with tests where they matter. Code review is where quality is actually enforced, so I treat it as a first-class part of the work.
- Vertical slices, not big-bang branches
- Automated tests on critical paths
- Review culture and shared standards
Ship it and keep it alive
Environments, pipelines, DNS, monitoring. A feature is not done when it merges, it is done when it runs reliably in production and someone would notice if it broke.
- CI/CD and multi-environment setup
- Monitoring and alerting
- Cost and performance tuning
The toolkit behind the work
Not a list of everything I've touched — these are the tools I reach for, grouped by the part of the product they solve.
Interfaces that feel fast and match the design down to the pixel.
Let's build something worth shipping
Available for freelance projects, full-time roles, and technical consulting. Tell me what you're building and I'll tell you honestly whether I'm the right person for it.
Based in Rio de Janeiro, Brazil · Working with teams in any timezone · Fluent in English and Portuguese