TCS Says Nida Khan Was Not HR. Then How Did She Operate Like HR?
The controversy surrounding TCS’s Nashik unit has quickly moved beyond a routine corporate clarification into a serious question of internal accountability. What began as a police-led sting operation has now exposed a deeper contradiction that the company’s official statement has not resolved. Investigation officers, backed by undercover findings, have reportedly identified Nida Khan as the mastermind behind the alleged activities. More importantly, she has been linked to an HR-facing role in the entire setup, interacting in a manner consistent with recruitment or hiring processes.
TCS, however, has responded with a sharply worded distancing strategy. In its statement, the company clarified that Nida Khan was merely a process associate and had no role in HR or recruitment. It further emphasized that no complaints were received through official ethics or POSH channels, and that its Nashik operations remain unaffected. On paper, this appears like a clean separation. But in reality, it opens up a far more uncomfortable question. If she was not HR, then how did she operate like HR in a manner convincing enough for both victims and investigators?
This is not just a semantic issue of designation versus perception. It is a structural contradiction that goes to the heart of how access, authority, and oversight function inside large corporations. Because if both statements are true, then the system itself has failed in ways that cannot be brushed aside with job titles.
The “Not HR” Defence: What TCS Is Really Saying
TCS’s response relies heavily on formal structure. By stating that Nida Khan was not part of HR and had no recruitment authority, the company is drawing a clear legal boundary. It is essentially saying that whatever actions are being alleged did not originate from within its official HR framework. This is a classic corporate defense, one that separates organizational responsibility from individual conduct by focusing on designation.
But this defense, while technically sound, raises a larger concern. Corporations do not operate solely on designations. They operate on processes, access, and interactions. If an individual, regardless of title, was able to function in a way that mirrored HR activity, then the issue is no longer about what her job title was. It becomes about how the system allowed such a role to emerge in the first place.
Mastermind Without Authority: The Core Contradiction
The police investigation reportedly identifies Nida Khan as the mastermind. This is not a minor characterization. It suggests planning, coordination, and control. When placed alongside TCS’s claim that she had no authority in HR or recruitment, the contradiction becomes stark.
How does someone without formal authority allegedly orchestrate an operation that appears to sit within one of the most sensitive functions of a company? Recruitment and HR are tightly controlled domains, especially in large organizations like TCS. If she indeed played a central role, then her lack of official designation only deepens the concern rather than resolving it.
How Did She Gain HR-Level Access?
This is where the operational questions begin to matter. How did Nida Khan interact with candidates or individuals involved in the alleged case? Did she have access to hiring pipelines, candidate data, or communication channels that are typically restricted to HR personnel? Was she acting independently, or did she exploit existing gaps in internal workflows?
Even more critically, how did her role appear legitimate enough for others to engage with her as if she were part of HR? Whether through direct representation or indirect involvement, there had to be a point at which perception aligned with authority. That alignment does not happen in isolation.
Where Was the Real HR and Management?
In a company of TCS’s scale, hiring and HR processes are layered, monitored, and audited. There are multiple checkpoints designed to prevent exactly this kind of situation. Which raises the obvious question: where was the actual HR structure when these alleged activities were taking place?
Did internal systems fail to detect irregular patterns? Were there no red flags raised by employees or candidates? Or were those signals ignored or dismissed? The absence of answers here points toward a possible gap in supervision, not just an isolated incident involving one individual.
No Complaint, No Problem? The POSH Angle
TCS has leaned heavily on the fact that no complaints were received through official ethics or POSH channels. While this may be factually accurate, it does not necessarily settle the issue. The absence of formal complaints does not automatically imply the absence of misconduct.
It raises a different set of questions. Did individuals feel confident enough to report concerns? Were they aware of the mechanisms available to them? Or was there a disconnect between the existence of these channels and their actual accessibility or effectiveness? A system that exists only on paper offers little protection in practice.
Did She Present Herself as HR?
At the center of this entire issue lies a simple but critical question. Did Nida Khan present herself as HR in her interactions? And if so, how was that representation accepted without verification?
If candidates or individuals believed they were dealing with HR, that perception had to be created somehow. Whether through communication style, control over processes, or institutional proximity, the gap between perception and reality is where the problem sits. And that gap cannot be explained merely by pointing to an official designation.
A Bigger Question for Corporate India
This incident is no longer just about one individual or one company. It raises broader questions about how large organizations manage internal access and accountability. If someone without formal authority can allegedly operate within a critical function like HR, then the issue extends beyond TCS.
It becomes a question of systemic safeguards. Are internal controls robust enough? Are verification mechanisms strong enough to prevent role misrepresentation? And most importantly, are companies too reliant on formal hierarchies while ignoring how work actually flows within their systems?
Conclusion
TCS’s statement attempts to draw a clear line between official roles and alleged actions. But instead of closing the issue, it has widened the gap between what is being claimed and what appears to have occurred.
If Nida Khan was not HR, then how did she operate like HR? And if she did, how did it go unnoticed in one of India’s largest corporations?
These are not peripheral questions. They go to the core of accountability. Because in this case, the absence of answers is far more telling than the presence of a carefully worded statement.
