FullStack Engineer (Flutter + Backend) - LatAm only!

The ratio of frontend to backend will shift project to project. Some weeks you'll live in Flutter. Some weeks you'll live in Go. Most weeks you'll touch both. If that sounds energizing rather than exhausting, keep reading.

• Fluency with the widget tree model — you think in composition, understand when to use StatelessWidget vs. StatefulWidget vs. more advanced state solutions, and know how to keep rebuilds efficient

• Experience with state management patterns in Flutter (Riverpod, Bloc, Provider, or similar) — and the ability to articulate why you prefer what you prefer, not just follow a tutorial

• Understanding of platform channels and how to bridge to native iOS/Android code when Flutter's abstractions aren't enough

• Comfort with Dart as a language — async/await patterns, isolates, null safety, strong typing — not just "I can write Dart" but "I write idiomatic Dart"

• Experience with testing in Flutter — widget tests, integration tests, golden tests — and a practical sense of what's worth testing vs. what's ceremony

• Familiarity with CI/CD for mobile — build pipelines, code signing, distribution to TestFlight and Play Console, managing flavors/environments

• Understanding of Go's concurrency model — goroutines, channels, select statements, and the practical discipline of knowing when concurrency helps vs. when it introduces unnecessary complexity

• Experience designing and building APIs — clean endpoint design, versioning, error handling, and documentation that other engineers (including your frontend self) can actually use

• Comfort with Go's standard library and idioms — error handling patterns, interfaces, struct composition over inheritance, and writing code that looks like Go rather than Java-in-Go-syntax

• Familiarity with database interaction in Go — whether through an ORM or direct SQL with something like sqlx or pgx, you understand connection pooling, migrations, and query performance

• Experience with observability and operational concerns — structured logging, metrics, health checks, and writing services that are debuggable in production, not just functional in development

• Awareness of deployment and infrastructure patterns — containerization, CI/CD pipelines for backend services, environment configuration, and the basics of running services in cloud environments

• You've already worked across the full stack in previous roles and it's where you do your best work

• You've worked on teams where you were the person who could plug in wherever the team needed you most

• You're comfortable with ambiguity — you don't need a perfectly scoped ticket to be productive

• You have opinions about API design, data modeling, and where the boundary between frontend and backend should live

• You've owned features from the database schema through the API to the UI — and you enjoyed all three layers

• A frontend specialist who will tolerate backend work. We need someone who genuinely enjoys both sides.

• An engineer who needs to be told exactly what to do. We want someone who sees what needs to happen and makes it happen.

• Someone who views "full-stack" as a resume keyword rather than a working style.

We think about our team like a competitive soccer team — not a recreational one. Winning is not an individual sport, and we expect every player on this team to embrace that. There are four team-first behaviors we value and incentivize:

The Assist — You put the team's mission over personal credit. If passing the ball to a teammate means the team scores, you pass the ball. You won't always get your name on the goal, but the team knows what you did. We are looking for engineers who would rather ship the right outcome than claim the glory.

The Rotation — When a teammate moves out of position to make a play, you rotate to cover the gap. On an engineering team, this means if a teammate is heads-down on a critical deliverable, you pick up the work they can't get to. You don't wait to be asked. You see the open space and you fill it.

The Sacrifice — Sometimes the highest-value thing you can do is the unglamorous work — the migration nobody wants, the bug that's been lingering, the on-call escalation during your focus time. Low-performance teams let that work rot. We don't. We make room for sacrifice and we recognize it.

The Risky Gamble — We encourage smart risk-taking. If you see an opportunity to push the team's capabilities beyond where they've been, take the shot. We'd rather have an engineer who tries something ambitious and learns from a miss than one who plays it safe every time. We manage risk through planning and support — not by avoiding it.

These aren't just slogans. They shape how we plan, how we review work, and how we evaluate the people on this team. If you're the kind of engineer who is motivated by winning as a team, you'll fit right in. If you're looking for a place to pad a personal highlight reel, this isn't it.

We'll be direct about this: AI is becoming table stakes in software engineering, and we are leaning in — hard.

Every engineer on our team works hand-in-hand with AI tools as part of their daily workflow. We're not experimenting with AI. We're not "exploring the possibilities." We have invested in it, we use it every day, and we expect every engineer on this team to do the same.

We are a growth-minded organization. AI is a force multiplier for us — it magnifies the impact of every engineer on the team. We are not using AI to downsize. We're using it to build more, ship faster, and punch above our weight. The engineers who thrive here are the ones who see AI as a tool that makes them more dangerous, not a threat to their relevance.

If you're excited about what's happening in AI and you want to work on a team that embraces it rather than fears it, you'll feel at home. If you're waiting for AI to "blow over," this probably isn't the right fit.

This is a month-to-month contract. That said, we're not looking for a short-term gap fill — we have years of product work ahead and want someone who is interested in a long-term engagement. We are open to contract-to-hire for the right person.

If this sounds like the way you already work — or the way you've always wanted to work — we'd like to hear from you. Tell us about a time you played the midfielder role on a team. We don't need a cover letter. We need to know you've done this before and you want to do it again.