VP of Engineering / CTO-minded technologist. I build cloud platforms and engineering teams using the same principle: structure beats heroics.
I don't chase disruption — I believe it's what consistent, incremental work produces over time. Most of what's below is proof of that, not a pitch for it.
I architect cloud systems (mostly AWS) and lead the engineers who run them. In practice, that means:
- Turning legacy monoliths into resilient microservices — in stages, not big-bang rewrites
- Building delivery processes that don't depend on a few "hero" engineers to work
- Translating between executives, product, and engineering without losing precision on either side
- Helping teams adopt AI and GenAI where it actually moves the business needle, not where it sounds good in a deck
I've done this in startups, regulated industries (gaming, finance), and large-scale consulting engagements — including one of the biggest cloud migrations in Canada, for a company operating across multiple legal jurisdictions.
I ask more questions than I give orders. In a formal leadership-style assessment, my top style was Coaching, followed by Visionary — pace-setting and command-and-control came in dead last, and that's by design.
A few things I actually believe, not just say:
- Culture > Process > Tools. Get the culture wrong and nothing else holds.
- No delivery without a metric. If I can't measure it, I don't know if it worked.
- Peer review beats individual brilliance. More than one mind thinking always wins.
- Anti-fragile teams admit their weak spots instead of hiding them — that's where the real improvement happens.
I'm not trying to be a "guru" of anything. I'd rather be useful than quotable.
- 🔭 Leading engineering & delivery at Elevata — cloud-native and AI-oriented consulting
- 🧠 Studying Rust and advanced Kubernetes, daily, because skill stagnation is the actual risk in this field
- 🗣️ Occasionally writing on Medium — usually because something at work made me think, not because I scheduled a post
Cloud / Infra: AWS (Lambda, ECS/EKS, DynamoDB, RDS, SQS/SNS, Bedrock) · Terraform · Terragrunt · AWS CDK · Kubernetes Backend: Node.js / TypeScript (NestJS, Express) · Python · Go · PHP Data: PostgreSQL · MySQL · MongoDB · Cassandra · Elasticsearch/OpenSearch · Kafka (MSK) AI: RAG pipelines · Knowledge Bases · MCP servers · LLM integrations Frontend (when needed): React · React Native
If you want the long version of how I think, these are closer to it than any bullet list:
- Como reduzimos em 2/3 nossos custos apenas mudando nossa estratégia de uso do S3
- Uma abordagem financeira para tratar engenharia de software e débito técnico
- Vamos falar sobre cultura de qualidade de software e Code Review?
- Vamos falar sobre arquitetura ágil
- Como fiz para corrigir dados na casa dos 20000k de forma assíncrona com JS
If you're here for the resume version, that lives on LinkedIn. This page is closer to how I actually think.