I've been navigating American enterprise tech as an immigrant for over 12 years. Here are the things I wish someone had told me.
Twelve years navigating American enterprise technology as an immigrant reveals patterns that aren't written about honestly: the code-switching required at different levels of seniority, the immigration anxiety that runs as a constant background process in every career decision, the things Indian professionals specifically tend to misread about American executive culture, and what carries over from an Indian professional background that actually creates advantages in the right context.
When I started at Microsoft in 2014, I had an MBA from a good school and several years of professional experience. I also had a working assumption that I understood American corporate culture well enough to navigate it. That assumption was partly right and partly expensive.
This is a piece about the partly expensive part.
I want to write it honestly, which means it's going to include things that are uncomfortable to say directly about cultural patterns. I'm writing from my own experience as someone who grew up and built a career in India before moving to America at 31. The patterns I'm describing are not universal. But they're common enough that I wish someone had named them clearly before I had to learn them by experience.
American professional culture rewards a specific kind of visibility that doesn't come naturally to many people from South Asian professional backgrounds. The reward system is built around being seen to have ideas, not just having them. Speaking in meetings, putting your name on things, making your contributions legible to the people above you in the organisation — these are not incidental to advancement, they are the mechanism of advancement.
In many Indian professional contexts — particularly in large organisations — there's a deference structure around seniority that makes this kind of self-promotion feel inappropriate. You do good work. Your manager sees it. Your manager advocates for you. The chain of recognition runs through the hierarchy rather than around it.
American corporate culture, especially in technology, is flatter and louder. Your manager may or may not advocate for you. Your skip-level may or may not know who you are. The people making decisions about your career may have very limited information about your contributions unless you have actively created that information.
I learned this the hard way in my first eighteen months at Microsoft. I was working hard, delivering well, and waiting for that work to be noticed through the normal channels. It was being noticed — but by the people immediately adjacent to me, not by the people whose decisions would affect my trajectory. The fix was uncomfortable: I had to learn to make my work visible in ways that felt like self-promotion and were, in fact, self-promotion. The distinction I eventually made peace with was that in a large organisation with limited information flow, making your work visible is not bragging. It's how the organisation learns what resources it has.
There's a version of "Indian professional communication style" that American colleagues sometimes read as evasive or non-committal. This is a misread, but it's a common one and it has real consequences.
The pattern: a question is asked that has an uncertain or complicated answer. The honest response acknowledges the uncertainty and explains the complication. This reads, to many American colleagues, as hedging — as not knowing the answer or not being willing to commit to a position.
The American professional norm is to state a clear position, even on uncertain things, and then defend it. "I think we should do X because Y. The risks are Z and here's how I'd manage them." The same intellectual content, packaged as a clear recommendation with acknowledged uncertainty, lands as confidence rather than evasion.
Neither communication norm is better in any objective sense. But in American corporate settings, the clear-recommendation style is the dominant code, and not speaking it fluently creates a perception gap between your actual capability and how your capability is read.
The calibration I've landed on: lead with the recommendation, follow with the uncertainty. Not "there are many factors to consider here and it's a complicated question" — that's true but it doesn't land well. "I think we should do X. Here's why, and here are the main things that could make me wrong about that." That's the same intellectual honesty in a different order.
I want to name something that immigrant professionals almost never say directly in professional contexts: immigration status runs as a constant background process in every career decision.
For most of my time in America, I've been on employment-based visas. This creates a specific kind of career risk that doesn't exist for citizens or permanent residents: your legal status is tied to your employment. Changing jobs requires paperwork. Taking a startup risk requires careful legal analysis. Layoffs are not just financially disruptive — they create a ticking clock on status. The green card process, for Indian nationals, involves timelines measured in decades rather than years.
I don't say this to generate sympathy. I say it because the constraint is real and shapes decisions that look, from the outside, like ordinary career choices. The immigrant professional who seems risk-averse about job changes may be managing a legal exposure that their colleagues don't know exists. The one who stays in a role longer than seems optimal may be in the middle of a multi-year immigration process that would reset if they moved.
Understanding this — whether you are an immigrant navigating it or a colleague or manager of someone who is — makes better sense of behaviours that otherwise look puzzling.
Not everything about building a career in India translates poorly to American contexts. Some things carry over with advantage.
The resourcefulness. Building a business in Delhi with limited resources and uncertain infrastructure develops a problem-solving orientation that shows up differently in well-resourced corporate environments. I have a strong bias toward finding the version of the solution that works with what exists rather than waiting for ideal conditions. This is useful in large organisations that have more resources than they have clarity about how to use them.
The relationship orientation. Indian professional culture invests heavily in relationships as the foundation for getting things done. This maps surprisingly well to how large American corporations actually work as opposed to how they're supposed to work. The official process matters less than who you know, who trusts you, and who you've built goodwill with over time. The relationship infrastructure I was accustomed to building was more valuable in corporate America than I expected it to be.
"The immigrant professional's most transferable skill is navigating ambiguity in systems that aren't designed for you. American corporate culture, whatever else it is, rewards that."
Seattle has been home for several years now. I live here with my wife and son, I ride my bike on trails that still surprise me with how beautiful they are, and I navigate a career in enterprise technology that has turned out to be, among other things, a continuous education in how different the same professional world can look from different vantage points.
The things I learned the hard way are the ones I've tried to write down here. I'd rather someone else find them useful than watch them learn the same lessons by experience.
Kuber Sharma leads platform product marketing at UiPath. He writes Positioned, a newsletter on AI-era product marketing strategy for enterprise PMMs.