India's IT Industry

Zusammenfassung

India’s information technology industry built itself on a paradox: a country with inadequate roads, unreliable electricity, and a per-capita income below sub-Saharan Africa became the world’s back-office for technology work. The reasons trace to a specific combination of policy decisions, a single crisis, a diaspora network, and the structural economics of software labor — a combination that produced Infosys and Wipro, redefined how American companies built their engineering organizations, and eventually produced more engineering graduates annually than the United States and Europe combined.

The Foundation: IITs and an Educated Elite

India’s technology story begins not with companies but with institutions. The Indian Institutes of Technology, established starting in 1951 under Prime Minister Nehru’s vision of “temples of modern India,” created a pipeline of rigorously trained engineers that was disproportionate to India’s overall development level. The entrance exam — the JEE — became one of the world’s most competitive; acceptance rates below 1% ensured that IIT graduates were genuinely elite.

The problem was that India had almost no domestic technology industry to absorb them. The Indian government’s regulatory regime — popularly called the “License Raj” — made starting businesses, importing equipment, and scaling companies almost impossible. IBM left India in 1977 rather than comply with requirements that it reduce its ownership stake in Indian operations to 40%. Texas Instruments, which wanted to open a development center in Bangalore in 1985, spent two years negotiating permissions for a satellite uplink that would let its engineers transmit data to the US without shipping magnetic tapes by air.

The result was brain drain at scale. IIT graduates moved to the United States, Britain, and Germany, where technology industries could actually employ them. The Indian diaspora in Silicon Valley, in particular, became technically and financially influential in ways that would matter enormously in the 1990s.

Info

The IIT diaspora’s influence on Silicon Valley is difficult to overstate. By 2000, Indian-born founders or co-founders led companies including Sun Microsystems (Vinod Khosla), Hotmail (Sabeer Bhatia), and Juniper Networks (Pradeep Sindhu). Vivek Wadhwa’s 2007 research found that Indians had co-founded 15.5% of Silicon Valley’s technology and engineering companies, despite representing less than 6% of the US population.

Texas Instruments and the Satellite Uplink

Texas Instruments’ 1985 decision to open a software development center in Bangalore was the inflection point that demonstrated the model. TI negotiated, eventually, a dedicated satellite link that allowed its Bangalore engineers to collaborate in real time with engineers in Dallas. The arrangement worked: Indian engineers, paid a fraction of American salaries, produced work indistinguishable in quality.

Other American companies noticed. The model was simple: hire trained Indian engineers in India, pay Indian salaries (often 10–15% of US equivalents in the 1990s), transmit code via telecommunications links. The cost advantage was enormous. The risk — communication delays, time zone differences, coordination overhead — was real but manageable for certain categories of work.

Nasscom, the National Association of Software and Services Companies, was founded in 1988 to represent the emerging industry. The Indian government, recognizing software exports as a foreign exchange earner that required no physical commodity imports, created Software Technology Parks of India (STPI) in 1991 — dedicated zones with reliable power, telecommunications infrastructure, and tax exemptions that Indian businesses otherwise could not access. The liberalization of the Indian economy in 1991, forced by a balance-of-payments crisis, removed many License Raj constraints.

Infosys and the Professional Model

Narayan Murthy founded Infosys in 1981 with six colleagues and $250 — borrowed from his wife. The company’s founding insight was not technical but managerial: Indian software companies could build Western-style professional processes, predictable delivery, and institutional client relationships, and could do so at dramatically lower cost than Western competitors.

Infosys was deliberately unusual in Indian corporate culture. It listed on NASDAQ in 1999 — the first Indian company to do so — signaling to American corporate clients that it met Western disclosure and governance standards. It issued stock options broadly, creating millionaire software engineers and a middle class of technology workers that was unprecedented in India. It built its headquarters in Mysore as a corporate campus modeled, explicitly, on American technology company campuses.

Wipro’s path was different. Founded by Azim Premji’s father as a vegetable oil company in 1945, it pivoted into technology hardware in the 1970s and software services in the 1980s. Tata Consultancy Services (TCS), owned by the Tata conglomerate, had begun as an internal technology function and externalized into a services business. These three companies — Infosys, Wipro, TCS — became the anchor institutions of what Indians called “IT services” and Americans called “outsourcing.”

Y2K: The Accidental Launching Pad

The Year 2000 computer problem was, for India’s IT industry, the equivalent of a decade of organic growth compressed into three years. The Y2K problem was perfectly suited to the Indian IT model: it was well-defined, urgent, required enormous amounts of competent but not creative programming work, and carried enormous financial penalties for American companies that failed to fix it in time.

American corporations, facing an army of COBOL mainframe code that needed inspection and remediation line by line, could not hire domestic programmers fast enough. Indian IT companies had the bodies. TCS, Infosys, and Wipro each staffed hundreds of Y2K remediation projects for American financial institutions, insurance companies, and government agencies. The work was tedious — finding and fixing two-digit year fields in millions of lines of code — but it introduced Indian IT firms to the procurement processes, legal structures, and relationship networks of Fortune 500 companies.

