Soft Skills That Matter Most for Indians Working in Multicultural Teams

My first week at a company in Seattle, I sat through a meeting where my manager asked the team for opinions on a new feature direction. Everyone around the table started talking. They disagreed with each other. They interrupted. Someone said, "I think that's wrong, and here's why." Another person pushed back on the VP's suggestion directly — to his face — and said the data didn't support it. And then they all went to lunch together like nothing had happened.

I sat through the entire meeting without saying a word. Not because I didn't have opinions. I had several. But I was waiting for the right moment. I was waiting to be asked. I was being respectful, or at least what I'd been taught was respectful — don't speak until spoken to, especially when you're the new person, especially when senior people are in the room, especially when you're not sure if your opinion is "right." By the time the meeting ended, every point I would have made had been made by someone else. And nobody even noticed I'd been silent.

That was the moment I realized that the soft skills I'd developed over twenty-some years of growing up in India and working in Indian companies were not just insufficient for this new environment — some of them were actively working against me. The things that made me a "good team member" back home were making me invisible here.

This article is about that adjustment. Not the technical skills, not the visa stuff, not the salary negotiation. The interpersonal, cultural, behavioral adjustments that nobody prepares you for and that end up mattering as much as — sometimes more than — your ability to write good code.

Assertiveness Is Not Aggression

This is the big one. This is the thing I see Indian professionals struggle with most in multicultural teams, and I include myself in that struggle because it took me years to get comfortable with it.

In most Indian work environments, there's a hierarchy. You defer to your manager. You defer to people with more experience. You don't challenge a decision made by someone senior to you, at least not publicly. If you disagree, you might mention it privately, or you might just accept it and move on. Being agreeable is valued. Being confrontational is not. This is deeply cultural — it connects to concepts of respect, seniority, and maintaining group harmony that are embedded in how most of us were raised.

In American (and more broadly Western) work culture, especially in tech, assertiveness is expected. Not aggression — there's a line, and crossing it makes you the "difficult" person. But stating your opinion clearly, disagreeing with your manager in a meeting, pushing back on a decision you think is wrong, saying "I don't think that will work and here's why" — these are considered normal professional behavior. More than normal — they're signs of engagement, critical thinking, and leadership potential.

When an Indian professional doesn't do these things, it doesn't read as "respectful" to American colleagues. It reads as "doesn't have opinions" or "doesn't care enough to contribute" or, worst of all, "isn't at the level to have opinions worth sharing." That's a devastating perception to have attached to you, and it happens quietly. Nobody tells you it's happening. You just don't get invited to the important meetings. You don't get asked to lead the next project. You get passed over for promotion and the feedback is vague — "needs to demonstrate more leadership" or "should increase their visibility."

How do you fix this? Practice. Start with low-stakes situations. In a team standup, instead of just giving your status update, add an opinion. "I think we should prioritize the database migration over the UI changes this sprint because of the deployment window." In a design review, point out a concern even if you're not sure. "I might be wrong about this, but won't this approach have latency issues at scale?" The qualifier ("I might be wrong") is actually a useful bridge — it lets you be assertive while still signaling humility, which makes the transition feel less jarring if you're not used to being direct.

Over time, you can drop the qualifiers. But at first, they're training wheels. Use them.

