It rarely arrives as a slur. It does not appear in the job description or the company values slide. On a tech team, casteism tends to look like something else entirely: a full review that never comes, a promotion cycle where the same names keep surfacing, a better idea absorbed into the room and attributed to someone else by the end of the meeting.
The thesis is simple and uncomfortable. Caste does not stop at the office door. It travels with people — into standups, into Slack threads, into the unspoken calculus of who gets sponsored and who gets managed out. The technology industry's self-image as a meritocracy is precisely what makes it so effective at hiding this.
Consider what informal networks actually are. Mentorship, referrals, after-hours conversations, the warm introduction to a senior engineer — these are not neutral professional courtesies. They are systems of transmission. Who gets pulled into those systems and who is left to perform competence without the social capital that accelerates careers is rarely random. Caste shapes those patterns long before anyone enters a hiring pipeline.
The counterargument is predictable: tech rewards output, not identity. But output does not exist in a vacuum. It is evaluated, attributed, amplified, and remembered by people embedded in social structures they did not choose and rarely examine. A Dalit engineer navigating that environment is not competing on the same terrain, no matter how elegant their policies are.
Naming this is not grievance. It is precision. Until tech teams learn to see the hierarchy inside the flat org chart, they will keep reproducing it — and calling it excellence.