When Y2K passed without catastrophe, many of those client relationships continued. The American companies that had outsourced Y2K work realized they could outsource other software development work on similar terms. The offshoring wave of the early 2000s was, in significant part, a Y2K aftereffect.

The H-1B Economy

The H-1B visa program, created by the Immigration Act of 1990, allowed American companies to hire foreign workers in “specialty occupations” — predominantly software engineering — on temporary work visas. The program was designed with Silicon Valley’s talent needs in mind: the technology industry had lobbied for it as a solution to a perceived domestic shortage of engineering talent.

The H-1B program created a triangular economy. Indian engineers on H-1B visas worked for American technology companies. Indian IT services companies — Infosys, Wipro, TCS, and later HCL — used H-1B visas to staff their American operations with employees who could work on-site with clients while remaining on Indian payrolls. The visa program became controversial because it allowed companies to simultaneously claim they could not find American workers and pay foreign workers wages below American market rates.

By the 2000s, Infosys and Wipro were among the largest recipients of H-1B visas annually. The structure created a labor market anomaly: Indian engineers in America on H-1B visas had limited ability to change employers (the visa tied to a sponsoring employer), which gave companies leverage over wages and working conditions that they would not have had with American citizens or green card holders.

Warnung

The H-1B program’s design — capping visas at 65,000 annually but allowing companies to apply for far more than available — created a lottery system that was widely gamed. Body-shopping firms (companies that acquired H-1B visas and rented workers to clients) exploited the program’s design. The debate between “importing cheap labor” and “filling genuine talent gaps” was never resolved, because both were simultaneously true depending on the company and the role.

The Offshoring Wave

The 2001 dot-com crash was, paradoxically, an accelerant for Indian IT offshoring. American technology companies, facing pressure to cut costs after the bubble burst, adopted offshore development models that had previously been considered risky or experimental. Accenture, McKinsey, and IBM’s services division advised Fortune 500 clients to move application development, testing, and maintenance work to Indian vendors. The cost savings were real: a software engineer in Bangalore in 2003 cost roughly one-sixth of an equivalent role in San Jose.

The offshoring wave produced a model called the “Global Delivery Model” — a hybrid structure in which requirements definition and architecture happened in the United States, coding and testing happened in India, and delivery was managed across time zones. Infosys codified this as a systematic methodology; its Mysore training campus could on-board thousands of engineers annually into the model.

The social consequences in the United States were visible and politically charged. American software developers, particularly in industries like financial services, insurance, and healthcare IT, found their roles being eliminated or reclassified as “offshore-eligible.” The term “outsourcing” became a political negative. The 2004 US presidential campaign featured debates about “Benedict Arnold CEOs” who sent American jobs abroad.

India’s consequences were different. Software engineer became the most aspirational career track in the country. Engineering college enrollment exploded. A generation of Indian parents who had grown up under the License Raj told their children that software was the path to economic security. The boom created a genuine middle class in Bangalore, Hyderabad, and Pune — cities that built corporate parks, apartment complexes, and malls to service the new economy.

Beyond Services: The Product Question

For two decades, India’s IT industry was defined almost entirely by services — writing code and running systems for other companies’ products. The question of whether India could produce globally competitive technology products became a recurring debate.

The structural barriers were real. Services companies optimized for billing rates and utilization — the percentage of engineer-hours billed to clients. Product development requires extended periods of non-billable work, tolerance for failure, and a different compensation model (equity rather than salary). The cultural and managerial systems built for services were poor preparation for product development.

The 2010s produced partial answers. Flipkart, founded by IIT Delhi alumni Sachin and Binny Bansal in 2007, built India’s dominant e-commerce platform before being acquired by Walmart for $16 billion in 2018. Ola became the domestic answer to Uber. Paytm, Zomato, and Razorpay built significant fintech and payments businesses. Freshworks became the first India-founded SaaS company to IPO in the United States (2021). Zoho, privately held and headquartered in Chennai, quietly became a serious global competitor to Salesforce and G Suite.

But the category of globally dominant, frontier technology products — search engines, operating systems, cloud platforms, social networks — remained almost exclusively American (with Chinese equivalents for the Chinese market). Indian engineers led product teams at Google, Microsoft, and Adobe, and two of America’s most prominent technology CEOs — Sundar Pichai at Google and Satya Nadella at Microsoft — were IIT alumni. India’s contribution to the world’s technology products was immense. The companies that captured the value from those contributions were American.

The AI Wave and a New Inflection

The rise of large language models beginning in 2022 created a new strategic question for Indian IT. If AI could automate significant portions of routine software development and testing — the work that constituted the core of services business — the low-cost labor arbitrage that had driven India’s IT industry for thirty years would erode.

The response was varied. TCS, Infosys, and Wipro announced large investments in AI capability, positioning themselves as partners in “AI transformation” rather than providers of labor. But the underlying economics were uncomfortable: if an AI system could do the work of ten entry-level engineers, the cost advantage of Indian labor was irrelevant. The industry that had been built on the arbitrage between Indian engineering talent and American salaries would need to find a new basis for value creation.