Flowzao
Careers

Work at Flowzao

We are engineers, not vibe coders. If you care about craft, architecture, and building software that lasts, keep reading.

Flowzao is a small team between Porto and Maputo. We work remotely, deploy to production every day, and hold ourselves to a high standard of engineering quality.

We are not looking for people who follow tutorials. We are looking for people who understand systems, who think about trade-offs, and who take pride in writing code that other engineers enjoy reading.

There are no formal openings listed here. We hire people, not roles. If something on this page resonates with you, get in touch.

Engineering

Engineering at Flowzao

Our engineering perspective is fundamentally different from what you see in most startups today. We do not chase trends. We do not rewrite the codebase every six months. We invest in architecture that lets us move fast for years, not just weeks.

Every line of code we write has a reason. Every abstraction earns its place. We use domain-driven design and hexagonal architecture not because they are fashionable, but because they produce systems that are testable, maintainable, and adaptable to changing requirements.

We believe artificial intelligence is transforming software development, and we embrace it fully. But we embrace it as engineers, not as passengers. AI is a tool in our process, not a replacement for thinking. The engineer remains at the center of every decision.

Methodology

Tree Programming

We developed our own methodology called Tree Programming. It is our evolution of pair programming for the AI era.

In traditional pair programming, two developers work together at one workstation. One writes code, the other reviews in real time. The idea is sound: two minds produce better results than one.

Tree Programming extends this to three actors: the engineer, the AI assistant, and a reviewer. The engineer drives the architecture and design decisions. The AI accelerates implementation, handles repetitive patterns, and catches errors. The reviewer provides the critical perspective that neither the engineer nor the AI can offer alone.

The result is software that is written faster, reviewed more thoroughly, and designed with more intention. The AI handles the volume. The engineer handles the direction. The reviewer handles the quality gate.

This is not about using AI to write code faster. It is about using AI to build better software, with humans firmly in control of every architectural and design decision.

Engineer

Architecture and direction

AI Assistant

Implementation velocity

Reviewer

Quality assurance

Culture

How we operate

01

Ship daily, iterate weekly

We deploy to production every single day. Not because we rush, but because our architecture and testing give us the confidence to do so. Small, frequent changes reduce risk and keep momentum.

02

Writing over meetings

We write short documents to align on direction, then we build. No daily standups. No two-hour planning sessions. If something needs discussion, we discuss it. Otherwise, we work.

03

Own your domain

Every engineer owns a part of the system. You make the architectural decisions for your domain. You deploy your code. You are responsible for its quality in production.

04

Remote with intention

We are remote-first across two continents. This works because we communicate clearly in writing, trust each other to deliver, and respect each other's time and timezone.

Interested?

Send us a short email about yourself. Tell us what you have built and what excites you about how we work. No CV templates. No cover letters. Just be direct.

careers@flowzao.com