I was mentoring a junior engineer last month who built something genuinely clever—a multi-tenant orchestration layer that solved a real operational problem at his startup. When I asked him to present it to the broader team, he hesitated. “It might not be production-ready,” he said. “Someone else probably has a better solution.” This wasn’t false modesty. This was learned helplessness dressed up as humility.
That moment stuck with me because I’ve seen it play out across Indian tech teams for years. We’ve built a generation of engineers who are technically skilled but psychologically trapped in a zero-sum game. They optimize for not losing rather than for winning. And that distinction matters enormously when you’re trying to solve novel problems.
The Historical Machinery
The competitive obsession in Indian education didn’t emerge organically from our culture. The British engineered it, quite deliberately, during the colonial period. They needed a hierarchical administrative class—people who would compete fiercely for scarce positions within the Indian Civil Service. So they built an education system around scarcity and rank. You didn’t learn to think; you learned to score higher than the person next to you.
Independence didn’t dislodge this system. We doubled down instead. With limited university seats and intense pressure to escape poverty through education, competition became a survival mechanism. Survival mechanisms don’t simply disappear when conditions improve. They calcify into culture.
The JEE entrance exam is where this crystallizes. A single test determines access to India’s premium engineering colleges. Not curiosity. Not the ability to ask good questions. Not collaboration. A rank. One number that supposedly measures your worth as a thinker.
Where Culture Meets Psychology
Here’s what fascinates and disturbs me: Indian parents aren’t being irrational when they obsess over their children’s marks. They’re responding to real systemic incentives. But the psychological cost is staggering.
When a child’s entire childhood is structured around comparison—“your cousin scored 95, you scored 92”—they internalize a fundamental belief: my value is relative to others. Researchers call this “contingent self-worth.” You can’t evaluate your own work on its merits anymore; you can only evaluate it against a peer group.
I’ve watched this play out in code reviews. An engineer will defend a technically inferior solution because “at least it’s not the worst approach.” Or they’ll stay silent in meetings about a potential optimization because they’re not certain it’s the optimal solution. Uncertainty—the natural starting point for innovation—feels like failure.
The fear goes deeper than professional embarrassment. There’s genuine anxiety about being revealed as “not good enough,” and no amount of actual competence seems to alleviate it. I’ve worked with engineers who’ve shipped to millions of users, who architect complex systems daily, and they still carry this low-level dread that they don’t truly belong.
The Corporate Amplification
The workplace should theoretically be where we unlearn these patterns. Instead, most Indian tech companies actively reinforce them.
Stack ranking is everywhere. Performance ratings tied to forced distributions. Promotions framed as zero-sum advancement. “Only one person can be the senior engineer on this team.” Knowledge gets hoarded because sharing expertise is seen as reducing your competitive advantage. I’ve watched talented people deliberately obscure their work to prevent others from taking credit.
This creates a specific dysfunction: pockets of excellence surrounded by broken collaboration. Teams can’t synthesize knowledge across silos because the silo is your moat. The company loses optionality. The engineer loses growth. Everyone loses.
Young professionals enter this environment primed for competition and find validation for those instincts. The system works perfectly—just not in the direction of innovation. It works in the direction of attrition and burnout.
The Innovation Problem
Innovation requires something the competitive model actively suppresses: the willingness to explore directions that might fail.
When you’re optimizing for rank, you gravitate toward established domains with clear metrics. In India’s tech space, that historically meant Java backend development, front-end frameworks, and QA automation—domains with proven ROI and clear advancement paths. Nothing wrong with those specializations. But a nation of specialists in proven domains doesn’t build novel solutions. It optimizes existing ones.
What we systematically avoid: emerging infrastructure problems, deep systems work, cross-disciplinary integration. These are inherently uncertain. You might spend months on an approach that doesn’t work out. In a zero-sum competitive system, that’s a loss you carry into your next evaluation.
The real question isn’t “Can I afford to fail?” It’s “Can I afford not to explore?” But that requires a psychological shift most of us weren’t trained to make.
Toward Ecosystem Thinking
I don’t have a policy prescription. Education system reform requires alignment across government, institutions, and culture—that’s a multi-decade bet. But there’s something engineers and technical leaders can do right now.
What does good engineering culture look like when you remove competitive ranking? I’ve found that it looks like ecosystem thinking—viewing your team as an interconnected system where individual growth is coupled to collective capability.
Practically, that means:
- Explicit knowledge sharing. Document architectural decisions. Pair on hard problems. Celebrate when someone learns something novel.
- Reframe failure as data, not rank. “That approach didn’t work” becomes “Now we know X” rather than “I’m not good enough.”
- Measure team progress, not individual comparison. How much technical leverage did we build this quarter? How did our infrastructure improve? What new capabilities emerged?
- Rotate responsibility. Let people work in unfamiliar domains. Most of the best engineering I’ve seen came from people who were slightly outside their comfort zone.
None of this requires changing the national education system. It requires changing what you optimize for in your sphere of control.
The Wager
I’m betting that the next wave of Indian technical innovation will come from people who somehow escaped the competitive trap—either because they had unusually self-aware mentors, or because they worked remote and never fully internalized the local culture, or because they’re just wired differently and couldn’t internalize the rankings even when they tried.
But we’re leaving enormous potential on the table. There are people in our tech industry right now who could build genuinely novel infrastructure, who could bridge domains, who could ask the weird questions that lead somewhere—and they’re not doing it. They’re still optimizing for not losing.
The irony cuts deep. Real competitive advantage in tech comes from exactly what we’ve been trained to suppress: the willingness to try things that might not work, the confidence to integrate disparate skills, the psychological safety to say “I don’t know yet, but let’s find out together.”
That shift from zero-sum competition to collaborative exploration isn’t just better for individuals. It’s what actually moves technology forward.