How a dev from Brazil started getting paid in dollars
I was born in the interior of Mato Grosso, Brazil, into a humble family. Today I'm a tech lead at a US company and I get paid in dollars. I've never left Brazil. I live in Nova Lima, Minas Gerais, and I work for people I've never met in person.
It wasn't luck. It wasn't a foreign degree. It wasn't being born in the right place. It was something else. And that something else is exactly what nobody really tells you.
The global market doesn't ask how long you've been around
It asks one thing. Can you solve the problem?
The American recruiter doesn't care how many years are on your résumé. Doesn't care about your university. Doesn't care where you live. They care about one thing: do you deliver real value or not?
That changes the game for a Brazilian dev. Because the bar stops being where you were born and becomes what you can build. And building has no zip code.
I saw it firsthand. I started coding at 11 because of a game. I wanted to understand what was happening underneath. I opened the source, stood up a server by hand, broke everything, fixed it, broke it again. Nobody paid me to do that. I did it because it became a way of life, not a way to make money.
Years later I found out that's exactly the kind of obsession the global market pays a premium for. Not the diploma. The ability to take an ugly problem and solve it.
What actually opened the door
Depth.
Not memorizing frameworks. Not collecting courses. Not knowing the fancy name for every little thing. Understanding what happens behind the scenes, at the level where the problem actually lives.
Because the shallow dev solves the easy case. Anyone solves the easy case — including an AI in a ten-second prompt. What pays in dollars is the hard case. The one nobody understands, the one that's in production, that's costing the company money right now, that the whole team already tried and got stuck on.
When you understand the mechanism, you solve what the next person can't. And that's when dollars stop being a dream and become a consequence. Not the goal. A consequence.
I built this slowly. I co-founded a community of 2,000 people in the interior of Brazil. I gave talks in city after city. At one event I packed a room with more than 500 devs, sponsored by Google. I helped friends switch careers, mentored a lot of people. Every time I taught, I understood twice as much. Whoever teaches learns double — it's real.
It wasn't a shortcut. It was layer on layer of actually wanting to understand. And that's what holds you up on a global team when everything breaks at 3pm and everyone turns to look at you.
AI accelerates mastery, it doesn't replace it
Now there's the 2026 trick. AI.
And here's where most people get it badly wrong. They use AI to skip the part where you understand. Ask for the answer, copy, paste, move on. It works until the day it breaks — and when it breaks, they don't even know where to start, because they never understood what was going on.
I use AI all day. I run multiple agents in parallel while I think about what matters. But I use it to master things faster, not to fake that I've mastered them.
The practical difference? Every time AI hands me something, I ask for the why. The reasoning behind each decision. Two wins right away. The AI itself thinks harder before answering, because it knows it'll have to justify itself. And I see the reasoning, so I fix things for real instead of guessing.
That's the difference between pushing a button and understanding what's happening underneath. Whoever just pushes buttons becomes a commodity. Whoever understands becomes indispensable. And indispensable is what dollars pay for.
AI doesn't drop you into the global market. It gets you there in two years instead of eight. But only if you use it to go deeper, not to dodge the work.
English is a toll, not a wall
That leaves one last excuse. English.
I'll be honest. You don't need to sound like a native. You don't need a pretty accent. You don't need three years of classes before you even try.
You need to communicate well enough to unlock the technical conversation. Read the docs, write a clear PR, explain a decision on a call without freezing. That's a toll. You pay it once at the entrance and you keep going. It's not a wall that blocks you forever.
And here's the best part. English gets built through use, not in an empty classroom. You get better by coding, reading open source issues, replying to people on GitHub. I never left Brazil and I built mine entirely that way — the hard way, by doing.
The wall that holds you back is almost never technical. It's mental. It's the voice that says "someone from Brazil doesn't make it out there." I made it. From the interior of Mato Grosso, without ever boarding a plane out of the country, getting paid in dollars.
If I made it, the problem was never where you were born. It's the depth you refuse to build.
follow me and I'll break down every step of this.