The Art of Small Talk (and Why It's Not Small)

I used to think small talk was a waste of time. "How was your weekend?" "Did you catch the game?" "Nice weather, huh?" Who cares? We're here to work. Let's talk about the code, the project, the deadline. Chitchat seemed inefficient, unnecessary, even slightly fake. Why are you asking me about my weekend when you don't actually care about my weekend?

What I didn't understand — and what took me an embarrassingly long time to figure out — is that small talk isn't about the content. It's about the connection. When your American colleague asks about your weekend, they're not looking for a detailed itinerary. They're establishing rapport. They're signaling "I see you as a person, not just a function." And when you respond with something human — "I tried this new restaurant in Bellevue, it was amazing" or "I spent the whole weekend trying to assemble IKEA furniture and I'm still not done" — you're building a relationship. That relationship, over time, translates into trust. And trust translates into collaboration, opportunities, and advocacy when promotions come around.

Indian professionals who skip small talk or treat it as an obligation rather than an opportunity miss out on something that's genuinely career-defining. The people who get the best projects, who get promoted, who get tapped for leadership roles — they're not always the best technical performers. They're often the people that others enjoy working with, feel connected to, and trust. Small talk is the gateway to that.

If you're not naturally good at small talk — and many engineers aren't, regardless of nationality — here are some concrete things that helped me. Keep up with one American sport at a surface level. You don't have to become an NFL fanatic, but knowing that the local team had a big game and being able to say "that fourth quarter was wild" gives you entry into a conversation that half your office is having on Monday morning. Follow a couple of popular shows or podcasts so you have something to reference. Ask people about their hobbies — most people love talking about themselves, and genuine curiosity goes a long way. And share something about yourself. One of the things I noticed is that many Indian professionals keep their personal lives very separate from work. Your American colleagues are sharing stories about their kids, their weekend hikes, their home renovation disasters. When you share nothing, you become a bit of a mystery — and not in a good way. In an interesting way. People don't know how to connect with someone who doesn't give them anything to connect with.

Communication Styles: Direct vs. Indirect

Indian communication tends to be indirect. If something is a problem, you hint at it rather than stating it bluntly. If you can't do something, you say "it will be difficult" rather than "no." If you're confused, you nod and figure it out later rather than admitting confusion in the moment. This indirectness is a cultural pattern rooted in saving face — both yours and the other person's.

In a multicultural team, indirectness causes real problems. I'll give you a specific example that I witnessed. An Indian engineer was asked by his manager if the feature would be ready by Friday. He said, "We'll try our best." In his mind, he was communicating that the deadline was very tight and he wasn't confident they could make it. In his manager's mind, she heard "yes, we'll get it done." Friday came, the feature wasn't ready, and the manager was frustrated because she felt blindsided. The engineer felt frustrated because he thought he'd communicated the risk. Neither was wrong — they were just operating with different communication protocols.

Direct communication means saying what you mean. "I don't think we'll make Friday. The testing alone will take until Thursday and we haven't started it. Can we push to Monday?" That feels uncomfortable if you're used to softer communication. It feels like you're admitting failure or being negative. But in a multicultural team, it's the only reliable way to ensure everyone is on the same page. And most managers — good ones, at least — prefer hearing bad news early and directly over hearing vague assurances that turn into missed deadlines.

There's a nuance here though. Being direct doesn't mean being blunt to the point of rudeness. "This code is terrible" is direct but unhelpful. "I have some concerns about this approach — specifically, I think the error handling in the payment flow could lead to data inconsistencies. Can we walk through it?" is direct and constructive. The skill is combining clarity with kindness. Say what you mean, but say it in a way that opens a conversation rather than shutting one down.

Presentation Skills: Stop Reading Slides

This one is specific and actionable. If you ever have to present to a team, a stakeholder group, or a leadership audience — and you will, if you advance in your career — you need to be able to present well. Not perfectly. Not like a TED speaker. But well enough that people listen and remember what you said.

The default Indian presentation style — and again, I'm generalizing from what I've observed — is to create dense slides full of text and then read them aloud. Or to create beautiful slides with charts and then explain every data point in exhaustive detail. Or to present in a monotone because you're nervous and you're focusing on the content rather than the delivery. None of these work in a multicultural environment where attention spans are short and expectations are high.

What works: fewer slides, more storytelling. Start with the punchline ("We reduced latency by 40% and here's how"), then walk through the journey. Use visuals instead of text. Make eye contact — actually look at the people in the room, not at your laptop. Vary your voice — louder for important points, quieter for details. Pause after key statements to let them land. And keep it short. Whatever amount of time you think you need, cut it by 30%. Nobody has ever complained that a presentation was too concise.

I struggled with this for years. What helped me was watching how senior leaders at my company presented. They didn't use scripts. They barely used slides. They told stories, made arguments, asked questions, and engaged the room. It looked effortless but it wasn't — it was practiced. I started practicing my presentations out loud, by myself, in a room. I recorded myself and cringed. I asked a colleague for feedback and cringed more. But it got better. And as it got better, I started getting more visibility, more opportunities to present, and more recognition. Presentation skills are a multiplier on everything else you do. Great work that nobody sees because you presented it poorly is effectively invisible work.

Feedback: Giving It, Getting It, and Not Taking It Personally

Feedback culture in India and feedback culture in the US are wildly different, and this mismatch causes more interpersonal friction than almost anything else I can think of.

In many Indian workplaces, feedback flows one way: from manager to employee. And even that feedback is often cushioned, indirect, or delivered through annual reviews rather than in real-time. You might work with someone for months and never tell them directly that their code reviews are too superficial, or that they talk over people in meetings, or that their documentation is consistently incomplete. You might think these things, but saying them feels confrontational, personal, or not your place.

In the US, and especially in tech companies, there's an expectation of regular, direct, peer-to-peer feedback. Your colleague might say to you after a meeting: "Hey, I noticed you didn't speak up when the PM changed the requirements. I think the team needs your perspective — can you try to jump in earlier next time?" That's not an attack. That's someone investing in your growth. But if you're not used to receiving feedback this way, it can feel like criticism, and the natural response is defensiveness.

Learning to receive feedback gracefully is a skill. When someone gives you feedback, the right response — even if you internally disagree — is "Thank you, I'll think about that." Not "But the reason I did that was..." Not silence and resentment. Not agreeing in the moment and then never changing anything. Actually sitting with the feedback, considering whether it's valid, and if it is, adjusting your behavior. And then circling back and saying "I tried what you suggested in yesterday's meeting. How did that land?"

The other side is learning to give feedback. This is where many Indian professionals really struggle, because giving direct feedback to a peer — or especially to someone senior — feels deeply uncomfortable. But it's expected, and not doing it is actually seen as a failure of teamwork. If you notice a colleague's code has a security vulnerability, you don't quietly fix it yourself. You tell them, clearly, so they learn and so the team improves. If your manager's meeting structure is ineffective, you bring it up. "I've noticed our sprint planning meetings run over every week. I think we could be more efficient if we... what do you think?"

Start with positive feedback if giving constructive feedback feels too hard at first. Tell a colleague when they do something well. "Your presentation to the leadership team was really clear. I especially liked how you framed the cost-benefit analysis." This builds the relationship so that when you eventually need to give harder feedback, there's a foundation of goodwill.

Saying No to Extra Work (Without Feeling Guilty)

There's a pattern I've seen so many times with Indian professionals on multicultural teams that I've started calling it the "yes spiral." It goes like this: you're assigned your sprint work. Then your manager asks if you can also look into a production bug. Sure, you can. Then a colleague from another team asks if you can help with a data migration. Sure, why not. Then the QA person asks if you can review the test cases because they're behind. Of course. And suddenly you're working twelve-hour days, your own work is falling behind, and you're stressed and exhausted, but you can't say no because saying no feels like letting people down, and letting people down feels like it puts your position at risk, and your position feels especially precarious because you're on a visa.

This pattern is amplified for Indian professionals because of the combination of cultural tendency toward accommodation and the real vulnerability of being on an employer-sponsored visa. But really: consistently saying yes to everything doesn't make people respect you. It makes them assume you have infinite capacity. And when you eventually can't deliver on everything you committed to, the perception isn't "wow, they took on too much." It's "they couldn't handle their work."

The solution isn't to become the person who says no to everything. The solution is to make saying no about prioritization rather than refusal. When someone asks you to take on something additional, the response is: "I can do that, but I'm currently working on X and Y. Which one should I deprioritize to make room for this?" This puts the decision back on the requester and makes your capacity constraints visible. It's not "no." It's "here are the tradeoffs." And it's a completely professional, expected response in the US workplace.

I wish someone had told me this in my first year. It would have saved me a lot of late nights and a lot of frustration.

Understanding Humor and Cultural References

This is one of those soft skills that people don't talk about because it feels trivial. But it's not. Humor is one of the primary ways that people bond in the workplace, and if you don't understand the references, you're left out of those bonding moments.

American workplace humor relies heavily on cultural references — TV shows (The Office is basically a shared cultural text for American white-collar workers), movies, sports, politics (tread carefully here), and memes. When someone makes a "that's what she said" joke or says a situation is "the Fyre Festival of project launches," they're using shorthand that connects through shared cultural knowledge.

You don't need to become an encyclopedia of American pop culture. But watching a few key shows (The Office, Parks and Recreation, maybe a couple of current popular series), following major news events, and understanding common cultural references will make you more fluent in the informal language of the workplace. This fluency matters for belonging, and belonging matters for advancement.

Your own cultural references are valuable too, by the way. Don't erase your identity. Sharing aspects of Indian culture — explaining what Diwali means, bringing in sweets during festivals, talking about cricket during the World Cup — enriches the team and makes you memorable in a positive way. The goal isn't to become American. The goal is to be culturally bilingual.

Email and Slack Etiquette That Actually Matters

I could write a whole separate article on this, but let me hit the key points because I've seen so many Indian professionals undermine their own credibility through small communication habits.

Don't start emails with "Dear Sir/Madam." Ever. Even if the recipient is a VP. "Hi [Name]" or just "[Name]," is standard. "Dear" signals that you're either writing to a customer service department or you're not familiar with American business communication norms.

Don't end messages with "Please do the needful." This phrase, while perfectly standard in Indian English, is one of the most commonly cited linguistic markers of Indian communication in American workplaces. Rightly or wrongly, it stands out. "Let me know if you have questions" or "Can you take a look when you get a chance?" are better alternatives.

On Slack, be responsive during work hours. If someone sends you a message and you don't respond for four hours without any indication of why, it reads as disengaged. Even a quick "Saw this, will look into it after my current meeting" is better than silence.

Use threads. Reply in threads, not in the main channel. This is a small thing that makes a surprisingly big difference in how organized and collaborative you appear.

And for the love of everything, don't send a Slack message that just says "Hi" and then wait for a response before stating what you actually need. This is sometimes called the "no hello" principle, and it's one of the quickest ways to mildly annoy your colleagues. Just say what you need. "Hi, quick question about the deployment — are we using the blue-green strategy or rolling updates for this release?" One message. Everything they need to help you.

What Changed My Mind About Soft Skills

For most of my early career, I thought of soft skills as the consolation prize for people who weren't technically strong enough. Real engineers ship code. They solve hard problems. They don't need to worry about "communication styles" and "cultural fluency." That was stuff for MBAs and HR people.

What changed my mind was watching who actually moved into leadership. It wasn't the best coders. It wasn't the people with the most certifications or the deepest technical knowledge. It was the people who could explain a complex technical concept to a non-technical executive in two sentences. The people who could defuse a tense meeting with a well-timed comment. The people who gave feedback that made others better without making them defensive. The people who everyone wanted on their team, not because they wrote the best code but because they made the whole team work better.

I realized that soft skills aren't the opposite of hard skills. They're the amplifier. A brilliant engineer with great soft skills has ten times the impact of a brilliant engineer without them. And a decent engineer with exceptional soft skills often outperforms a brilliant engineer with none, because engineering is a team sport and the person who makes the team better is more valuable than the person who writes the best individual code.

That realization came slowly, over years of watching and learning and sometimes failing. And I'm still working on it. I still catch myself being too indirect sometimes. I still sometimes say yes when I should say no. I still occasionally sit through a meeting without contributing because old habits die hard. But I'm aware of it now, and awareness is where change starts.

If you're an Indian professional working in or preparing to work in a multicultural team, take this stuff seriously. Not as an afterthought to your technical preparation. As an equal priority. The technical skills get you the job. The soft skills determine what you do with it.