Skip to content
Available for remote roles · US

Flutter Engineer building production mobile apps.

Mobile · Dart · Clean Architecture · Design Systems

As a Flutter Engineer, I help product teams ship mobile apps that stay maintainable, with clean architecture, reusable design systems and a testing discipline built into the workflow.

GMT−3 · Open to relocation (US) Belo Horizonte, Brazil PT (native) · EN (working)
About

Mobile engineering with attention to detail.

I build with what teams need in mind as the codebase evolves, not just what looks good in the first sprint. Clear boundaries, feature-focused modularization, and tests that enable confident refactoring.

  • Flutter & Dart engineer with 5+ years building production mobile applications.
  • Focus on Clean Architecture, readable code and reusable design systems.
  • Strong culture of automated testing, unit tests are part of my definition of done.
  • Comfortable working independently or as part of product teams, collaborating with designers, product managers, and other engineers.
  • Async-first collaboration: solid PR descriptions and written docs as part of the delivery.
Stack

Tools I reach for.

Grouped by the problem they solve — not a loose logo grid.

Core

  • Flutter
  • Dart
  • Dart Workspaces

State & Architecture

  • MVVM
  • Clean Architecture
  • Cubit / Bloc
  • MobX
  • Feature-First

Quality

  • Unit tests
  • Widget tests
  • Mockito
  • Golden tests
  • CI/CD

Platform & Backend

  • Firebase
  • REST APIs
  • Flavors (dev/prod)
  • GitHub Actions
  • Google ML Kit

Design Systems

  • Figma → code
  • Design tokens
  • Reusable components
  • White label

Currently learning

  • Advanced testing
  • Performance profiling
  • Native platform channels
Experience

Where I've shipped.

A few years across product companies and consultancies. Focused on mobile since 2021; a prior background in infrastructure informs how I think about reliability and CI.

Mobile Software Engineer · CareOn BrasilFull-time

May 2026 — Present · Remote (Brazil)
  • Working on Flutter development for a healthcare product — feature-first modularization and shared UI components.
  • Introducing Cubit-based state management and a testing baseline for new features.

Mobile Software Engineer · DB (Consultancy) - PagareFull-time

Nov 2025 — May 2026 · Remote (Brazil)
  • Shipped Flutter features for a fintech client under a consultancy engagement.
  • Refactored legacy screens toward MVVM, unblocking parallel work between designers and engineers.

Mobile Software Engineer · FITecContract

Apr 2025 — Apr 2026 · Hybrid (Brazil)
  • Hourly consulting project conducted alongside a full-time role, with flexible scheduling to accommodate both engagements.
  • Built and hardened production Flutter modules; wrote unit tests as part of the definition of done.

Mobile Software Engineer · CMOS DrakeContract

May 2024 — Mar 2025 · Hybrid (Brazil)
  • Delivered Flutter features on an IoT-adjacent product with hardware integration constraints.
  • Helped set the branching, PR review and CI conventions still used by the team.

Mobile Software Engineer · Raro LabsFull-time

Sep 2021 — May 2024 · Remote (Brazil)
  • First full-time mobile role, moved from an infrastructure background into shipping production Flutter across client projects.
  • Owned features end-to-end: architecture, implementation, tests and release.
How I work

Engineering principles.

The short version of what shows up in my code reviews and design decisions.

01

Write for the next developer.

Boundaries and naming that hold up after the original author move out. Cleverness has an expiration date.

02

Tests are a design tool.

Coverage isn't the goal, testability is. If a class is hard to test, the design is telling you something.

03

Design systems > screens.

Build reusable components early. Consistency is cheaper to establish than to retrofit.

04

Async-first communication.

Write it down. A good PR description saves three meetings and lets remote teams move across timezones.

05

Ship, measure, then iterate.

Get real usage data early. What users actually do matters more than what we think they'll probably do.

06

Defer the reversible decisions.

Lock in what's hard to change, keep the rest cheap to swap. Architecture is about what you don't decide yet.

Contact

Let's build something worth shipping.

Open to remote opportunities and relocation to the US

Available for full-time or contract roles as a Flutter Engineer.
The best way to reach me is via LinkedIn or email.

Response time: < 1 business day GMT-3 · Open to relocation (US)