My focus on global software development has enabled me to see amazing places and meet interesting people. I blogged about many times about traveling to Costa Rica as part of my work. I thought I would provide insights I have learned for how to steer your career toward a life of exotic travel combined with world wide software development.
Step 1: Travel for business and pleasure
I have always tried to include a day or two at the tail end of my trips to see some place new. This didn’t start out as a business goal. It was more of a personal goal. However, I soon realized that my global business interactions were enhanced by my knowledge of different countries. Indian company leaders always smile when I tell them I spent a long weekend in Goa, a place on the coast with very little technology industry.
When you travel for work, you of course have to get the job done. But there is no reason why you can’t see a bit of the world after that. International organizations can tell the difference between somebody culturally focussed and someone who is not. The opportunities and rewarding experiences will come to those who are interested in more than just the job. As a member of the global community, you will also add a bit more to the discussion.
Step 2: Work in a foreign country
I spent time working in Germany and France on localized personal finance software. Once you get over the challenge of figuring out how to buy milk (true story, this is a challenge), and you start to grow accustomed to your surroundings, you begin to develop those second level observational skills. You learn how to sense cultural differences and then how to navigate the challenges of people from vastly different backgrounds.
I was in a project discussion where the team told me they were uncomfortable with the schedule. Over and over again, I heard it was a cultural thing. Do you think managing teams to aggressive dates has anything to do with culture? Of course not. But something in the discussion was making them focus on cultural issues and not the schedule. I offered to wait quietly as they discussed the issue in their native language. I stayed with their metaphors instead of trying to introduce my own (“there is no red line” versus “we need to get on the same page”). And in the end, I respectfully pointed out on this issue we had to see ourselves as one team not different cultures. It worked for the most part.
The secondary skills you develop help you to blend in with the local culture and teach you how to include culture in the discussion. Working in foreign countries teaches you how to work through cultural differences.
Step 3: Build relationships not contacts
You meet someone on a trip. You talk about the technological landscape, your experiences and your companies. You exchange business cards. Is that a contact or a relationship? Well, ask yourself this. In the course of your interactions, did you ask any non-work related questions? Did you ask about how the person in front of you arrived at this point in time? How about asking about their recent travels or books they read?
The point here is simply that if you try to get to know the person, if you provide just a little more information about yourself, you will end up with a stronger connection than just another vcard in Outlook. And further down the road, when opportunities to work globally come up, the people who build relationships are more likely to get those opportunities.
Step 4: Take the right job even if you don’t travel
Here’s two projects for you. One is an established team that is a cash cow for the company. The second job is a new effort. Now, to be honest, earlier in your career you should take the first job! Strong experience open doors in all cases. But as your experience grows, sometimes it is better to move laterally or even take less responsibility if it provides you more opportunity to learn and more freedom to make choices. Hone your craft on big important projects. Then move on to projects that push you out of your comfort zone. You will spend a lot of time expanding your comfort zone when working globally.
Step 5: Work different jobs
I am primarily an engineering manager type (visions of Dilbert haunt my nights). But I also code side projects, write business requirements, publish, and test. My career goal to lead technology organizations compelled me to become experienced in all aspects of the organization. This is smart from a career perspective. Opportunities to present, to work globally, to be seen as a global expert will come to those people who have in fact become an expert. This applies whether you are a code jockey or a manager such as myself.
Good luck, now go see the world!
Posted by bbenedict