I grew up in Santa Catarina, in the south of Brazil. I studied there, did my research there and got good at my job there. Then I moved to Geneva, later to Barcelona, and was bad at a lot of things again. Looking back, that was the most useful part of moving.
Most people reading this won't move country, and they shouldn't need to. Moving makes one mechanism impossible to ignore, and you can trigger that mechanism on purpose without a plane ticket.
The competence trap
It goes like this. You join an environment and you're bad at it. You learn fast, because everything is new and the feedback never stops. A few years later you know the systems, the people, the unwritten rules and which meetings matter, and you're effective.
By then your learning rate has dropped, because the environment has stopped asking you new questions. You still work hard, mostly on variations of problems you've already solved.
From the inside this feels great. Competence is pleasant, and so is being the person who knows how the thing works. Nothing tells you that you've stopped growing, because the local indicators (output, reputation, how often people come to you for help) all point up.
You can work hard for years in a place that has stopped surprising you.
What a new environment resets
A new environment shows you which of your beliefs were defaults rather than facts.
Engineering culture is a good example, because we like to think it's universal, and it isn't. Places differ on how much context gets written down and how much is assumed, on whether people disagree directly in the room or settle it afterwards, and on what "done" means: merged, deployed, adopted or forgotten. They differ on how much of a decision has to be documented before you can act on it, and on whether being late is a scheduling detail or a sign of how much you respect the other person.
None of this is in an onboarding document. You learn it by getting it wrong, which is uncomfortable in a particular way: the technical work is fine, and what you're failing at is the part everyone else finds obvious.
I'd also be wary of treating "Europe" as one culture. Geneva and Barcelona are both European cities, and they run on different assumptions about time, directness and how work fits into a life. Moving between them was its own adjustment, smaller than the first one and still real. Whatever you generalise in one place is a hypothesis in the next.
Working in a language you half speak
The most useful discomfort I found was linguistic. My Portuguese is native and my English is proficient. My French and Spanish are basic.
In your own language you can be precise, funny and persuasive, and you can soften a hard message. In a language you half speak you're approximate. You say the second-best version of your thought because the best one is out of reach, and for a while you're the slowest person in the room.
Most senior people never get that experience, and it teaches you a lot. You find out what colleagues working outside their first language deal with every day. You also write more clearly, because charm can no longer carry an unclear argument and you can't hide behind fluency. The idea has to hold up by itself.
Being visibly bad at something for a while is how this kind of growth happens. If nothing you're doing right now makes you feel a little unqualified, you're consolidating what you already know.
What transfers and what doesn't
Technical skill transfers immediately. Python is Python, and a distributed system behaves the same way in Zurich as in Joinville. Nobody has to relearn how a database index works because they crossed a border.
Social capital doesn't transfer at all. The credibility you spent years building, where people know that when you call something risky it is risky, stays behind. You arrive with your skills intact and your reputation at zero, and you rebuild it while also being less articulate than usual.
That's humbling, and I think it's the most useful part. You have to earn credibility on current evidence instead of history. You also learn first-hand what it's like to be the newcomer, and it changes how you treat the next one who arrives.
How to do this without moving country
Relocating is one way to force the reset. It's expensive and disruptive, and there are other ways. They all come down to putting yourself somewhere your existing competence doesn't cover:
- Change the domain before you change the stack. Going from e-commerce to logistics to travel teaches you far more than a new framework in a domain you already understand, because the hard part of software is rarely the software.
- Take the role you're not obviously qualified for, the one where you'll be the least experienced person in the discussion for the first six months.
- Learn something publicly, and badly: a language, an instrument, a discipline outside engineering. Pick something where your professional identity can't protect you.
- Work with people who don't share your starting assumptions. That's a different group from the people who disagree with your conclusions.
The uncomfortable part
None of this feels clean while it's happening. Being a beginner again in your thirties, in a language you don't fully control, while people still expect senior work from you, means months of working below the standard you hold yourself to. At the time it feels like being worse at your job.
You pay that price up front, which is why most people decline to pay it. The alternative is a career that gets more comfortable and less interesting every year, and over a whole career I think that costs more.