IndiaIndustry

Why Tech Talent is So Cheap in India (The Real Truth)

Not because we are worse. Not because we are small. Because a huge amount of the value we create flows to somebody upstream, while we keep selling by the hour instead of the outcome. This post digs into the real pricing mechanics — positioning, services-versus-products, customer ownership, niche — and the four concrete shifts that quietly double rates without any change in skill. You can be the best hammer in the world; if you sell by the hour, you get hour money.

Siddharth PuriMarch 24, 20269 min read
India Tech Reality

Why Tech Talent is So Cheap in India (The Real Truth)

March 24, 2026 · 9 min read · Siddharth Puri

I love this country. I also know what Indian engineers get paid and what their work sells for to the end client. Those two numbers do not match the talent level. The gap is wide enough that it cannot be explained by "we are cheaper because we are smaller." So why?

I have spent a lot of time thinking about this, and the answer is not flattering to anyone — it is not about skill, it is about positioning, and positioning is a thing we have collectively gotten bad at. The good news: positioning is fixable.

It is not skill. It is positioning

Most Indian tech work is sold one step below where value is captured. We sell services, not products. We sell billable hours, not outcomes. We sell "a developer" instead of "a solution." You can be the best hammer in the world; if you sell by the hour, you get hour money. The hammer is not the issue. The business model is.

An American engineer shipping the exact same code at an American startup captures 10x what the same code captures through an Indian services shop. The code is the same. The wrapper around the code is different.

The value chain, honestly

Imagine a feature that produces $1M of revenue for a US startup. That startup pays, let's say, $400k to build it. They hire a US agency. The agency keeps $200k and subcontracts $200k to an Indian shop. The Indian shop pays the actual engineers $80k. The engineer who wrote the code — the thing that generated $1M — got $80k. Everyone upstream got more without writing any code.

This is not a conspiracy. It is a value chain doing what value chains do: paying the people closest to the end customer more than the people doing the underlying work. The fix is not complaining. The fix is moving closer to the customer.

What actually moves the price

  • Owning the customer, not subcontracting the customer — talk to the end user, not the middleman
  • Selling an outcome, not a body — "I'll ship this feature" not "I'll provide 2 devs for 3 months"
  • Product equity over project margin — own a slice of the upside, not just an invoice
  • Saying "no" to one-off work that funds the next month but kills your leverage — keep the bench warm for bigger bets
  • Building a niche so specific that "the person for that problem" is you, globally

The customer-distance problem

Here is the specific trap for Indian engineers and agencies: we often work two or three customers removed from the actual end user. We are building what a middleman told another middleman the real customer wanted. The message degrades at every hop, and so does the value we can capture.

Closing that gap is worth more than any technical upskilling. One conversation with the real customer beats three emails with a middleman every time. If you currently have a job or client where you never talk to the person using what you build, you are leaving money on the table you do not even know exists.

Why this is slowly changing

The encouraging part: the internet has made customer proximity achievable in a way it was not ten years ago. Indian engineers and small shops are increasingly selling directly to US startups via Twitter, LinkedIn, Upwork, and their own direct networks, cutting out the agency middlemen entirely.

When this happens, rates go from $30/hr agency to $100/hr direct. Same engineer, same code. The only thing that changed is one fewer middleman. That is the opportunity of this decade for Indian tech workers who are paying attention.

What you can do this quarter

  • Write in public about your domain. Blog, tweet, publish case studies. Build a direct inbound channel
  • Pitch one outcome-based engagement, even a small one — "I'll deliver X for $Y" instead of hourly
  • Research who your real customer is. If you're sub-contracting, find one direct client this quarter
  • Say no to one underpaid gig. Keep the bench time open for a better one. Hard but necessary
  • Pick a niche. "Full-stack developer" is a race to the bottom. "Fintech dashboards for US Series A startups" is a career

The larger picture

India does not have a talent problem. We have a positioning problem. That is actually a better place to be, because positioning is a learnable skill and can change in five years. Fixing a talent gap takes decades.

The best engineers I know in India today are charging US-market rates. Not because they are better than their peers — because they figured out positioning first. The rest of us can catch up. The path is known.

We are not cheap because we are small. We are cheap because we sell by the hour.
All postsSiddharth Puri

Keep reading

View all →
AI & Future of Work

Claude 3 vs GPT-5: What Changed and Why It Matters

March 26, 2026 · 9 min

Claude 3 vs GPT-5: What Changed and Why It Matters

They both claim to be the smartest thing ever built, and both demos look suspiciously similar. This is a ground-level look at how Claude 3 and GPT-5 actually differ in reasoning depth, long-context reliability, code quality and tool use — plus a blunt cheat sheet for which one to pick for which job. Written in English, without the benchmarks theatre.

AI & Future of Work

Will AI Really Replace Developers or Just Upgrade Them?

March 18, 2026 · 8 min

Will AI Really Replace Developers or Just Upgrade Them?

The internet has been burying developers every year since 1998 and we keep showing up for breakfast. Here is the honest split — which parts of the job AI genuinely eats (boilerplate, docs, test scaffolding, Stack Overflow archaeology) and which parts quietly get harder and more valuable (product judgement, architecture, ambiguity). Short answer: it replaces the parts of your job you hated, and the parts that pay you get more fun.

AI & Future of Work

Jobs That Will Survive the AI Revolution (And Why)

March 8, 2026 · 9 min

Jobs That Will Survive the AI Revolution (And Why)

Forget the "creative vs repetitive" framing — the real line is "work customers trust a machine with vs work they do not." This post maps three tiers: jobs that will stay deeply human (health, founding sales, investigative journalism, skilled trades), jobs that will transform rather than disappear (design, engineering, teaching, support), and jobs that are quietly becoming the best bets of the decade. A calmer, less LinkedIn-flavoured take on the next ten years.